Hi,

 

I am not sure if this is a bug or user error. Here is my setup and I will explain what I am experiencing below.

 

Share name: Data

Allocation Method: Fill-Up

Included Disk: Disk1

Export: Export read/write

 

Share name: Movies

Allocation Method: Fill-Up

Included Disk: Disk2

Export: Export read/write

 

Share name: Music

Allocation Method: Fill-Up

Included Disk: Disk2

Export: Export read/write

 

Under Windows My Computer, I mapped T:\\Tower\Data, U:\\Tower\Movies\ & V:\\Tower\Music

I setup my all my disks such that all Data will go to Disk1 and all Movies and Music files will go to Disk2.

 

Problem#1:

When I copied some movie files to my share mapped drive U:\\Tower\Movies, the files actually got saved in Disk1 under a new "Movie" folder (created by unRaid).

 

Problem#2:

Now I also see "Music" folder created in Disk1 with 7 song albums folders. These songs that I didn;t even play on the computer. All the song folders have only one file which is a "Thumbs" 9kb in size.

 

I started off with only Data folder in Disk1 but now I have Data, Movies and Music.

Disk2 is still the same with Movies and Music folders.

 

Has anyone seen this before? Thanks for responding!

I believe you have to specify both included AND excluded disks for a share.  So your data share should include disk1 and exclude disk2, and your movies/music shares should be the opposite.

 

Also, I've read a few reports of the 'fill-up' disk allocation method being broken or at least buggy.  Try using 'high-water' instead.  In your case it won't matter anyway since each of your shares only spans one disk.

I believe what Rajahal said is correct.  There is something weird with Fill-Up that makes it so both include and exclude disk have to be specified.  Lime-tech has commented that this is not the way it is supposed to be and he is looking to fix it (hopefully in a 4.5.7 and not just in 5.0b3).

 

I have always specified both include and exclude disks so I have never run into this problem.

Thanks Rajahal and prostuff1! I will try out both methods.

Update to this post.

 

I tried both method suggested here:

Share name=Music

Allocation method=High-water

Included Disk=Disk2

Excluded Disk=Disk1, Disk3

 

When I save new music folder to my "Music" share, the files are appearing in Disk1.

 

So, I cleanup my Disk1 and left only "Data" Share, moved all the new music folders back to Disk2. I then created a new "Test" folder under Music share. When I looked at Disk1, "Music" folder was created and now I have 42 other folders (with nothing in it) in it together the new "Test" folder. I actually have over a hundred music folders in Disk2 but only 42 blank ones were randomly created in Disk1.

 

I think this is a bug. Anything else I can do?

Thanks!

I have had something similar where the fill-up method did not respect the split level.

 

Try putting in a split level of either 0 or 1 and see what happens.

 

0 says that the child directory is only created on a drive where the parent directory already exists.

1 says that the top level share can not be split between drives.

 

Another thing to try is clear out the extra directories on disk1, set the user share correctly and then reboot before trying to use the server again. Shut down any media playing software since those files you are seeing commonly come from WMC or WMP.

 

Peter