It took me a while to figure out what the root of the problem was here, but if I connect to two different shares from my Mac via smb and try to transfer a file from one share to the other the file transfer will fail after a few minutes. My Mac will also completely lose connection to the LAN. The only way I've been able to restore the LAN connection is to reboot the Mac (there's probably a better way, I just don't know it).

 

I doubt this really an unRAID issue. Probably an smb or Mac/smb problem. Or maybe user . I know I can avoid this problem if I transfer the file first to the Mac and then to the intended share destination. Is this some limitation of smb? Is there something I can adjust in my smb share settings that will stop this from happening? I'm constantly forgetting about this and then having to wait for the Mac to reboot and start the transfer all over again.

So you have 2 windows open in finder, each is open to a different share and you are transferring a file(s) from 1 window/share to the other is when you have the issue. Is that correct?

Yes. Only when I transfer from one window to the other and only after about 3 or 4 GB.

I just tried it with 4gb and it only took <second from my '11 iMac.

I'm on OSX 8 (ML) which is not suppose to be as good with SMB..

Maybe it is a network issue, mine is all hardwired except WIFI for my iPad & FireStick.

Mine's all hard wired too. Don't see how it could transfer 4GB in less than a second between two different shares over your network? Are you sure it wasn't two folders in the same share?

32 minutes ago, wgstarks said:

Mine's all hard wired too. Don't see how it could transfer 4GB in less than a second between two different shares over your network? Are you sure it wasn't two folders in the same share?

It's not actually transfering data, just changing a directory pointing to the file(s). Although if moving to a different share on different disc which the second share does not exist then, I believe the files would actually come through the network, to the Mac then back out the network to the second share..

So that's a long way around.

If that is the case probably a better way to move the file is in Terminal...

 

Somebody correct me if I'm wrong.

29 minutes ago, Russ Uno said:

Although if moving to a different share on different disc which the second share does not exist then, I believe the files would actually come through the network

That's probably exactly what's happening. The "source" share is fairly new so probably only exists on one disk and then the "destination" share uses cache so would be writing to that disk.

 

Doesn't explain why doing this crashes the network connection though?

Did this also happen with an earlier version of Unraid?

I'm running v6.2.4..

 

1 hour ago, wgstarks said:

That's probably exactly what's happening. The "source" share is fairly new so probably only exists on one disk and then the "destination" share uses cache so would be writing to that disk.

 

Doesn't explain why doing this crashes the network connection though?

 Unless you have a bad switch, cable, cable connection or etc...

Only installed most of these dockers a few weeks ago. Never needed to move files between docker shares before that.