From: NeilBrown <neilb@suse.de>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: linux-raid@vger.kernel.org
Subject: Re: imsm raid is always readonly on boot
Date: Wed, 8 Feb 2012 19:45:02 +1100 [thread overview]
Message-ID: <20120208194502.05a9f7c6@notabene.brown> (raw)
In-Reply-To: <4F3232B2.6010605@profihost.ag>
[-- Attachment #1: Type: text/plain, Size: 1455 bytes --]
On Wed, 08 Feb 2012 09:30:42 +0100 Stefan Priebe - Profihost AG
<s.priebe@profihost.ag> wrote:
> 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...
It should be configured to create it in a writable filesystem,
maybe /dev/.something or /var/run/something.
If it is configured to create it somewhere that isn't writeable when mdadm is
run, then that is a system integration error.
(not entirely surprising as we seem to keep changing our mind as to where
this stuff should go - I think /run is the flavour of the month).
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2012-02-08 8:45 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
2012-02-08 8:45 ` NeilBrown [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=20120208194502.05a9f7c6@notabene.brown \
--to=neilb@suse.de \
--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).