From: Neil Brown <neilb@suse.de>
To: Peter Rabbitson <rabbit+list@rabbit.us>
Cc: linux-raid@vger.kernel.org
Subject: Re: BUG: possible array corruption when adding a component to a degraded raid5 (possibly other levels too)
Date: Mon, 28 Jan 2008 22:34:49 +1100 [thread overview]
Message-ID: <18333.48601.218262.452373@notabene.brown> (raw)
In-Reply-To: message from Peter Rabbitson on Monday January 28
On Monday January 28, rabbit+list@rabbit.us wrote:
> Hello,
>
> It seems that mdadm/md do not perform proper sanity checks before adding a
> component to a degraded array. If the size of the new component is just right,
> the superblock information will overlap with the data area. This will happen
> without any error indications in the syslog or otherwise.
I thought I fixed that.... What versions of Linux kernel and mdadm are
you using for your tests?
Thanks,
NeilBrown
next prev parent reply other threads:[~2008-01-28 11:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 10:05 BUG: possible array corruption when adding a component to a degraded raid5 (possibly other levels too) Peter Rabbitson
2008-01-28 11:34 ` Neil Brown [this message]
2008-01-28 11:54 ` Peter Rabbitson
2008-01-29 0:38 ` Neil Brown
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=18333.48601.218262.452373@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=rabbit+list@rabbit.us \
/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).