From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.50) id 1EWlOW-0005Ux-2M for garchives@archives.gentoo.org; Tue, 01 Nov 2005 01:57:00 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jA11rdAL030721; Tue, 1 Nov 2005 01:53:39 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id jA11rbvx032172 for ; Tue, 1 Nov 2005 01:53:38 GMT Received: from ns.nikon-sys.co.jp ([202.230.170.1] helo=gwsrv.nikon-sys.co.jp) by smtp.gentoo.org with esmtp (Exim 4.43) id 1EWlLF-0007QV-2J for gentoo-amd64@lists.gentoo.org; Tue, 01 Nov 2005 01:53:37 +0000 Received: from mail.nikon-sys.co.jp by gwsrv.nikon-sys.co.jp (8.11.7+Sun/3.7Wpl2/01102715) id jA11rZR01558; Tue, 1 Nov 2005 10:53:35 +0900 (JST) Received: from mail.nikon-sys.co.jp (localhost.localdomain [127.0.0.1]) by localhost.nikon-sys.co.jp (Postfix) with ESMTP id 24E5EEC8 for ; Tue, 1 Nov 2005 10:53:35 +0900 (JST) Received: from mxsrv2.nikon-sys.co.jp (mxsrv2 [128.33.252.98]) by mail.nikon-sys.co.jp (Postfix) with ESMTP id 00F2AF27 for ; Tue, 1 Nov 2005 10:53:35 +0900 (JST) Received: (qmail 13264 invoked by uid 89); 1 Nov 2005 10:53:34 +0900 Received: from unknown (HELO ?10.215.33.53?) (10.215.33.53) by 0 with SMTP; 1 Nov 2005 10:53:34 +0900 Message-ID: <4366CA93.3020400@nikon-sys.co.jp> Date: Tue, 01 Nov 2005 10:53:23 +0900 From: Edward Middleton User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051017) X-Accept-Language: en-us, en Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org MIME-Version: 1.0 To: gentoo-amd64@lists.gentoo.org Subject: [gentoo-amd64] Re: Root on Raid and LVM - Solved References: <4365CBC8.2080502@nikon-sys.co.jp> In-Reply-To: <4365CBC8.2080502@nikon-sys.co.jp> X-Enigmail-Version: 0.91.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: de5fc528-b118-4fc0-9192-62b1c528bc90 X-Archives-Hash: 636a64119d9119ebf37a09a5c04b6c97 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@gentoo.org mailing list