I've been using unRAID since 4.7 and have my Movies share configured since day 1.

 

I'm currently in the process of migrating from reiserFS to XFS, and am seeing some weird things.

 

disk12 is my new 4TB drive that is currently formatted XFS. I'm migrating the 4TB disk5 to disk12 so I can reformat disk5. I've globally excluded both disk5 and disk12 from all shares (Settings | System Settings | Global Share Settings). I went to watch a movie last night, only to discover that there was something wrong with the encode (wife = disappointed). Today, I went to investigate, and discovered a very weird distribution of files across my drives.

 

The "Movies" share is configured to "Automatically split only the top three directory levels as required" (Image 1). I'm pretty sure that this is how it's always been set.

 

As you can see, however, from the 2nd and third attachments, it seems that the movie Memoirs of a Geisha has actually been split across 4 disks. (Images 2 & 3)

 

As I understood it, the "split level" was from the named share downwards. So in this example:

+ Movies

|+ Movie A

||+ Subfolder A

|||+ Sub-subfolder AA

||+ Subfolder B

|||+ Sub-subfolder BA

|+ Movie B

All directories under Movie A would be kept on one disk because Movie A, Subfolder A, and Sub-subfolder AA were 3 levels of directories, and they would be kept together.

 

It appears, however, that /mnt/user are included in the count of directories, because files and directories below Movies are being split anywhere.

+ Movies

|+ Memoirs of a Geisha (2005)

||+ extrafanart  disks 4 & 11

||+ extrathumbs disks 4 & 11

||+ *.mkv disk 4

||+ *.nfo disk 6

||+ *-fanart.jpg disk 5

||+ *-poster.jpg disk 5

 

I can think of 3 possibilities:

• 1. Share splitting is broken and nobody's noticed yeah, right
  
• 2. Share splitting doesn't work the way I understand it to likely
  
• 3. Disks were really full when these files were written so it was forced to split them further possible

 

Also, a final point of confusion, and this may actually be a bug in WebGUI:

When I went to user shares, clicked on the folder icon next to Movies, then browsed to the Memoirs of a Geisha directory, why are the two *.jpg files that are on disk5 not shown? I understand that disk5 has been globally excluded from shares, but I thought that was only for new writes, and that any existing files anywhere on any disk would still be reported back to the users as being there. As you can see from the 4th attachment, they're not being reported via SMB to Windows10, either.

 

What am I missing?

Your allocation method is "Fill-up". When you save a file it is simply stored on the lowest numbered disk that has more than the designated Free Space for that user share available; in your case, 10 GB.

 

I could buy that, but that means that when it came time to write these files, it found 5GB on disk4, but only ~900KB on disk 5 and had to put the remaining 23KB on disk 6? That doesn't make much sense.

 

Actually, that makes no sense at all. If there was more than 10GB (my minimum setting) available on disk4, there would have been enough room for the 5GB .MKV file plus the <1MB for the .JPG & .NFO files.

 

You're also implying that Fill-Up overrides the split level?

I think you have got Split Level backwards!  It starts at the top level (not the bottom level) so in your example with a Split Level of 3 the movies, movies A, and subfolder A could be split across multiple drives, and I think this is what you are seeing?