linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: imsm raid is always readonly on boot
Date: Wed, 08 Feb 2012 09:30:42 +0100	[thread overview]
Message-ID: <4F3232B2.6010605@profihost.ag> (raw)
In-Reply-To: <20120208125729.5674f35d@notabene.brown>

Hi Neil,

Am 08.02.2012 02:57, schrieb NeilBrown:
> Probably mdmon isn't running for some reason.
> 
> For these arrays the metadata is managed in user-space by mdmon.
> Until it is ready to record failures the array must remain readonly.
> On of the first things it does is switch the array to read-write, having
> arranged to catch any failure notifications.
> 
> If you 
> 
>  mdmon --all --takeover
> 
> it might just start working.  However that doesn't explain why mdmon wasn't
> started at boot.  mdadm is meant to start it.
> There are some concerns about mdmon starting this way being not "the right
> thing" from a systemd perspective and there might be some issues there that
> are causing problems.

You're correct the mdmon does not run as the root filesystem is readonly
and it cannot create a pid file... and the root filesystem stays
readonly as the mdmon is not running...

Greets

Stefan

  reply	other threads:[~2012-02-08  8:30 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
2012-02-08  1:57 ` NeilBrown
2012-02-08  8:30   ` Stefan Priebe - Profihost AG [this message]
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=4F3232B2.6010605@profihost.ag \
    --to=s.priebe@profihost.ag \
    --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;
as well as URLs for NNTP newsgroup(s).