Re: imsm raid is always readonly on boot

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 07 Feb 2012 12:58:17 +0100 Stefan Priebe - Profihost AG
<s.priebe@xxxxxxxxxxxx> 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@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Attachment: signature.asc
Description: PGP signature


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux