From: Neil Brown <neilb@suse.de>
To: linux-raid@vger.kernel.org
Subject: [PULL REQUEST] a few more md patches....
Date: Fri, 13 Nov 2009 20:36:13 +1100 [thread overview]
Message-ID: <19197.10381.201071.987808@notabene.brown> (raw)
[I just realised that when I sent this to Linus a couple of hours ago
I forgot to cc to linux-raid - sorry]
I know it is getting late, but continued testing showed that an
unclean shutdown during a RAID level migration can leave the array
in a slightly inconsistent state. If after that you get a device
failure, md may not respond exactly the right way. There is room for
data corruption in there.
Thanks,
NeilBrown
The following changes since commit aa021baa3295fa6e3f367d80f8955dd5176656eb:
Linus Torvalds (1):
Merge git://git.kernel.org/.../mason/btrfs-unstable
are available in the git repository at:
git://neil.brown.name/md for-linus
NeilBrown (4):
md: factor out updating of 'recovery_offset'.
md: allow v0.91 metadata to record devices as being active but not in-sync.
Don't unconditionally set in_sync on newly added device in raid5_reshape
md/raid5: Allow dirty-degraded arrays to be assembled when only party is degraded.
drivers/md/md.c | 41 ++++++++++++++++++++-----
drivers/md/raid5.c | 85 ++++++++++++++++++++++++++++++++++++++++++++++++----
2 files changed, 112 insertions(+), 14 deletions(-)
reply other threads:[~2009-11-13 9:36 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=19197.10381.201071.987808@notabene.brown \
--to=neilb@suse.de \
--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