Fill-Up share changed to High-Water [Solved]

[Gwendolyn Parker]

Hi Everyone. I'm a total newbie. I successfully set up an unraid server with 3 disk of which one is parity (3x 14Tb shucked WD).

 

I created a share with Fill-Up option enable. Perhaps I misunderstood how it works.

I copied my media library over to the share but after a little less of 14 tb transferred, I got a disk full error, although the 2nd data disk is less than 1% full.

I expected a similar folder structure was created on 2nd disk and the  transfer to continue. But no joy.

 

I switched the share allocation method to "High Water" and rebooted hoping that it would solve the problem, but again... no luck.

 

I have a qbittorrentvpn docker running in the background. Other than that everything is stock.

 

 

Edited September 22, 2020 by Gwendolyn Parker

[trurl]

There are other things to consider besides allocation method. 

 

Go to Tools-Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post. 

[civic95man]

Maybe need to set the minimum free space to a larger value? Something greater than the largest file anticipated to be transferred

[trurl]

12 minutes ago, civic95man said:

minimum free space

split level has precedence so 

18 minutes ago, trurl said:

other things to consider

 

[Gwendolyn Parker]

Wow. You guys are lightning fast ! Okay I'm on a steep learning curve. Never touched anything Linux before.

note to self: Always send diagnostics

 

Here they are !

tower-diagnostics-20200713-2029.zip

[itimpi]

Your problem is almost certainly the Split Level setting.   With a value of 1 any file whose path is more that one folder deep will be constrained to the drive where that folder is first created.  As was mentioned Split Level takes precedence in the event of any contention between the Share settings for choosing the drive for a file.

[Gwendolyn Parker]

Thank you ! This solved my issue.

 

I reread the help and got it right from what you clarified. What I understood is that setting it to 1 would keep all that is 2nd level directories and below on the same drive, but it works the other way around it seems. Could you provide a use case in which the non automatic split level is necessary/useful ? Just for my knowledge.