From: NeilBrown <neilb@suse.de>
To: Johan Hovold <jhovold@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: MD-raid broken in 2.6.37.3?
Date: Wed, 9 Mar 2011 21:02:51 +1100 [thread overview]
Message-ID: <20110309210251.744ef954@notabene.brown> (raw)
In-Reply-To: <20110309090622.GA3570@localhost>
On Wed, 9 Mar 2011 10:06:22 +0100 Johan Hovold <jhovold@gmail.com> wrote:
> Hi Greg and Neil,
>
> I updated from 2.6.37.2 to 2.6.37.3 yesterday only to find that my
> raid-0 partitions are no longer recognised. The raid-1 ones still are,
> though. They did not show up after a reboot. (It has happened once
> fairly recently that these exact partitions were not recognised but a
> reboot fixed it -- blamed my disks.)
>
> Today I mistakenly booted into 2.6.37.3 again -- still missing. No
> problems with 2.6.37.2.
>
> Browsing the changelog I found f663ed60892c3e1d4490b079a45d9e546271c40c
> (md: Fix - again - partition detection when array becomes active) and
> other md-related changes so I figure one of these could perhaps be to
> blame?
>
> As it is my personal/production machine I feel uncomfortable bisecting
> this at this point, but maybe Neil has an idea of what might be going
> on?
Hi Johan,
could you please be a bit more specific about the problem that you
experienced.
What, exactly, was "no longer recognised"?
Was it that the array (e.g. /dev/md1) didn't appear, or was it that the
array did appear, but that it has a partition table, and the partitions
(e.g. /dev/md1p1, /dev/md1p2) did not appear?
If you still have the boot-log from when you booted 2.6.37.3 (or can
recreated) and can get a similar log for 2.6.37.2, then it might be useful to
compare them.
Thanks,
NeilBrown
next prev parent reply other threads:[~2011-03-09 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 9:06 Johan Hovold
2011-03-09 10:02 ` NeilBrown [this message]
2011-03-09 19:26 ` Johan Hovold
2011-03-09 22:28 ` NeilBrown
2011-03-10 11:25 ` Johan Hovold
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=20110309210251.744ef954@notabene.brown \
--to=neilb@suse.de \
--cc=gregkh@suse.de \
--cc=jhovold@gmail.com \
--cc=linux-kernel@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
Powered by JetHome