Not sure if I am posting to the right place, but I am running 4.5.3.

 

I recently started using a cache disk and just noticed that on a drive I use exclusively as a download location (/mnt/user/downloads on disk 14) I had user shares that didn't belong with recently copied content.  I have 3 directories which explicitly exclude disk14.  What even more bizarre is that the split level is not obeyed, I have files in the first level directories split among multiple disks even when split levels are set to 1 on all those drives.

 

Any ideas on how I can troubleshoot this the right way?

 

Thanks.

 

G

Well I posted about a similar problem and emailed Limetech and got no response. I'm using disk shares right now even though it sucks using multiple disk shares compared to 1 user share.

 

Peter

Well I posted about a similar problem and emailed Limetech and got no response. I'm using disk shares right now even though it sucks using multiple disk shares compared to 1 user share.

 

Peter

Please post a link to that thread.

 

EDIT: nevermind, I found it.

Thanks for the reply.  It happened again.  I deleted everything in the share on the excluded disk (e.g. \\tower\mnt\disk14\Movies\ which shouldn't have ever existed since this disk is excluded).  Then I copied content user share \\tower\Movies\ and waited for Mover to do it's things (and I did confirm that disk14 was in the exclude list for the Movies user share).  When the scheduled time came Mover had moved the new content to disk14 again. This is a big problem for me...

Thanks for the reply.  It happened again.  I deleted everything in the share on the excluded disk (e.g. \\tower\mnt\disk14\Movies\ which shouldn't have ever existed since this disk is excluded).  Then I copied content user share \\tower\Movies\ and waited for Mover to do it's things (and I did confirm that disk14 was in the exclude list for the Movies user share).  When the scheduled time came Mover had moved the new content to disk14 again. This is a big problem for me...

 

There should be a file on the flash called 'config/shares/Movies.cfg'

Please post the contents of this file.

Here you go, thanks...

 

# Generated settings:

shareExport=e

shareExportNfs=

shareComment=

shareValidUsers=

shareInvalidUsers=

shareExceptions=

shareInclude=

shareExclude=disk2,disk13,disk14

shareUseCache=yes

shareAllocator=highwater

shareSplitLevel=1

shareFloor=0

 

 

Disk 14 is the one that is being written to by Mover even though it is excluded.

I too noticed this occuring.  I have excluded one disk from my movies share but when the Mover Script runs, it is placing some movie files on the excluded disk.  

 

Do we need to populate both the include and exclude fields??  I only have the exclude disk filled in as I do not mind that the movies go on any disk but one, so I excluded that one.

 

I am using 4.5.4.

 

Thanks

I tried to populate both the include and the exclude fields for my Movies Share and my excluded disk was still populated with movies by the mover script.

 

Thanks

Funny, I tried the same thing, with the same result...  Hope this gets fixed in the next version...

Seems to be only the exclude portion that does not work.  I nixed the exclude field and only populated the include field and all was well.  I only have 6 disks so its no biggie type in the few include disks.

Good find.  I didn't think to try that, I just set that up for one of my problematic shares.  I have 14 disk so it was slightly annoying but not too bad.  Thanks for the idea.  Will see if it works.

Spoke too soon!    I noticed movies on my excluded disk today.  Using only the include did not work with the mover script.  And since I am on that topic, I posted another thread under Forum Feedback (http://lime-technology.com/forum/index.php?topic=6453.0) (May be the wrong spot), mentioning that I am unable to disable the mover script from the Web GUI.

 

Whenever I select disable and then apply, page refreshes and the dropdown reflects enabled.  I figured maybe the dropdown was just saving the correct value and the script actually stopped but it did not stop.

 

I am using 4.5.4

Yeah, you're right, I had some stuff move correctly, but some if just back on the "non-included" drive (as opposed to explicitly excluded).  This is very annoying...

I can not reproduce this behavior, but perhaps I need more details.

 

There is a case where files/directories will be created on a disk, despite what the excluded/included masks indicate.

 

The case is where the parent directory already exists on a certain disk, and that directory is "unsplittable".  Here is an example:

 

Suppose we have this state:

share: Movies

split-level: 1

excluded:

included:

 

(ie, excluded/included masks are not set to anything).

 

disk1

Movies

 m1

  file1

disk2

Movies

 m2

  file1

disk3

Movies

 m3

  file1

 

So under 'Movies' we see:

m1

m2

m3

 

Let's say we now set 'excluded=disk2', and we create Movies/m2/file2

 

Well Movies/m2 is an 'unsplittable' directory (because split-level is 1).  So even though we are excluding disk2, Movies/m2/file2 will still get created on disk2 because the parent directory of the file we're trying to create is 'm2' and already exists on disk2.

 

Edit: just to amplify a bit... suppose the free space is as follows:

disk1: 150

disk2: 200

disk3: 100

and,

excluded=disk2

allocation method=most free

 

Suppose we create the folder "Movies/m4".  Since the parent directory of 'm4' is 'Movies', and 'Movies' is at level 0 in the share heirarchy, and split-level is 1, 'm4' could potentially be created on any disk.  With allocation method 'most free' ordinarily this would be disk2, but since disk2 is excluded, the next disk with the most free space is disk1, so 'm4' will be created on disk1.

 

---

So... I would like to see an example of a file, including it's complete path, that exists on the cache disk, which ends up getting created on an excluded disk.

 

I just started my unraid system so in my case, disk 1 is the only disk that holds the Folder "Movies".  But I think what may be happening is the movies are moving to the excluded disk because it happens to be the current disk in use by other files being copied.

 

For example, I have 6 disks (1 parity, 4 data, and 1 cache).  I have Parity, disk1, disk2, disk3, disk5, and cache in use.  Disk 4 slot is not used.

 

I have "Movies" allowed to be on disk1-3 with a splitlevel of 1 and using HighWater.  I have "TempCopy" only allowed on Disk5 with a splitlevel of 0 and using HighWater.  Any files in "TempCopy" always only show up on disk5 but files in "Movies" will also show up on disk5 even though disk5 is not part of the include for "Movies".  So maybe since it is already copying files to disk5 from "TempCopy", rather than spinup another disk it moves "Movies" to disk5.

 

I attached the share cfg files for "Movies" and "TempCopy".  I am not sure what you are wanting me to attach to show you an example of a file that was on cache and then gets moved to a disk not in the include.

 

My share cfg files are no longer using the exclude option at all and I am simply only specifying the include disks and yet, "Movies" are still moving to a disk not in the included disks.

Movies.cfg

TempCopy.cfg

mace-

Try this... using windows explorer, go to the cache disk share and create the 'Movies' folder; then create a folder within Movies named 'test'; and within 'test' create, say, a text file.  So on cache disk you have:

 

Movies/test/file.txt

 

Now go to Shares page and click 'Move now' button.  Where does Movies/test/file.txt get moved to?  Should not be disk5.

 

 

Ok, so I did what you suggested and the "test" folder got moved to its correct place on disk1.  So now that leads me to believe that the issue is connected with using the mv command to move files around.

 

As I mentioned in my previous reply, I have a "Movies" share and a "TempCopy" share.  "Movies" is allowed  on 1-3, and "TempCopy" is allowed on 5.  I rip all my movies to "TempCopy".  Once I get a few built up, I login to Putty and do a mv command to move all files from "TempCopy" to "Movies".  It is faster to move files this way rather than using Windows Explorer to move large amounts of data.  The command I use is: mv /mnt/user/TempCopy/DVDFab/mkv/* /mnt/user/Movies/

 

So since I have cache implemented, this really places my "TempCopy" files to the cache disk and then I let the mover script move everything over night to their appropriate disk.  The movies always end up on disk 5 as well as any tempcopy files that I had not yet moved to "Movies".

Ok, after doing more research from realizing what you suggested worked, I have found how to re-create the issue.

 

The issue, in my case, is not the mover script but the mv command.  For example, last night 11 movies in my "TempCopy" share got moved to disk5 as they should.  This morning I did another movie rip and it was in "TempCopy" on the cache disk.  I executed the mv command to move from "TempCopy" to "Movies": mv /mnt/user/TempCopy/DVDFab/mkv/* /mnt/user/Movies/

 

I then ran the mover script from the web interface.

 

The result was any movie that was in the "TempCopy" on disk5 was placed in a newly created movies folder on disk5.  The one rip that was in "TempCopy" on the cache, correctly got moved to disk1 movies.

 

So I am not sure how this would be corrected but if I am moving files from one share that is only allowed on disk5 to another share that is only allowed in disk1-3, they should move correctly and not hold the original include values, which in this case, they were only allowed on disk5 in the "TempCopy" share and the files held that value and created a new folder called movies on disk5 and moved them there instead of moving to a movies folder on disk1-3.

 

I wish I could provide a solution and not just a problem, lol =)

Yes the "problem" is with the way the 'mv' command works in conjunction with user shares.  What's happening is that, if both source and destination are in the same file system, 'mv' actually executes a "rename" (a bit more complex than that, but point is data is not actually moved).  Since /mnt/user/TempCopy and /mnt/user/Moves are in the same file system, this is what's happening.

 

You could disable the mover and use this command instead:

mv /mnt/cache/TempCopy/DVDFab/mkv/* /mnt/user/Movies/

 

Or you could modify your mover script to put the above command right after the line:

echo "mover started"