-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transfering large files fails #1814
Comments
After some more investigations it seems like the closed down connection happens even with no file transfer. After a few minutes after system booted I always get this message. |
This is almost certainly because the client or server is not seeing DSI "tickle" packets. Once a DSI connection is established, both the client and server send these out periodically to verify that the link is still alive. A network trace will determine which side is not working (logs points to server not seeing client tickle). How is the SE/30 connected to the network? PDS Ethernet? SCSI Ethernet? |
It is connected using BlueSCSI DaynaPort emulation through SCSI. What is the best way to get network trace for this ? Wireshark, mitm, ... ? |
What build options were used to compile? I know that if First test would be Wireshark (use filter |
Can you please share your afp.conf? It is helpful to know your exact settings. The |
@ronangaillard Did you have the chance to look at this yet? If we can get some debug logs, we should be able to get some insights into the movement of DSI tickles. |
I've been having the same issue connecting from Mac OS 9.2.1 running under UTM 4.6.4 (a QEMU wrapper) when attempting to write a file to a network share of almost any size. The Finder gets to 3K of and then just craps out, but it appears the copy process is still running because a blob of bytes is deposited onto the server but cannot be read usefully. I have a physical device, a PowerMac 7100/80 running Mac OS 9.1 connected via Ethernet, that I will test out as well. I'm running Netatalk 4.0.8 on a Raspberry Pi that I compile and install locally. It's connected to an ethernet hub, which in turn, is connected to one of my Eeros. In terms of obtaining the debug logs, is it a compile-time or run-time option to generate those? |
OK, I figured out logging! Here's an example of trying to copy a PDF file, NetworkingOpenTransport.pdf, from my emulated Mac OS 9.2.1 to the AppleShare directory, which is just the root of my home directory. Please let me know if you want a more detailed debug log level or what else would be helpful.
|
Some follow up FWIW:
|
@cgervais So if I understand the situation correctly, you had the issue consistently in your environment before, but after reinstalling netatalk it works? |
After building and deploying the latest 4.1.0 code, the problem seems to have gone away. I'll keep testing and if something changes with supporting large file transfers, will add more here. I mistakenly cited a non-existent 4.0.10 version above. |
Describe the bug
When moving a large file (tried with a 842k file) from the hard drive to the shared folder it fails and disconnect from the shared drive.
If I move files around 200k it works fine.
I tried to set
tickleval = 600
but it did not change anything (apart from failing later).For information the transfer failed after 5 minutes and 15 seconds. The transfer speed seems very bad too, not sure why.
Here is the log I have on the netatalk side :
I tried
To Reproduce
Move file more then 800k from hard drive to the shared drive.
Expected behavior
To not fail
Environment
Logs
The text was updated successfully, but these errors were encountered: