linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.com>
To: Gareth Evans <donotspam@fastmail.fm>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm/Software RAID problems - another update
Date: Thu, 25 Jun 2015 09:26:26 +1000	[thread overview]
Message-ID: <20150625092626.1ac30dfe@noble> (raw)
In-Reply-To: <1434896517.3660124.303759113.0AE76093@webmail.messagingengine.com>

On Sun, 21 Jun 2015 15:21:57 +0100 Gareth Evans <donotspam@fastmail.fm>
wrote:

> After a number of tests with VirtualBox this weekend, it seems things work as they should with Fedora 22 but openSUSE 13.2, Debian 8.1 and Ubuntu 14.04.2 all appear to hang on boot when one vdisk is removed and another is attached, even if formatted with a "Linux RAID autodetect"-type partition.  CentOS 7 doesn't hang but doesn't have mdadm in its emergency console (I gave up with CentOS after that as not sure how to add commands, if that's possible...) and neither Fedora nor CentOS emergency consoles seem to include fdisk, which isn't too helpful.  
> 

I cannot comment on the other distros, but I believe that openSUSE
13.2, with all updates installed, handles boot on degraded md arrays
correctly.  As I *am* the mdadm maintainer for that distro, I can put
effort there.

If you have specifics of a configuration on openSUSE-13.2 with latest
updates for mdadm and dracut installed, where it doesn't boot correctly,
then I would definitely like to know about them, either here or at
bugzilla.opensuse.org - whichever suits you.

Thanks,
NeilBrown


  reply	other threads:[~2015-06-24 23:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-19 18:48 mdadm/Software RAID problems Gareth Evans
2015-06-20  5:56 ` mdadm/Software RAID problems - update Gareth Evans
2015-06-21 14:21   ` mdadm/Software RAID problems - another update Gareth Evans
2015-06-24 23:26     ` NeilBrown [this message]
2015-06-24 23:21 ` mdadm/Software RAID problems NeilBrown

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=20150625092626.1ac30dfe@noble \
    --to=neilb@suse.com \
    --cc=donotspam@fastmail.fm \
    --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).