June 13, 201610 yr Hello all, I need help trying to solve an issue with a couple of my shares and understanding the Mover function. Sorry if this appears to have been covered several times before but I what I've read in other threads didn't seem to help whatsoever. I have two shares that are reporting this warning: One called "Archive" and the other "appdata". The Archive share was originally created to NOT use cache. However, at one point, it was enabled then later disabled. I read through some of the threads here and tried a few different solutions. First, I tried using the "Move" button which didn't do anything. Tried waiting a few nights to see if it would go away. Then I tried creating a new share and COPYING the files and deleting the old shares to no avail. The new share shows that it's using 0B on the cache drive. The Appdata share is set to use cache but as I understand it, contents are supposed to be moved nightly or by manually evoking the mover with the move button. Is this correct? When I read that, I decided that I would like my Archive share to use cache after all as I keep a photo library on there that I use regularly (Photoshop Lightroom) if it means better throughput. Does it? This is my first unRAID box (built in Jan 2016) 10 Drives including parity + 1 cache drive. v: 6.1.9. Any help that I could get on any of this would be greatly appreciated. Thank you!
June 13, 201610 yr Community Expert Typically appdata is set to Use cache disk: Only because you don't want its files moved off cache. Moving appdata files will usually break your apps. If a share is set to Use cache disk: No, that means any new files written to the share will not go to cache. It also means mover will skip the share so any files for the share already on cache will not be moved. If a share is set to Use cache disk: Yes, then new files written to the share will be written to cache, then moved at the schedule time. You can also invoke mover manually with the Move now button. Share settings are covered in the Help which you can turn on by pushing the Help button at upper right. Also recommend you install "Community Applications" and "Fix Common Problems" plugins.
June 13, 201610 yr Author If a share is set to Use cache disk: No, that means any new files written to the share will not go to cache. It also means mover will skip the share so any files for the share already on cache will not be moved. If a share is set to Use cache disk: Yes, then new files written to the share will be written to cache, then moved at the schedule time. You can also invoke mover manually with the Move now button. If this is the case, my log files show that my appdata share (which is set to Use cache disk: Yes is being skipped by the mover. logger: skipping "appdata" Share settings are covered in the Help which you can turn on by pushing the Help button at upper right. I've read through this. However, things aren't working the way they're supposed to. Also recommend you install "Community Applications" and "Fix Common Problems" plugins. This is installed and I get " No Warnings Found"
June 13, 201610 yr This is installed and I get " No Warnings Found" Unless there's a coding mistake by me, that means that no files on a cache-only share exist on the array, and no files on an array-only share exist on the cache drive.
June 14, 201610 yr Author Post diagnostics Attached! Thanks guys! unRAID-diagnostics-20160613-2017.zip
June 14, 201610 yr You're the best: You ran FCP and went into CA Backup prior. Tells me tons about those three shares: appdata share appears to be cache: only (and only exists on the cache drive) (and this is confirmed by you going to CA's appdata backup module and it didn't mention in the logs about appdata being an invalid source) archive share appears to be use cache:no, but only the folder itself (no files/folders within it) exist on the cache drive -> confirmed by ca backup bitching about it not being a valid source -> which is a minor bug because fix common problems didn't complain about it (and fcp has a more refined test) archive_old share is set to use cache:no, but only the folder itself exists on the cache drive itself (same as above) All three of those folders mover will skip properly This is at the end of the logs Up further (The day before), you ran FCP and it found problems with Archive and Archive-old which you've fixed by moving the files around yourself At least you found a small bug in CA
June 14, 201610 yr Author appdata share appears to be cache: only (and only exists on the cache drive) (and this is confirmed by you going to CA's appdata backup module and it didn't mention in the logs about appdata being an invalid source) archive share appears to be use cache:no, but only the folder itself (no files/folders within it) exist on the cache drive -> confirmed by ca backup bitching about it not being a valid source -> which is a minor bug because fix common problems didn't complain about it (and fcp has a more refined test) archive_old share is set to use cache:no, but only the folder itself exists on the cache drive itself (same as above) All three of those folders mover will skip properly This is at the end of the logs Up further (The day before), you ran FCP and it found problems with Archive and Archive-old which you've fixed by moving the files around yourself At least you found a small bug in CA Sorry, I'm still very confused. What can I do about these shares "not being a valid source" and/or about mover skipping them??? Is mover not working for me? Not sure what I should do at this point. Not sure how CA Backup affects my shares being protected or mover executing properly. Sorry if I'm not understanding. Thanks for your help.
June 15, 201610 yr CA backup doesn't affect mover at all was merely pointing out the organization of the folders based upon what CA and fcp logged. And as I stated all 3 of those folders are going to be skipped by mover. If you want mover to touch them you have to adjust your use cache settings for those shares Sent from my SM-T560NU using Tapatalk
June 15, 201610 yr Author OK. So, I just created a test share, set it to use cache: yes, copied 4 PDFs in there, looked at the log and saw that the PDFs were moved properly. However, the orange warning still appeared next to the test share. I then browsed the share's content via the unRAID web GUI and noticed that they were now on Disk1 except for a hidden folder (".AppleDB" which I think MacOS creates). A hidden file: ".DS_Store" was moved with the rest of the PDFs. Is there a way to have the mover move those files/folders as well? Is this a permissions issue?
June 15, 201610 yr the orange warning still appeared ... And it always will for a single cache drive. Files/folders on the cache drive are not protected from a failure of the cache drive whether they are permanently there (no mover) or temporarily there (waiting for the mover). It's not protected like the array. That is normal and a correct warning. I am not sure if the warning goes away if you set up the cache as a pool of drives but that is how you might mitigate any potential failure.
June 15, 201610 yr I am not sure if the warning goes away if you set up the cache as a pool of drives but that is how you might mitigate any potential failure. I can confirm that it does. If you have a cache pool those directories are treated as protected. That said, I'm mixed on cache pools (running one myself) because it's not well documented, and people have had trouble recovering data / stability issues.
June 16, 201610 yr Author And it always will for a single cache drive. I was referring to a share on the raid that's set to use the cache drive. I ended up telling my MacOS clients to not write these files to network shares.... https://support.apple.com/en-us/ht1629 This definitely did the trick. Now after I write files to my share, it changes to green after the mover runs at night (or I manually run it). I also had to delete the actual folder (with the name of the share) from the cache drive. I am not sure if the warning goes away if you set up the cache as a pool of drives... It does. My friend has a cache pool setup and all his shares (including appdata) are "protected". I ended up setting up Backup appdata. Everything seems ok now. Other than having some file corruption on a Lightroom library. But that's another story. Just want to thank you guys for the knowledge and help! Much obliged.
Archived
This topic is now archived and is closed to further replies.