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 12:57:29 +1100 [thread overview]
Message-ID: <20120208125729.5674f35d@notabene.brown> (raw)
In-Reply-To: <4F3111D9.2060303@profihost.ag>
[-- Attachment #1: Type: text/plain, Size: 2116 bytes --]
On Tue, 07 Feb 2012 12:58:17 +0100 Stefan Priebe - Profihost AG
<s.priebe@profihost.ag> wrote:
> Hi,
>
> i'm running 3.0.18 as kernel (renamed to 2.6.40) and mdadm 3.2.2.
>
> I'm trying to get an intel fake raid running but it is always set to
> readonly on boot after running
> mdadm --assemble --scan --run --force --auto=yes
>
> But i've absolutely no idea why.
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.
NeilBrown
>
> My mdadm.conf:
> # by default (built-in), scan all partitions (/proc/partitions) and all
> # containers for MD superblocks. alternatively, specify devices to scan,
> using
> # wildcards if desired.
> #DEVICE partitions containers
>
> # auto-create devices with Debian standard permissions
> CREATE owner=root group=disk mode=0660 auto=yes
>
> # automatically tag new arrays as belonging to the local system
> HOMEHOST <ignore>
>
> # instruct the monitoring daemon where to send mail alerts
> MAILADDR root
>
> # definitions of existing MD arrays
> ARRAY metadata=imsm UUID=24cdb70d:101f4c4b:23dfa5cb:3f176b6a
> ARRAY /dev/md126 container=24cdb70d:101f4c4b:23dfa5cb:3f176b6a member=0
> UUID=84aa9982:ed593d80:ee7c7f53:e2944038
>
>
> ~# cat /sys/block/md126/md/array_state
> readonly
>
> What's wrong? Thanks!
>
> Stefan
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-02-08 1:57 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 [this message]
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=20120208125729.5674f35d@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).