TooMeeK User

Try RECYCLE.BIN method, move deleted files into bin. Then issue sync. Purge bin only when ready to do so. New & deleted files will be still under protection. Of course, the bin folder have to be included in snapraid config and best would be unlimited capacity.

snapraid status always reports failures, either missing/broken disks or files, best would be implement script that outputs that to e-mail on daily basis. It will inform You when it cannot eg. read content file, something bad is reported from the drive, it's missing, etc. However, you should still implement smartctl --test=short /dev/sdX and smartctl --test=long /dev/sdX scripts because the way how SnapRAID works it's up to You to first detect failure before it escalates and consume more disks. You...

Probably caused due to protection mechanism that detect buffer overflow errors, but dunno the cause, Out-of-memory during recover? Try fixing independent disks one by one. snapraid fix -d1 -l/tmp/snapraid-disk1-fix.log snapraid fix -d13 -l/tmp/snapraid-disk13-fix.log

There should be no problem as executable file detectes if any other process is running and simply refuse to proceed, At least on Linux.. so generally single instance of the process is allowed, that's why lock files are used for. What's the snapraid.content.lock file? It's a file used by SnapRAID to check if another SnapRAID instance is already running. It's created where the first content file is placed.

I belive You cannot remove parity-1 as it's needed for parity-2 and parity-3 to work as intended. So remove parity-3, issue sync, copy all files from parity-1 to parity-3 drive, sync again, remove original parity-1 drive,

There should be no problem as executable file detectes if any other process is running and simply refuse to proceed, At least on Linux.. so generally single instance of the process is allowed, that's why lock files are used for.

Use --log switch and collect these files to track all changes, my sync script looks like this: #!/bin/bash #vars data=$(date +'%Y%m%d') #echo Today is $data ! snapraid diff --log $data.diff; snapraid status --log $data.status; snapraid sync --log $data.sync; snapraid scrub -p new --log $data.scrub; snapraid touch --log $data.touch;snapraid status --log $data.status after revieving them I just gzip them. For data recovery usually procedure is: 1. replace failed drive, note which one was that (d1,...

snapraid diff will return differences between current state of the array and last successful sync. It will also return path of changed or missing files. If files are silently corrupted, snapraid scrub -p 100 should find them. Restore depends on failure itself - if entire drive dies, single parity drive and all remaining data drives are required to recover. If two drives die at once - double parity and all remaining drives must be heatlhy. Generally speaking, if You don't miss something in "exclude...