User Share does not expand to next disk in array

[matty2k]

Dear folks,

 

I am new to unraid and just set up my first server. Now trying to copy my files from my existing synology NAS via mounted SMB share to the unraid user share on my array. Unfortunately I am running into problems, because the share does not expand to the next disk when the first disk is full. I started with 6.10RC1 and hope it is not a related problem to the RC. I first had built the array with 2x 16 GB Toshiba HDD (data and parity) and later on expanded with another 8 TB Toshiba disk. The user share was configured before I expanded the array ... only if this does matter, but from my understanding Unraid would use every additional disk as needed (if share is configured correct).

 

Share structure is:

 

movies => resolution => movie name => files

Split level is set to two ... I already tried with 3 .. 

 

Hope for help

Kind regards

 

matty

 

 

 

 

nasa-diagnostics-20210823-0816.zip

[ChatNoir]

Probably because file transfer generally first create the directories and your splitlevel makes it that the share want to keep everything together.

[itimpi]

Your example path definitely requires a split level of at least 3 to give the results you want as a value of 2 forces UnRaid to try the first disk.  Since you are using the ‘Fill-Up’ allocation method I do not see any advantage to putting any Split Level restrictions on the share unless I am missing something about how you want files split accross drives

 

[matty2k]

Thank`s for the quick answers, I will try with split level 3.

What I woul like unraid to do if I copy files from a destination (in this case the mounted smb share) is to fill up the first disk, when the first disk is full, then copy to disk2 and so on .. 

Therefore the split level .. but perhabs my understanding is not correct for this.

 

regards

[itimpi]

54 minutes ago, matty2k said:

Thank`s for the quick answers, I will try with split level 3.

What I woul like unraid to do if I copy files from a destination (in this case the mounted smb share) is to fill up the first disk, when the first disk is full, then copy to disk2 and so on .. 

Therefore the split level .. but perhabs my understanding is not correct for this.

 

regards

 

Split level always wins any contention over which drive to use.  This means it can force a file to a drive that does not have enough room.  I would suggest that you set the Split Level to "Automatically split any directory as needed".   

 

Split Level restrictions really only make sense if using one of the other allocation methods as a way to keep related files on the same drive, with "Fill-Up" this is will happen anyway.

 

There is a good explanation of Split Level here in the online documentation that can be accessed via the Manual link at the bottom of the Unraid GUI.

 

[matty2k]

Ok. I have read the information before, but obviously did not fully understand the logic. Let me clarify:

 

Do I need to create the user share folder(s) or better say the complete file structure on each disk manually?

 

Or does Unraid create the user share file structure for me if needed, e.g. disk1 is full and need to go on writing on disk2?

 

it ist a little bit confusing since I am used to work with Raid system where you do not need to manage the file structure on every single disk separately.

 

kind regards and thanks again.

[itimpi]

1 hour ago, matty2k said:

Ok. I have read the information before, but obviously did not fully understand the logic. Let me clarify:

 

Do I need to create the user share folder(s) or better say the complete file structure on each disk manually?

 

Or does Unraid create the user share file structure for me if needed, e.g. disk1 is full and need to go on writing on disk2?

 

it ist a little bit confusing since I am used to work with Raid system where you do not need to manage the file structure on every single disk separately.

 

kind regards and thanks again.

If you turn of set any Split level restrictions then Unraid will create directories as needed on each disk as it fills up.  No need for any manual intervention.

 

With Fill-up allocation method the only Share setting that would then matter regarding drive selection is the Minimum Free Space value to act as the trigger for moving onto the next drive.

[matty2k]

OK. Did try to change split level to 3 again, but still does not work. Minimum Free Space is still set to 90GB but however, Disk1 is written completely full and Unraid does nit switch to disk2!

[itimpi]

2 minutes ago, matty2k said:

OK. Did try to change split level to 3 again, but still does not work. Minimum Free Space is still set to 90GB but however, Disk1 is written completely full and Unraid does nit switch to disk2!

Why not change Split Level to allow any number of levels?    If any of the paths have more folder levels than was shown in your screen shot then split Level=3 would still be too restrictive.

[matty2k]

Hi,

I now tried again with split level=split as needed but behavior is the same, krusader fills completely up disk1 and does not jump to disk2. Stops with error not enough space! Really annoying.

[itimpi]

Does it work over the network?    If so what are the settings for your Krusader volume mapping?

[matty2k]

Actually only try via network .. copy from mounted network smb share (synology share) to unraid.

Does krusader get the changes correct without restarting when I change share settings in unraid while krusader is running?

What settings to you need to know? The picture shows the settings I used following the video from spaceinvader.

Everything else is unchanged.

 

[itimpi]

I meant try running the copy from a machine that is not the Unraid server to try and eliminate any variables.  
 

Nothing obviously wrong with those Krusader settings though.

 

I am sure the solution will eventually be something trivial - the problem is going to be spotting why it is not already working.

 

it might be worth posting new Diagnostics so we can check your current settings.

 

[matty2k]

OK. Here we go, latest diagnostic file attached.

I will try to initiate copy to unraid server from mounted share at my synology NAS later on.

nasa-diagnostics-20210824-0853.zip

Edited August 24, 2021 by matty2k

[matty2k]

OK. I have now mounted the Unraid Usershare on my Synology NAS and copy the files from Synology to Unraid. And indeed - now unraid is writing to disk2 when limit of free space is reached. Another difference is that I created a user to access the share from Synology NAS ... (with Krusader I did not need to add any user).

However, somewhere seems to be an problem - with Krusader or unraid itself.

Would still like to know, where the problem is originated.

 

kind regards

 

Quote

 

 

[itimpi]

47 minutes ago, matty2k said:

OK. I have now mounted the Unraid Usershare on my Synology NAS and copy the files from Synology to Unraid. And indeed - now unraid is writing to disk2 when limit of free space is reached. Another difference is that I created a user to access the share from Synology NAS ... (with Krusader I did not need to add any user).

However, somewhere seems to be an problem - with Krusader or unraid itself.

Would still like to know, where the problem is originated.

 

kind regards

 

 

Glad to hear you ‘sort’ of got it working.

 

No idea why it is not working for you from Krusader - lots of people use that without the problems you seem to be encountering.

[matty2k]

Any relation to RC1 perhabs?

[itimpi]

40 minutes ago, matty2k said:

Any relation to RC1 perhabs?

I don’t see how it could be.    If it works over the network it should also work locally (I.e. using Krusader) as the same disk selection logic would get invoked.