February 5, 201610 yr now that's original: unraid is now saying i have some "spillover", some "leakage" with some of my shares. when i reinstalled unraid, i momentarily ended up with my shares using "all drives"; this was rectified, but not before copying some files on the server, only for said files to end up on a drive that is not part of any the shares i supposedly copied to. so, my "drive 4" had some files that were not supposed to be on it. so i copied the files off the server, deleted them so that said "drive 4" would no longer be used, and after a reboot, discovered that unraid still thinks it's part of other shares. see partial screenshot below: my question is how do i tell unraid to "forget" about "drive 4" so that i can copy the files back onto their respective shares, only residing on the drives assigned to said shares? thanks.
February 5, 201610 yr go into terminal and check the contents of /mnt/disk4/ (I guess you can do this the GUI as well) What I think you'll find is that a folder with that share name still exists at /mnt/disk4/foldername/ ... if that folder is empty delete it and then it should stop writing to disk4. If that folder is not empty, move the data on it to a different disk, then delete it. Edit: Adding a bit more explanation. Include / Exclude only prevent unRAID from creating content on the disks that are excluded or included respectively. The way it does this is by preventing the creation of the share folder on that disk. If that folder already exists it won't prevent it from being created and won't delete it...
February 7, 201610 yr Author reading your reply, i'm going "this is so obvious, why didn't i think of that?". you were right, i did have three directory trees on "disk4" with the share names as their respective root names. just as you described. anyway, after verification, i deleted those trees and, long story short, no more "spillover". problem solved! thanks a lot. :-) /bm
Archived
This topic is now archived and is closed to further replies.