August 24, 201411 yr unRAID OS Version: Long Standing, still in 6b7 Description: Long delays and timeouts when copying files using Samba shares How to reproduce: - Initiate a copy from another Samba share (or a local Windows directory) to another Samba share. Does not always happen (see details below) Expected results: - File copied successfully Actual results: - Timeout error (or excessive wait before copy starts) Other information: I tried to copy a 16G file from one disk share to another disk share using Samba. The destination was almost full. I was using Windows 8.1 File Explorer. The server was recently rebooted and all disks were spun up. The copy dialog sat there at 0% copied for a very long time - I'd say a minute or even longer, before giving an error (see image below - note the file name is masked). I had noticed, about 20 seconds or so waiting for the copy to start, that the file explorer window that was displaying the source disk of the file i was copying was having trouble refreshing (the path field started filling with green from left to right). I refreshed the WebGUI to see if the server was unresponsive and it responded quickly while this copy delay was occurring and the file explorer window continued to try to refresh. Nothing in the log. After I got the message I tried it again. This time there was a short delay maybe 5-10 seconds, and the copy began and completed without issue. It did ask if I wanted to overwrite the file (the file didn't exist on the disk before I initiated the copy the first time). This kind of behavior has been occurring going back to sometime during the 5.0 betas I think, and has happened on multiple different servers / motherboards, and using various flavors of Windows from XP to Windows 8.1. I have noticed that this problem tends to happen and get worse especially with bigger disks and when the destination disk becomes fuller. I do not have any problem coping files between disks - even to near full disks - when doing the operations on the server (cp/mv).
August 24, 201411 yr Author Is either the source or destination a user share? For this example - yes, both are in the same user share. But they are being accessed via their disk shares. There was no media being played from the server at the time. In the past this same type of thing has happened with user shares disabled.
August 24, 201411 yr Is either the source or destination a user share? For this example - yes, both are in the same user share. But they are being accessed via their disk shares. There was no media being played from the server at the time. In the past this same type of thing has happened with user shares disabled. You mean the source/target is "DiskN/Share/file" instead of "Share/file" correct? How full is the target disk and can you please run a 'File System Check" on it? reiserfs is known to have severe slow down issues as the disk becomes very full.
August 24, 201411 yr Author Is either the source or destination a user share? For this example - yes, both are in the same user share. But they are being accessed via their disk shares. There was no media being played from the server at the time. In the past this same type of thing has happened with user shares disabled. You mean the source/target is "DiskN/Share/file" instead of "Share/file" correct? How full is the target disk and can you please run a 'File System Check" on it? reiserfs is known to have severe slow down issues as the disk becomes very full. I will run a check on the filesystem when I can. Server is busy today. I was copying from a disk share to a disk share. (//tower/disk5 to //tower/disk4). Both of the disks are in the same user share, but that user share was not being accessed at the time. The delay was in starting the copy, not doing the copy (once it started the copy fluctuated from maybe 15 MB/sec to 75 MB/sec, averaging maybe 25 or 30 - no complaints there.) Wondering if Samba is trying to pre-allocate the space for the copy and maybe RFS is taking a while to hunt up the blocks on the disk? But that doesn't explain why it would kick off relatively fast when I tried it a second time. I am going to try some random copying between disks and see what I find. Why do you think Samba lost its ability to refresh the source disk while trying to initiate the copy?
August 24, 201411 yr Author No corruption ... reiserfsck 3.6.24 Will read-only check consistency of the filesystem on /dev/md4 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Sun Aug 24 16:06:01 2014 ########### Replaying journal: Trans replayed: mountid 54, transid 11557, desc 4014, len 1, commit 4016, next trans offset 3999 Trans replayed: mountid 54, transid 11558, desc 4017, len 1, commit 4019, next trans offset 4002 Replaying journal: Done. Reiserfs journal '/dev/md4' in blocks [18..8211]: 2 transactions replayed Checking internal tree.. finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 963951 Internal nodes 5710 Directories 10 Other files 186 Data block pointers 975505621 (0 of them are zero) Safe links 0 ########### reiserfsck finished at Sun Aug 24 17:46:59 2014 ###########
August 24, 201411 yr This problem also exists with Windows 7 Windows explorer and using unRAID 5.05. The problem has been in Windows 7 since the early BETA days and has never been really addressed by MS. (I have no doubt that it also exists in Windows 8 which I don't use.) Have a look at the bottom of this thread for a possible 'work-around'. But I don't think it 'cures' it for everybody... http://social.technet.microsoft.com/Forums/windows/en-US/6f3edae6-c53c-4eee-a78c-0b8b2e0ecae1/a-lot-of-green-bar-freezing-in-windows-explorer?forum=w7itproperf If you do a google search on "what is green progress bar in windows 7" you will find lots of folks who have experienced this problem and I don't know if there is a guaranteed solution. I just ignore it and it usually resolves itself in about thirty seconds-more-or less.
August 24, 201411 yr Author This problem also exists with Windows 7 Windows explorer and using unRAID 5.05. The problem has been in Windows 7 since the early BETA days and has never been really addressed by MS. (I have no doubt that it also exists in Windows 8 which I don't use.) Have a look at the bottom of this thread for a possible 'work-around'. But I don't think it 'cures' it for everybody... http://social.technet.microsoft.com/Forums/windows/en-US/6f3edae6-c53c-4eee-a78c-0b8b2e0ecae1/a-lot-of-green-bar-freezing-in-windows-explorer?forum=w7itproperf If you do a google search on "what is green progress bar in windows 7" you will find lots of folks who have experienced this problem and I don't know if there is a guaranteed solution. I just ignore it and it usually resolves itself in about thirty seconds-more-or less. Thanks. I have seen this happen very occasionally too. But this issue with unRAID is very predictable and happens with SMB shares. The filling with green is a possible clue - not the cause. I have used shares extensively Windows to Windows and this problem has never occurred.
Archived
This topic is now archived and is closed to further replies.