Hi all, I am having problems coping large files from my mac to my unraid file share. The file starts copying hits 70MB and bombs out with the same -51 error.  I am getting the exact same issues mentioned in this thread:  http://lime-technology.com/forum/index.php?topic=5424.0

 

He mentions changing to a split level of 4 resolved the issue for him. Currently I don't have a split level set on my disk.  This share isn't a typical share rather just a file share with different directories and one of the directories contains my Aperture Photo library archives.  Some of these are 200+ GB.  I am trying to move over another archive around 260GB.  Would I want to use a split level on this share and if so how would I set this up?  None of my disks are super close to being full.  All have enough room for a smaller 60GB file I am trying to test with.  I have had a problem with files vanishing from plex and have a separate thread open for that.  I thought it was due to the drive not spinning up when scans are happing but possibly it's related to this as well? 

 

I would love to hear the suggestions. 

 

 

Share config contents

# Generated settings:

shareComment="Documents on Tower"

shareInclude=""

shareExclude=""

shareUseCache="yes"

shareAllocator="highwater"

shareSplitLevel=""

shareFloor=""

shareExport="e"

shareSecurity="public"

shareReadList=""

shareWriteList=""

shareExportNFS="-"

shareExportNFSFsid="0"

shareSecurityNFS="public"

shareHostListNFS=""

shareExportAFP="e"

shareSecurityAFP="public"

shareReadListAFP=""

shareWriteListAFP=""

shareVolsizelimitAFP=""

How big is much free space is on your cache drive?

It has about 60GB free. I tried bypassing the user share and going to the disk but same problem.

And how much free space did that disk have?

I tried one disk with 400GB and one with 1TB

Post a syslog that includes the activity.

my syslog is from Feb, I haven't rebooted in 177 days.  If I reboot will that load a more current syslog?  I saved a copy of the current one off to my desktop.

 

from Feb8-22nd

Syslogs are stored in memory like all of the unRAID OS and are lost on reboot so if you reboot you will only have a syslog that starts at that reboot.

 

Did you mean to attach the log to your last post?

I think what's in my log won't cover recent enough

The current log should go right up to now. See the v5 help link in my sig for instructions on getting your log.

I have ran the command to get the syslog but again it's only Feb.  I deleted it and reran the command and the same thing.  The logs directory contains stuff even older.  I am going to reboot and restart the copy in hopes of capturing something useful in the logs.  I made a copy of the older logs off to my desktop for now. 

zip the logs and attach.

Logs... it seems to truncate the logs on me. 

syslog-20150515-112021.txt.zip

You have a number of plugins running. Boot in SAFE mode and retry copy.