From: Alexandre Oliva <aoliva@redhat.com>
To: linux-raid <linux-raid@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: modifying degraded raid 1 then re-adding other members is bad
Date: Tue, 08 Aug 2006 06:38:19 -0300 [thread overview]
Message-ID: <or8xlztvn8.fsf@redhat.com> (raw)
Assume I have a fully-functional raid 1 between two disks, one
hot-pluggable and the other fixed.
If I unplug the hot-pluggable disk and reboot, the array will come up
degraded, as intended.
If I then modify a lot of the data in the raid device (say it's my
root fs and I'm running daily Fedora development updates :-), which
modifies only the fixed disk, and then plug the hot-pluggable disk in
and re-add its members, it appears that it comes up without resyncing
and, well, major filesystem corruption ensues.
Is this a known issue, or should I try to gather more info about it?
This happened with 2.6.18rc3-git[367] (not sure which), plus Fedora
development patches.
--
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
Secretary for FSF Latin America http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}
next reply other threads:[~2006-08-08 9:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 9:38 Alexandre Oliva [this message]
2006-08-08 11:12 ` modifying degraded raid 1 then re-adding other members is bad Neil Brown
2006-08-08 11:19 ` Michael Tokarev
2006-08-08 19:17 ` Krzysztof Halasa
2006-08-08 22:33 ` Neil Brown
2006-08-08 22:30 ` Neil Brown
2006-08-09 6:35 ` Jan Engelhardt
2006-08-09 23:18 ` Neil Brown
2006-08-09 9:01 ` Helge Hafting
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=or8xlztvn8.fsf@redhat.com \
--to=aoliva@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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).