On Wednesday 24 January 2007 09:49, Jim Moling wrote:
>I setup a test file server with an LVM consisting of 2 3390-9's, which I
>then loaded up with files, and it has been working just fine (couple of
>months now).
>For no reason that I can determine, the LVM has been "lost", resulting in
>errors at boot time, thus causing Linux to come up in maintenance mode.
From what you have written, it sound like the DASD on which your LVM
filesystem resides is not linked to your guest, or not known to the Linux
DASD device driver. The output you included is from vgscan(8) and
vgchange(8):
>Scanning for LVM volume groups...
> Reading all physical volumes. This may take a while...
> No volume groups found
>Activating LVM volume groups...
> No volume groups found
>..done
This tells me that Linux is just not seeing any of your physical volumes, so
those devices (eg. /dev/dasdd1) are just not there. Either the VM devices
are not in your VM directory entry for that guest (unlikely), or the Linux
kernel just does not know about them (more likely). See if a CP QUERY DASD
lists the devices you expect to be your physical volumes for that LVM
filesystem.
If not, add those devices to the VM directory. Otherwise, the problem is with
the Linux kernel not being able to find those devices. How you fix this
depends on which version of the kernel you are running (and thus which
device detection mechanism it uses). Which Linux distro are you running?
- MacK.
-----
Edmund R. MacKenty
Software Architect
Rocket Software, Inc.
Newton, MA USA
----------------------------------------------------------------------
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
