From: Brian Downing <bdowning@lavos.net>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: v3.5 regression in IMSM support
Date: Tue, 17 Jul 2012 21:20:50 -0500 [thread overview]
Message-ID: <20120718022050.GG23042@glaurung.lavos.net> (raw)
In-Reply-To: <20120718103458.70046aaf@notabene.brown>
On Wed, Jul 18, 2012 at 10:34:58AM +1000, NeilBrown wrote:
> Thank you so much for a very thorough bug report!!
>
> Fix is below - please test and confirm that it fixes your symptoms.
I applied this to Linus's master as of today and it appears to restore
the earlier working behavior for my system, including incremental assembly
and a correct-looking mdstat:
:; uname -r
3.5.0-rc7-ARCH-00082-g04f15c7
:; cat /proc/mdstat
Personalities : [raid0]
md126 : active raid0 sda[1] sdb[0]
625137664 blocks super external:/md127/0 128k chunks
md127 : inactive sdb[1](S) sda[0](S)
4520 blocks super external:imsm
Thank you very much for the quick fix!
Tested-by: Brian Downing <bdowning@lavos.net>
-bcd
prev parent reply other threads:[~2012-07-18 2:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 9:05 v3.5 regression in IMSM support Brian Downing
2012-07-18 0:34 ` NeilBrown
2012-07-18 2:20 ` Brian Downing [this message]
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=20120718022050.GG23042@glaurung.lavos.net \
--to=bdowning@lavos.net \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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