From: Paul Clements <paul.clements@steeleye.com>
To: linux-raid@vger.kernel.org
Subject: Re: Bug report: mdadm -E oddity
Date: Fri, 20 May 2005 16:05:11 -0400 [thread overview]
Message-ID: <428E42F7.40208@steeleye.com> (raw)
In-Reply-To: <d5n1m2-rb5.ln1@news.it.uc3m.es>
Peter T. Breuer wrote:
> b) rewriting is not necessarily idempotent, when half of it consists
> of using a parity to construct what you should write.
That's right. The rewrite is not idempotent. Having lost part, or all,
of either D1 or P at the time of the crash, you no longer have any
accurate way of reconstructing D2.
And that's assuming you can even do a rewrite. By default, only metadata
is journalled (in ext3), so for plain old data writes, you're just plain
out of luck...
--
Paul
next prev parent reply other threads:[~2005-05-20 20:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 15:44 Bug report: mdadm -E oddity Doug Ledford
2005-05-13 17:11 ` Doug Ledford
2005-05-13 23:01 ` Neil Brown
2005-05-14 13:28 ` Doug Ledford
2005-05-15 17:32 ` Luca Berra
2005-05-20 7:00 ` Neil Brown
2005-05-20 12:30 ` Doug Ledford
2005-05-20 16:04 ` Paul Clements
2005-05-20 17:16 ` Peter T. Breuer
2005-05-20 18:40 ` Doug Ledford
2005-05-20 19:15 ` Peter T. Breuer
2005-05-20 21:31 ` Doug Ledford
2005-05-20 17:45 ` Doug Ledford
2005-05-20 18:33 ` Peter T. Breuer
2005-05-20 20:01 ` berk walker
2005-05-20 21:00 ` Gil
2005-05-20 21:51 ` Peter T. Breuer
2005-05-20 22:14 ` berk walker
2005-05-20 20:05 ` Paul Clements [this message]
2005-05-16 16:46 ` Doug Ledford
2005-05-20 7:08 ` Neil Brown
2005-05-20 11:29 ` Doug Ledford
2005-05-16 22:11 ` Doug Ledford
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=428E42F7.40208@steeleye.com \
--to=paul.clements@steeleye.com \
--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;
as well as URLs for NNTP newsgroup(s).