From: David Niklas <Hgntkwis@vfemail.net>
To: linux-kernel@vger.kernel.org
Subject: [raid] How does raid-check know which piece of data is the correct one
Date: Fri, 19 Aug 2016 15:48:46 -0400 [thread overview]
Message-ID: <20160819154846.2ad3f35a@ulgy_thing> (raw)
Hello,
please CC.
I switched to a RAID 5 array about a year ago and I run raid-check every
week, the problem is that I've gotten some corruption of some of my files
over time (HW failure and cable creep have caused the array to need to
rebuild a few times), and I wanted to try to figure it out if this was a
"before I switched to raid problem", or if there may be insufficient
protection from my raid array.
Here is the case where I'm uncertain. If I've got two bytes.
10101010 01010101 then they are probably xor'ed for parity and that would
make it 11111111. Ok, but if one or the other byte or the parity byte are
damaged how does raid-check rectify the problem? How does it know which
one is damaged.
Thanks,
David
-------------------------------------------------
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!
reply other threads:[~2016-08-19 19:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160819154846.2ad3f35a@ulgy_thing \
--to=hgntkwis@vfemail.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome