Re: Questions regarding startup of imsm container

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

 



Update on progress....

I have managed to hack together a dracut created initramfs that has me
able to boot and has resolved all boot issues. Will let this thing
have a few hours of resyncing and see if external bitmap comes back
and how it handles the reboot.

Thanks again for the assistance.

On Tue, Mar 23, 2010 at 5:25 PM, Randy Terbush <randy@xxxxxxxxxxx> wrote:
> Thanks Dan, a few more steps forward here. I suspect I know the
> answer, but will see what you suggest.
>
> On Tue, Mar 23, 2010 at 4:16 PM, Dan Williams <dan.j.williams@xxxxxxxxx> wrote:
>> This shows that Gentoo is most likely not including mdmon in their initramfs
>> environment.  mdadm assembles the array readonly, but then mdmon is required
>> to mark the array writable.
>
> Looks like you are correct and current installation packages on Gentoo
> have apparently not dealt with these changes. mdmon is not getting
> started and is not being attempted anywhere.
>
> I don't run an initrd, so attempted to start mdmon after the mdadm -As
> runs. This is apparently too early in the process as I get the
> following:
>
> * Starting up RAID devices ...
>  [ ok ]
> mdmon: Neither /var/run nor /lib/init/rw are writable
>       cannot create .pid or .sock files.  Aborting
>  * Setting up the Logical Volume Manager ...
>  [ ok ]
>  * Checking local filesystems  ...
> HOME-vg0: clean, 13/3276800 files, 256151/52428800 blocks
> Warning... fsck.ext4 for device /dev/mapper/vg0-home exited with signal 11.
> SVN-vg0: clean, 191/1638400 files, 153087/26214400 blocks
> Warning... fsck.ext4 for device /dev/mapper/vg0-svn exited with signal 11.
> ARCHIVE-vg0: clean, 12/1638400 files, 152150/26214400 blocks
>
> So it appears the start of mdmon needs to wait until we have a rw
> filesystem mounted. Not entirely sure if it is related, but as you can
> see above, fsck blows up trying to check the filesystems on this
> array. That appears to clear itself up once mdmon is running. After
> starting mdmon by hand, the resync begins and I can successfully run
> fsck on these partitions.
>
> So looks like I have a chicken and egg problem that I suspect may be
> solved by creating an initramfs. I took a quick pass at dracut but
> could not convince it to add mdmon. Any hints appreciated as I go back
> to dig for more info.
>
> Thanks again for the assistance.
>
--
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

[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