June 11, 201313 yr I just upgraded my unraid hardware and am running 5.0rc12. I changed my shares from high water to fill-up method instead but now when the mover tries to move anything on the cache drive it makes it attempt on my first drive, finds that it is full and then quits completely. If I try to change the share back to high water it still does the same thing - I have no idea why this is happening? I now wish for them all to be back on high water but for some odd reason when the mover script is invoked, it errors out with drive space unavailable - and it always makes it's attempt to write to my first drive. Not sure why this is happening.
June 11, 201313 yr It might be worth giving details of the Split Level you are using and the pathnames that are failing? Split Level overrides allocation method so it is possible it is the path name that is prohibiting the file from being placed on the other drive.
June 13, 201313 yr The disk is not included in the share or it is excluded from the share. There is a global config and a per share config. The safest thing is to make all of the excludes and includes blank.
Archived
This topic is now archived and is closed to further replies.