Hi David... Thanks for replying. At the very least we'd like to put /var, /opt/local, and /usr/local in the lvm. I may not be saying this correctly, so bear with me. What we actually did was put all the r/w directories off of /guestvol which is the mount point for the lvm. When we boot the system, the script successfully remounts / (root) as r/o, but fails when it tries to run the e2fsck on the lvm (?) and the subsequent mount fails as well.
08:10:12 Basevol/Guestvol script begins... . 08:10:12 This server is running with shared disk support. 08:10:12 Many directories will be in R/O mode. 08:10:12 Forcing R/O mount of root file systems... . 08:10:12 Forcing a filesystem check on R/W guest volume... . 08:10:12 e2fsck 1.38 (30-Jun-2005) 08:10:12 e2fsck: No such device or address while trying to open /dev/system/lvol1 08:10:12 Possibly non-existent or swap device? 08:10:12 56 *-* 'e2fsck /dev/system/lvol1' 08:10:12 +++ RC=8 +++ 08:10:12 Mounting R/W guest volume... . 08:10:12 mount: /dev/system/lvol1 is not a valid block device 08:10:12 59 *-* 'mount -w -t ext3 -n /dev/system/lvol1 /guestvol' /* R/W, type EXT3, no update /etc/mtab */ 08:10:12 +++ RC=32 +++ I found the suggestion to run vgscan/vgchange first which I tried, but did not work. 14:15:34 Basevol/Guestvol script begins... . 14:15:34 This server is running with shared disk support. 14:15:34 Many directories will be in R/O mode. 14:15:34 Forcing R/O mount of root file systems... . 14:15:35 Reading all physical volumes. This may take a while... 14:15:35 Found volume group "system" using metadata type lvm2 14:15:35 /proc/misc: No entry for device-mapper found 14:15:35 Is device-mapper driver missing from kernel? 14:15:35 /dev/mapper/control: open failed: No such device 14:15:35 Failure to communicate with kernel device-mapper driver. 14:15:35 0 logical volume(s) in volume group "system" now active 14:15:35 Forcing a filesystem check on R/W guest volume... . 14:15:35 e2fsck 1.38 (30-Jun-2005) 14:15:35 e2fsck: No such device or address while trying to open /dev/system/lvol1 14:15:35 Possibly non-existent or swap device? 14:15:35 60 *-* 'e2fsck /dev/system/lvol1' 14:15:35 +++ RC=8 +++ 14:15:35 Mounting R/W guest volume... . 14:15:35 mount: /dev/system/lvol1 is not a valid block device 14:15:35 63 *-* 'mount -w -t ext3 -n /dev/system/lvol1 /guestvol' /* R/W, type EXT3, no update /etc/mtab */ 14:15:35 +++ RC=32 +++ I'll admit this is over my head, but if we could get it to work it would save DASD as well as provide a means to keep all images consistent. The Large Scale Linux Deployment Redbook (Ch. 8 - Shared Linux filesystems) does talk about "Device filesystem mounts" so maybe this won't work on an LVM. I presume a "Device filesystem" is /dev/dasdx1??? Thanks in advance for any suggestions/guidance. Susan ------------------------------ Date: Thu, 5 Jul 2007 10:36:27 -0400 From: David Boyes <[EMAIL PROTECTED]> Subject: Re: Another Basevol/Guestvol question > In order to be as flexible as possible, we'd like to place all R/W > directories in an LVM. Is this possible? It's possible. In fact it's been discussed here at length.=20 I'd encourage not doing it for / because if something gets munged, it makes it very, very difficult to get the system reassembled to the point you can fix stuff (and you shouldn't have to change the size of / very often if you've gotten everything possible out of the root filesystem and onto logical volumes).=20 ---------------------------------------------------------------------- ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
