#11 File transfer (SMB or ftp) frozen during transfer

[Anonymous]

Originally created by: Angel.M.... (code.google.com)@gmail.com

What steps will reproduce the problem?
1. Simply upload or download to NAS files no too large around (700MB)
2. after certain number of files, the transfer breaks and application (SMB
or ftp) seems frozen
3. restart of the application will reset and restart the transfer

What is the expected output? What do you see instead?
* download and upload files via ftp and SMB.

What version of the product are you using? On what operating system?
SNAKE OS V1.0.0 (20091027)/2.6.16-gazineu. Windows XP prf edition.

Please provide any additional information below.
-No error logs are found in Nas logs.
-Sometimes the transfer recovers itself
-RAM usage is always over 90%

[Anonymous]

Originally posted by: jasv6374... (code.google.com)@gmail.com

Hello, I have the same problem, Windows 7 Pro installed, and...
I was experienced too it can't erase directories if they are not empty... Only can
erase them if first erase the archives containing one by one... Any solution?

[Anonymous]

Originally posted by: jasv6374... (code.google.com)@gmail.com

I have problems too with read and write on NTFS hard disc attached to NAS, it
contents "dissapears" and transfers and Explorer (Windows) was locked at few seconds
of start transfers.
I was tested this issues with 2 different routers with same results...
Anybody has the solution?

[Anonymous]

Originally posted by: Angel.M.... (code.google.com)@gmail.com

Bad to know I am not the only one with the isse. If it was only me, I might be doing
a wrong setting.
In case it is of help to create a workaround/fix: I noticed that every time I find
the problem, the CPU of the nas is 100%. Normally, when every thing is fine, CPU is
around 50%~60%.
When the CPU recovers normal values, and if the aplication did not go in timeout, the
session/transfer recovers itself.
I hope we get it fixed.

[Anonymous]

Originally posted by: ulisses.... (code.google.com)@gmail.com

