Posts by jollyrogr

Quote from 1activegeek

It is probably set somewhere later in the script and/or is not present in your script because you have not set this anywhere. The script should check for the presence of that variable and then use it in comparison to the SCRUB_FREQUENCY variable later in the script. If you haven't set this variable in your SnapRAID config, it's probably not populated yet and thus the message you see about setting it to 0.

Where are you supposed to set the variable? There's no option in the plugin. What I'm saying is that it appears to me that the plugin setting that sets "SCRUB_FREQUENCY_IN_DAYS" should really be setting "SCRUB_OLDER_THAN_DAYS". But that's just my opinion, I could be wrong.

I think I found an issue with the omv-snapraid-diff script.

[2017-01-24 04:30:01] omv-snapraid-diff: INFO: 'SCRUB_OLDER_THAN_DAYS not set in '/etc/snapraid-diff.conf''
[2017-01-24 04:30:01] omv-snapraid-diff: INFO: 'set it to 0'

but /etc/snapraid-diff.conf looks like this:

this file was automatically generated from
# openmediavault Stone burner 2.2.13
# and 'openmediavault-snapraid' 1.5


SYSLOG="true"
DEBUG="false"
SENDMAIL="true"
RUN_SCRUB="true"
SCRUB_FREQUENCY_IN_DAYS=7
DEL_THRESHOLD=10
SCRUB_PERCENT=100

It seems the script is referencing a variable in snapraid-diff.conf that doesn't exist. I can't simply change snapraid-diff.conf since it says that it's generated by the plugin.

Quote from Lukas52

From my experience you need to delate the content file after you have reconfigured your Snapraid, no need to move it, just delate the one you dont need after the new one was created.

As far as i know the diff command doesnt update your parity information, it only lists the files that have been chanced since your last sync, but i have no idea what the OMV diff-script is actualy doing, since at least the OMV 3 Version of the plugin doesnt seem to work as its supposed to anyway.

In theory the two parity drives should be enough to recreate your two data drives, but im not 100% sure about that.

Thanks for your reply. I'm using OMV 2.1. Do most folks use the default delete threshold of 0? Suppose I have deleted some files, then I would have to do a manual sync before the cron would do a sync, right? Is that what everyone does? Also should I run a snapraid touch command to set subsecond timestamps?

I have some Snapraid questions.

My setup is 4 x 4TB WD reds, configured as 2 data drives and 2 parity. I configured Snapraid to put a content file on every drive, but I see that some recommend not putting content files on the parity drives. The problem is it requires parity + 1 copies and I don't see a way in the plugin to put the content file on my boot drive (60gb SSD). In the future when I add additional data drives, can I just select in the drives tab of the plugin the new data drive as having a content file, and unselect the parity drives, or will I need to move the content file manually and reconfigure snapraid.conf? Could i put a content file on my boot SSD today by manually copying one there and adding it in snapraid.conf?

My Snapraid has been successfully sync'd - took roughly 9 hours. Now I just need to setup the snapraid-diff script to run once per day, correct? The diff script will sync every day and do a full scrub every week? If the delete threshold is 0, it wont sync if any files have been deleted? I assume I will want to set that to some number higher than 0 that I'm comfortable with?

What happens if a drive fails, and it does a sync? Will the script not do a sync if a drive has failed?

Finally, with my 2 data + 2 parity configuration, I could recover if any 2 drives fail? Even if it's both data drives or both parity drives? Just want to make sure I fully understand.

Thanks