1 |
Duncan wrote |
2 |
|
3 |
>>Well, normally the root partition /will/ still be in use, so can't be |
4 |
>>unmounted. However, it's then mounted read-only, instead, forcing out all |
5 |
>>cached writes to bring the fs into a consistent state and then allowing no |
6 |
>>more writes to it after it's mounted read-only. Thus, the system can |
7 |
>>still shut down even with it mounted. |
8 |
> |
9 |
> |
10 |
|
11 |
I gather you mean in this situation the raid doesn't need to be deactivated. |
12 |
|
13 |
|
14 |
>>The problem here is that for some reason the system apparently isn't |
15 |
>>recognizing that partition as root, so it's still warning when it can't be |
16 |
>>unmounted. As mentioned, it could be an order thing, or it could be that |
17 |
>>particular raid or lvm config isn't setup correctly in the initscripts, so |
18 |
>>it's not recognizing them as devices containing filesystems, at all. |
19 |
> |
20 |
> |
21 |
|
22 |
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. |
23 |
|
24 |
--- /lib/rcscripts/addons/lvm-stop.sh.orig 2005-11-01 19:07:25.000000000 +0900 |
25 |
+++ /lib/rcscripts/addons/lvm-stop.sh 2005-11-01 19:48:38.000000000 +0900 |
26 |
@@ -46,6 +46,8 @@ |
27 |
then |
28 |
|
29 |
ROOT_DEVICE=`mount|grep " / "|awk '{print $1}'` |
30 |
+ [ -L ${ROOT_DEVICE} ] && ROOT_DEVICE="`readlink ${ROOT_DEVICE}`" |
31 |
+ [ -L ${x} ] && x="`readlink ${x}`" |
32 |
if [ ! ${ROOT_DEVICE} = ${x} ] |
33 |
then |
34 |
ewarn " Unable to shutdown: ${x} " |
35 |
|
36 |
|
37 |
Edward |
38 |
|
39 |
-- |
40 |
gentoo-amd64@g.o mailing list |