hi there!

 

i have a problem with my new unraid pro box: i've set up some shares to "fill up" because they are meant for backups that a) seldom changes and b) even less often needed to be read; now if there is say 4gb left on the first drive, and i'll try to copy a 8gb file from my windows 2008 r2 server (using dirsync or standard windows copy) it still starts writing to this disk leaving all other (still empty) disks aside; of course the copy process fails - but after a long, long time, while the speed drops to nearly 0 if i use windows copy. dirsync somehow manages to copy the next file already while disk 1 has 0b left (looks like the copy-process overlaps a bit) and this seems to direct it to the 2nd disk - but still only every 2nd file gets copied, because the used space of the partly copied (and failed) file ist released soon afterwards.

 

this isn'nt meant to be working like that, isn't it?

 

thanks in advance for every helpful answer - didn't find any clues using search and manual (or i'm blind)

 

ps: split level is set to 9, and the file is on the 3rd level...

 

pps: i found there is a "min. free space" setting for each share, which may do the trick, if set higher than the largest file will be (what still is a bit a pitty if there are random files as large as 100gb, which cuts 10% off from a 1tb drive) - BUT it would be nice to know if the setting is in bytes, kilobytes, megabytes, etc.pp.

 

one last addition: "min. free space" really did it, and it seems to count in bytes counts in kilobytes; so for the "fill up" setting, this really needs to be carefully set for each share, taking the largest possible file into account...

 

g

hi there!

 

i have a problem with my new unraid pro box: i've set up some shares to "fill up" because they are meant for backups that a) seldom changes and b) even less often needed to be read; now if there is say 4gb left on the first drive, and i'll try to copy a 8gb file from my windows 2008 r2 server (using dirsync or standard windows copy) it still starts writing to this disk leaving all other (still empty) disks aside; of course the copy process fails - but after a long, long time, while the speed drops to nearly 0 if i use windows copy. dirsync somehow manages to copy the next file already while disk 1 has 0b left (looks like the copy-process overlaps a bit) and this seems to direct it to the 2nd disk - but still only every 2nd file gets copied, because the used space of the partly copied (and failed) file ist released soon afterwards.

 

this isn'nt meant to be working like that, isn't it?

 

thanks in advance for every helpful answer - didn't find any clues using search and manual (or i'm blind)

 

ps: split level is set to 9, and the file is on the 3rd level...

 

pps: i found there is a "min. free space" setting for each share, which may do the trick, if set higher than the largest file will be (what still is a bit a pitty if there are random files as large as 100gb, which cuts 10% off from a 1tb drive) - BUT it would be nice to know if the setting is in bytes, kilobytes, megabytes, etc.pp.

 

one last addition: "min. free space" really did it, and it seems to count in bytes; so for the "fill up" setting, this really needs to be carefully set for each share, taking the largest possible file into account...

 

g

I think it is kilobytes.

pps: i found there is a "min. free space" setting for each share, which may do the trick, if set higher than the largest file will be (what still is a bit a pitty if there are random files as large as 100gb, which cuts 10% off from a 1tb drive) - BUT it would be nice to know if the setting is in bytes, kilobytes, megabytes, etc.pp.

 

one last addition: "min. free space" really did it, and it seems to count in bytes; so for the "fill up" setting, this really needs to be carefully set for each share, taking the largest possible file into account...

 

g

I think it is kilobytes.

 

hm; i set it to a whopping 20000000 - what would render a terabyte drive unusable if that where kilobytes. so i still tend to believe it is in bytes...

 

it IS kilobytes  

thanks for the hint...