Re: imsm raid is always readonly on boot

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


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
--
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


[ATA RAID]     [Linux SCSI Target Infrastructure]     [Managing RAID on Linux]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device-Mapper]     [Kernel]     [Linux Books]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Photos]     [Yosemite Photos]     [Yosemite News]     [AMD 64]     [Linux Networking]

Add to Google Powered by Linux