I’m using SnapRAID with Drivepool and recently did a rebalance as I realized I didn't leave enough space % in the "Prevent Drive Overfill" Balancer. Everything seemed to move correctly, and the drives were now balanced as I wanted. I ran the SnapRAID "sync" command and thought I was good to go. A few weeks later, I see that over a hundred files are missing including complete folders.
I ran the SnapRAID "diff" command and see 175 removed differences- these are the missing files which are apparently still a part of the parity. What is the best way to restore these files and folders? Does "fix -m" simply solve my problem, or will it attempt to restore directly to the drives the files and folders were previously on? If so, does that cause a conflict with the Drivepool balance settings as I know if those files and folders are restored to the previous drives, it will be over the balance limit.
Question
murphdogg
I’m using SnapRAID with Drivepool and recently did a rebalance as I realized I didn't leave enough space % in the "Prevent Drive Overfill" Balancer. Everything seemed to move correctly, and the drives were now balanced as I wanted. I ran the SnapRAID "sync" command and thought I was good to go. A few weeks later, I see that over a hundred files are missing including complete folders.
I ran the SnapRAID "diff" command and see 175 removed differences- these are the missing files which are apparently still a part of the parity. What is the best way to restore these files and folders? Does "fix -m" simply solve my problem, or will it attempt to restore directly to the drives the files and folders were previously on? If so, does that cause a conflict with the Drivepool balance settings as I know if those files and folders are restored to the previous drives, it will be over the balance limit.
Any help is greatly appreciated!
2 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.