Ok.. i had the same problem but i think i resolved it, or almost resolved it. By
using WinSCP, accessing thru SSH with your root account, you will see in your root
folder a folder named USB that contain the usb devices. You you notice the
permissions of that folder you can see that the T option is active ( right click the
folder and select Properties. You will notice that the STICKY BIT option is active.
I don´t know nothing about linux, but for what i could read online on some forums,
this options doesn´t allow user Y to delete a file owned by user X. As all of my
files are owned by root, i could not delete some files and folders. After making USB
and all files and folders inside 0777 instead of 1755 ( i think this was the initial
configuration ) i can now delete files and folders with my user account, despite all
files being marked as owned by root. sometimes i get a message that the file is
being used by some process, but those errors telling me that i needed root
permission to delete some file or folders, are gone for now. I have all my devices
formated as EXT3.

ALL OUR FILES BELONG TO US !!! :P

[Anonymous]

Originally posted by: jasv6374... (code.google.com)@gmail.com

Hi friends, I was made some tests and this problem persists with the new SnakeOS
1.1.0 firmware too...
File transfers freezes with disc formated in EXT3, then I was tested with FAT32 with
same bad results, so I think the HD format isn't the question.
I was read anywhere this problem is inherent to Samba security (Windows 7 and Vista,
but with others too) but I don´t know how to solve this issue.
And can't erase directly any folder if there is any archive in... And some files
erased reappears again!!!
With FTP clients occurs identical fails in LAN, I was tested several like Cuteftp
(the best I think), Filezilla, Fireftp...
Is possible to correct the permissions in Samba to permits to any LAN user to
read/write OK?

[Anonymous]

Originally posted by: pavel.ma... (code.google.com)@gmail.com

Try to use next settings for Samba daemon in /etc/smb.conf:
socket options = SO_KEEPALIVE TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=65536
SO_SNDBUF=65536
log level = 1
read raw = yes
write raw = yes
oplocks = yes
max xmit = 65535
dead time = 15
getwd cache = yes

[Anonymous]

Originally posted by: Angel.M.... (code.google.com)@gmail.com

Hello all, by chance, are all those with this problem using wireless? Encrypted? I
did, and to try I changed to wired. The problem (frozen transfers) disappeared.
Now I am more convinced than ever it is ... windows... as usual.
I noticed that every minute there are short interruption in the transfers (and
always). The frozen cases seems to correspond with one of those narrow interruptions
no recovered. See attached pic, every interrupt corresponds to a minute. I found in
internet reference to wireless card with side effects because of those interruptions
and a comment about the Windows "Wireless Zero Configuration" (WZC) -unbelievable-. I
have stopped the service and *by now* is working. It seems that WZC is useless in any
case.
I also changed the smb.conf file as Pavel indicates. Probably are good
recommendations improving smb sessions, but, Pavel, do you think they are the good
ones for wireless?
If someone has time, try: a-wired; b- wireless and stop WZC (admin tools->services->
Wzc and let me know your results.

Most of us uses wireless. Maybe Samba might come already with defaults values in
smb.conf optimized for wireless.

A bit long but I hope that helps. Angel

[Anonymous]

Originally posted by: Angel.M.... (code.google.com)@gmail.com

disregard the solution suggested in my previous mail. I still have the problem while
using wireless. However, it is not found using wired. Maybe it is still of help.
Angel

[Anonymous]

Originally posted by: dgazi... (code.google.com)@gmail.com

The wireless packet losses may be the culprit.
There may be two ways of get these problems sorted out, to upgrade samba or change
kernel tcp settings for better handling of it.
I could not reproduce this issue, will let you know to help in testing.

Labels: -Priority-Medium Priority-High
Status: Started

[Anonymous]

Originally posted by: Angel.M.... (code.google.com)@gmail.com

Hi Duglas, I captured several traces with wireshark in case you want to have a look
(one of with 2 recovers and 3 interruptions). Last one is too heavy to attach to
anything. If needed I better filter it out removing the central transfer data. I
attache a small one by now. As you guessed, it looks related with lost frames not
retransmitted by the server.
I am available for testing as needed.
Note: if needed, I may load V1.1 or other debugging one.
Angel  

[Anonymous]

Originally posted by: r.edwa...@hotmail.co.uk

Hi,

I have the same issue as well.  Running Windows XP Pro SP3, hard wired to router.  Can
provide further details if required; just let me know what you need

Thanks

Rob

[Anonymous]

Originally posted by: nahuel.r... (code.google.com)@gmail.com

I Have the same problem. I turn off the "ntp client" on the "Snake web admin" and
never frozen again (with my latop via wireless).
Any comments?

NAhuel

[Anonymous]

Originally posted by: dantu... (code.google.com)@gmail.com

I'm a Mac user and had these problems. I have managed to drastically reduce the number of errors by adding
this to /etc/smb.conf. I don't know if this will reduce problems for Windows users.

in the [global] section

add: unix extensions = no

then restart samba by using "/etc/init.d/samba restart"

Credit - http://www.macosxhints.com/article.php?story=20100405023255445

-Dan

[Anonymous]

Originally posted by: Angel.M.... (code.google.com)@gmail.com

Hello all, I am close to give up :-(

* I try all your smb.conf suggestions. The issue is still there. It makes sences it
is not a smb issue, it happens as well with ftp. 
* I set a log file via smb.conf (log file = /usb/500_root/download/log.%m) and the
following errors are shown:
[2010/05/21 23:24:37, 0] lib/util_sock.c:write_socket(566)
  write_socket: Error writing 61503 bytes to socket 7: ERRNO = Connection reset by peer
[2010/05/23 22:33:43, 0] lib/util_sock.c:write_socket_data(540)
  write_socket_data: write failure. Error = Connection timed out
[2010/05/23 22:33:48, 0] lib/util_sock.c:write_socket(566)
  write_socket: Error writing 32831 bytes to socket 7: ERRNO = Connection timed out

* btw, in the logs I found that entry "unix extensions" is not recognized.

I red in some samba old blogs that this might be caused by miss configuration in the
ethernet, and something might be related but maybe is the TCP implemenaton no enough
robust in the NAS. The reason i think so:
1- I tested 2 routers (wifi): same effect
2- with different PCs same behaviour.
3- removed all wifi encryption: same behaviour.
4- I connect with a fast ethernet (as mentioned before), and the problem disappears.

Wifi is the scenario presenting always the problem. But wifi plus other FTP at the
internet does not present the issue. Only with the NAS seems to be happening. Might
it be the TCP implementation in the NAS not able to recover the frequent frame lost
found in the Wifi?

Any hint to debug TCP errors at the NAS side?
Thank you in advance and Cheers,
Angel
PS: By the way, with FTP, max bit rate I get is 2,60Mbps and using samba, 9,60mbps. I
do not have a reason to explain that difference. I would expect similar throughput.

[Anonymous]

Originally posted by: agsa... (code.google.com)@gmail.com

Same problem here. I have tested this for one day with large files files and
different hdds, all with NTFS. The transfer was freezing regularly. I tested with 2
different access points (linksys WRT54G3G and tp-link TL-WA501G) - no difference.
With a wired connection I was not able to reproduce the problem.

I decided to check whether is is a packet-loss issue, so I tested with ping -t -l
65500 running at the same time. And while the ping was running I was not able to
reproduce the error. Then I found out, then if I'm able to catch the moment the
transfer freezes and send several ping commands before the error is reported then the
transfer was recovering. Seems like a concurrency bug in the software. Good that it
is reproducable.

[Anonymous]

Originally posted by: agsa... (code.google.com)@gmail.com

I've double checked my comment and one of the disks was FAT32. Same problem there.

[Anonymous]

Originally posted by: jasv6374... (code.google.com)@gmail.com

HI all,
Yesterday I made new tests transferring files from my computer, installed with Windows 7 32 bit and 64 respectively and within my own network and local network to my NAS WLX-652 with the latest firmware installed "-V1.2.0-snakeos 20100621-from-original.zip "installed, and the results were as follows:
- Both ethernet and wireless connection, you can access the shared folder and download files from the NAS to my PC as an anonymous user equipment.
- Both ethernet and wireless connection is accessible but not send files from my computers to the NAS, nothing happens and you receive a message that is not the path to the NAS.
- Using an FTP client to send files to a user logged into my NAS with write access from my computers to the NAS, is immediately a report that says that writing rights are denied by the NAS.
The shared folder on my NAS is configured to access any user with write access, and configuration of Samba access is anonymous or registered. The FTP server configuration is active for the same shared folder and turned off anonymous access.
That is, in any case I can access my shared files on my NAS to view and download to my computer either by ethernet or wireless, but in no case Samba allows writing.
Will this have any solution this in the future?

[Anonymous]

Originally posted by: Angel.M.... (code.google.com)@gmail.com

Hello, I do not see why does not allow you to modify them. I have never had such problem. I assume you have created your partitions with writable to "yes". You can check it as well under /etc/smb.conf. Each particion section has the writeable = yes.
If it does not solve it, try "properties" once mounted. There is a folder "permissions". it should be also changed there. I will try now version and report any change, but I suspect that it is not prepared the fix of the downaload problesm.

Regards,

[Anonymous]

Originally posted by: mdb... (code.google.com)@gmail.com

I can confirm that it isn't a Windows only problem. It happens too with Linux (over wireless 802.11n). I've made a packet capture over windows and I can see that when the problem happens a duplicate frame is sent by the NAS, without any request from the client. After that, several duplicated packets are sent. That seems to happen in large delays. On short delays (less than 1 sec), what seems to happen is that is a delay between the smb "chunk" request and the response, so the request must be retransmited.
All these symptoms almost disapear using settings on comment #6 (Pavel).
I'll keep testing and inform if I find out anything.

Regards,

[Anonymous]

Originally posted by: bala... (code.google.com)@gmail.com

I use Windows 7 32 bit and can't copy LARGE files with wireless interface with FTP or SMB.  With wired interface works fine.  As workaround, I use robocopy  to copy large files.  May be the problem is the tcp sliding window resize used for increase performance (Microsoft has a KBQ about it).

[Anonymous]

Originally posted by: enrico.b... (code.google.com)@gmail.com

I can confirm same issue from Linux to NAS via SMB: file transfers fails using wireless.
NAS Model: 650 BT
I also tried workaround on comment #6 with no success.
Please consider my NAS available for any test.
Thanks.

[Anonymous]

Originally posted by: magn... (code.google.com)@gmail.com

The problem happens to me as well. Only when I'm connected through WiFi.
Everything works great with Ethernet connection.
Ideas?

[Anonymous]

Originally posted by: pen... (code.google.com)@gmail.com

I have the freeze also, but in a different way.
I use the browse folder functionality from https://code.google.com/p/snake-os/issues/detail?id=50
So via the webserver on the NAS, I browse an external HD connected to the NAS via the USB port (directly).
And here also I have the problem that sometimes, while a directory listing is given, that it freezes for about half a minute.
The webserver is running on the NAS and via the NAS (unix ls command) a directory listing is made of the connected HD (formatted FAT 32) and then via a web page shown in the explorer of the connected computer. SAMBA or FTP are not used in this situation I guess.
So the problem seems to be really in the kernel of the NAS, is it not?
I have a second device and it has exactly the same problem.
The NAS device is a WLX-652

Can someone explain what is mend by accessing the NAS wireless (WiFi) or wired and why this would influence the problem?

Peter

[Anonymous]

Originally posted by: pen... (code.google.com)@gmail.com

Note that the change from comment 6 from https://code.google.com/p/snake-os/issues/detail?id=50 has as result that this problem does not occur that often anymore. So if you want to simulate this then use the older files before comment 6. It seems if the filesystem is accessed quickly that it does not occur...

[Anonymous]

Originally posted by: joelecl... (code.google.com)@gmail.com

I have the same problem.
I’ve tried all the snake OS firmware versions as well as the original and the updated original.
I’ve tried EXT 2, 3, NTFS and FAT32.
I’ve tried it wirelessly on 2 different NETGEAR routers, one with N and the other through G with WEP and WPA2 security.
I’ve tried transferring files to a Linux and several windows 7 computers.
Nothing seems to change it. While watching a movie it will drop out but if left to play will come back (depending on the player).
Is there any more information I could possible give to help the problem.

Joel