Question: split level and available space conflicts

[theone]

Hi,

 

What happens if split level is set to 1 (for example) and the available space on a certain disk is too low to add the new data to the raid - under the split level restrictions?

 

Where does the data go to?

 

What if the split level is set to 0?

 

Does the server report not enough space? or does it save data to another disk and overrides the split level restriction?

 

Anyone?

 

[lionelhutz]

It should fail to write.

 

Peter

[theone]

In both cases?

 

So any split level can at some point cause write fails due to not enough room in certain disk although more room is available in another disk.

 

Is this true?

 

[Joe L.]

In both cases?

 

So any split level can at some point cause write fails due to not enough room in certain disk although more room is available in another disk.

 

Is this true?

 

Correct.  It is up to the program copying to deal with it. It is why you should probably be aware of the space needed and why many of use do not use user share when copying large amounts of data to the server, but use the disk shares instead.

 

Many windows programs start with a zero length file and append to it when copying.   The zero length file will almost always fit. The total size will often not fit if you are set up incorrectly.  IT is why there are "min free settings" for each user share.  The "min-free" should be set so any given single file will fit.  If you are copying 8Gig files, you should set the min-free to 9Gig.

[lionelhutz]

Split level = 0 is actually a special case. You manually create the directory structure and then unRAID will fill it. If you are copying to \\Movies\Horror and you have created Horror directories on 3 disks then unRAID will use all 3 disks.

 

Peter