From: John Hendrikx <hjohn@xs4all.nl>
To: Shaochun Wang <scwang@ios.ac.cn>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID5 write hole?
Date: Sun, 27 Jun 2010 12:33:49 +0200 [thread overview]
Message-ID: <4C27290D.6000609@xs4all.nl> (raw)
In-Reply-To: <20100626143125.GA1010@localhost>
Shaochun Wang wrote:
> Hi:
>
> Recently I heard of the so called "write hole" problem of raid5 in
> Linux software raid. I use ext4 filesystem on my NAS, which assembles
> data disks using Linux software raid. So I wonder how safe my such
> system!
>
> If the "write hole" is inevitable, will it result in the corruption of
> ext4 filesystem?
The write hole occurs if your system crashes during a write operation,
where one stripe gets updated but the other corresponding stripe does
not. This could lead to parity information not matching the
corresponding data.
If the raid 5 system atleast ensures that the data stripe is always
written before parity, then the montly resync check that mdadm does
should be able to detect this and write new parity information.
Atleast this way the bad parity does not lurk around forever on your
raid system causing numerous problems when a disk finally fails.
The write hole is not inevitable, but would require some special
measures at the raid level which could affect performance. And as with
any corruption, it could definitely corrupt your filesystem.
--John
next prev parent reply other threads:[~2010-06-27 10:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-26 14:31 RAID5 write hole? Shaochun Wang
2010-06-26 15:42 ` Mikael Abrahamsson
2010-06-26 21:28 ` Shaochun Wang
2010-06-27 10:33 ` John Hendrikx [this message]
2010-06-27 12:16 ` Neil Brown
2010-06-29 6:16 ` Shaochun Wang
2010-06-29 6:23 ` Mikael Abrahamsson
2010-06-29 13:28 ` Shaochun Wang
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=4C27290D.6000609@xs4all.nl \
--to=hjohn@xs4all.nl \
--cc=linux-raid@vger.kernel.org \
--cc=scwang@ios.ac.cn \
/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;
as well as URLs for NNTP newsgroup(s).