Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Shaochun Wang <scwang@ios.ac.cn>
To: linux-raid@vger.kernel.org
Subject: RAID5 write hole?
Date: Sat, 26 Jun 2010 22:31:25 +0800	[thread overview]
Message-ID: <20100626143125.GA1010@localhost> (raw)

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? 

-- 
Shaochun Wang <scwang@ios.ac.cn>

Jabber: fungusw@jabber.org

             reply	other threads:[~2010-06-26 14:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-26 14:31 Shaochun Wang [this message]
2010-06-26 15:42 ` RAID5 write hole? Mikael Abrahamsson
2010-06-26 21:28   ` Shaochun Wang
2010-06-27 10:33 ` John Hendrikx
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=20100626143125.GA1010@localhost \
    --to=scwang@ios.ac.cn \
    --cc=linux-raid@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