From: John Robinson <john.robinson@anonymous.org.uk>
To: Stefan Priebe <s.priebe@profihost.ag>
Cc: Jes Sorensen <Jes.Sorensen@redhat.com>, linux-raid@vger.kernel.org
Subject: Re: imsm raid is always readonly on boot
Date: Tue, 07 Feb 2012 21:47:13 +0000 [thread overview]
Message-ID: <4F319BE1.2010306@anonymous.org.uk> (raw)
In-Reply-To: <4F316273.7030109@profihost.ag>
On 07/02/2012 17:42, Stefan Priebe wrote:
[...]
> md127 : inactive sdb[1](S) sda[0](S)
> 5544 blocks super external:imsm
I don't know what the answer is, but I suspect that the members of the
container both being marked as spares may be (part of) the problem.
Cheers,
John.
next prev parent reply other threads:[~2012-02-07 21:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 11:58 imsm raid is always readonly on boot Stefan Priebe - Profihost AG
2012-02-07 16:09 ` Jes Sorensen
2012-02-07 17:42 ` Stefan Priebe
2012-02-07 17:45 ` Jes Sorensen
2012-02-07 18:24 ` Stefan Priebe
2012-02-07 20:24 ` Jes Sorensen
2012-02-07 21:47 ` John Robinson [this message]
2012-02-08 1:57 ` NeilBrown
2012-02-08 8:30 ` Stefan Priebe - Profihost AG
2012-02-08 8:45 ` 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=4F319BE1.2010306@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=Jes.Sorensen@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=s.priebe@profihost.ag \
/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).