I am starting building out my home storage system and learning as I go.
Below is my current thinking/question
I will use drivepool and with all pool/files duplicated.
I will have additional backups (cloud and local)
I feel ok against drive-failures, against entire system failing etc.
My question is - how do I protect against silent bitrot
I know drivepool via integrated scanner will find blocks that are bad.
But how do I protect against silent bit flip.
I know its very rare.
But still - would be nice to know how to protect against it
Question does drivepool secure against "silent bitrot"
Lets say a file fileA is stored in diskpool and dubplicated on two drives and one of the drives a bit flips, changes value from say 1 to 0. At this point in time I will have
* disk1: fileA (correct file)
* disk2: fileA (corrupt file)
Question: Does diskpool have a "diskpool check" command that checks all files (all duplicates) and detects corrupted files?
Question: Next read of file1 - will it be the fileA from disk1 or from disk2? or?
Question: Will diskpool detect that fileA is now different on disk1 vs disk2?
Essentially
* will diskpool detect a underlying bit-root like this?
* will it in addition to detect it be able to fix it?
If not - sounds like a great value-add feature - ex
everytime diskpool writes a file it also calculates and stores a checksum of the file
* option to enable: write verification: after write - read both duplicates and verify checksum
dispool check command
* reads all files (all duplicates) and verifies that checksum is as expected
diskpool file read
* option to enable: read verification: everytime diskpool reads a file - verifies that read file checksum is as expected
* option to enable: read verification all duplicated: everytime diskpool reads a file - reads all duplicates and verifies that read files checksum are as expected
Question
Andreas W
Hi
I am starting building out my home storage system and learning as I go.
Below is my current thinking/question
I will use drivepool and with all pool/files duplicated.
I will have additional backups (cloud and local)
I feel ok against drive-failures, against entire system failing etc.
My question is - how do I protect against silent bitrot
I know drivepool via integrated scanner will find blocks that are bad.
But how do I protect against silent bit flip.
I know its very rare.
But still - would be nice to know how to protect against it
Question does drivepool secure against "silent bitrot"
Lets say a file fileA is stored in diskpool and dubplicated on two drives and one of the drives a bit flips, changes value from say 1 to 0. At this point in time I will have
* disk1: fileA (correct file)
* disk2: fileA (corrupt file)
Question: Does diskpool have a "diskpool check" command that checks all files (all duplicates) and detects corrupted files?
Question: Next read of file1 - will it be the fileA from disk1 or from disk2? or?
Question: Will diskpool detect that fileA is now different on disk1 vs disk2?
Essentially
* will diskpool detect a underlying bit-root like this?
* will it in addition to detect it be able to fix it?
If not - sounds like a great value-add feature - ex
everytime diskpool writes a file it also calculates and stores a checksum of the file
* option to enable: write verification: after write - read both duplicates and verify checksum
dispool check command
* reads all files (all duplicates) and verifies that checksum is as expected
diskpool file read
* option to enable: read verification: everytime diskpool reads a file - verifies that read file checksum is as expected
* option to enable: read verification all duplicated: everytime diskpool reads a file - reads all duplicates and verifies that read files checksum are as expected
/Andreas
Link to comment
Share on other sites
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.