Gentoo Archives: gentoo-amd64

From: Edward Middleton <edward@××××××××××××.jp>
To: gentoo-amd64@l.g.o
Subject: [gentoo-amd64] Re: Root on Raid and LVM - Solved
Date: Tue, 01 Nov 2005 01:57:00
Message-Id: 4366CA93.3020400@nikon-sys.co.jp
In Reply to: [gentoo-amd64] Re: Root on Raid and LVM - Solved by Edward Middleton
Duncan wrote

>>Well, normally the root partition /will/ still be in use, so can't be >>unmounted. However, it's then mounted read-only, instead, forcing out all >>cached writes to bring the fs into a consistent state and then allowing no >>more writes to it after it's mounted read-only. Thus, the system can >>still shut down even with it mounted. > >
I gather you mean in this situation the raid doesn't need to be deactivated.
>>The problem here is that for some reason the system apparently isn't >>recognizing that partition as root, so it's still warning when it can't be >>unmounted. As mentioned, it could be an order thing, or it could be that >>particular raid or lvm config isn't setup correctly in the initscripts, so >>it's not recognizing them as devices containing filesystems, at all. > >
Going on what you said before the /etc/conf.d/rc variable should be set to RC_VOLUME_ORDER="lvm" if you are using raidlvm. There is a bug in the /lib/rcscripts/addons/lvm-stop.sh which assumes that mount returns the symbolic link /dev/[volume group]/[logical partition] but it actually returns the actual device /dev/mapper/[volume group]-[logical partition]. The following path patch fixes this. --- /lib/rcscripts/addons/lvm-stop.sh.orig 2005-11-01 19:07:25.000000000 +0900 +++ /lib/rcscripts/addons/lvm-stop.sh 2005-11-01 19:48:38.000000000 +0900 @@ -46,6 +46,8 @@ then ROOT_DEVICE=`mount|grep " / "|awk '{print $1}'` + [ -L ${ROOT_DEVICE} ] && ROOT_DEVICE="`readlink ${ROOT_DEVICE}`" + [ -L ${x} ] && x="`readlink ${x}`" if [ ! ${ROOT_DEVICE} = ${x} ] then ewarn " Unable to shutdown: ${x} " Edward -- gentoo-amd64@g.o mailing list

Replies

Subject Author
[gentoo-amd64] Re: Root on Raid and LVM - Solved Duncan <1i5t5.duncan@×××.net>