It shouldn't be needed. When we ran into this, it didn't do any damage, we just ended up with the same filesystem mounted in two places.
The usual cause of the problem is a device missing from the configuration. LVM won't activate an incomplete VG, but instead of giving an error, it mounts the wrong one later. Fixing the underlying problem and activating the VG usually straightens things out. SLES8 WILL give an error trying to mount an LV in an inactive VG. This usually halts the IPL process at the "local filesystem mount" point, while the root FS is still in read-only mode. You can re-ipl without causing damage from here. Of course, if you have to fix fstab at this point, it's a little difficult, but the error messages give a hint about how to remount / read-write. > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Beth Somers > Sent: Tuesday, December 16, 2003 9:08 AM > To: [EMAIL PROTECTED] > Subject: Re: [LINUX-390] LVM Help > > > > > > > I noticed you had two responses. The one is one thing that I > was afraid of, > a bug in the lvm supplied on sles7. That we could have found > in the support > database. What about that vgcfgrestore. Did you try that? > > Beth Somers > Certified Consulting I/T Specialist - Large and Storage Systems > [EMAIL PROTECTED] > > > > > David Holt > <[EMAIL PROTECTED] To: > [EMAIL PROTECTED] > .fl.us> cc: > Sent by: Linux on Subject: LVM Help > 390 Port > <[EMAIL PROTECTED] > IST.EDU> > > > 12/15/2003 04:59 > PM > Please respond to > Linux on 390 Port > > > > > > > Yesterday I was trying to expand an existing LVM filesystem and it > appeared ok after I issued the resize2fs command but after I rebooted > the Linux instance the filesystem was mounted but it was not > the correct > file system. It appears LVM got the expanded file system > confused with > another file system. In trying to correct this problem I think I > corrupted another file system. When I issue a vgdisplay command I get > the following: > > vgdisplay -- ERROR: VGDA in kernel and lvmtab are NOT consistent; > please run vgscan > > I ran vgscan but it didn't help. I found what appeared to be backups > of volume group information in /etc/lvmconf directory. Is > there a way > to recover the LVM to a previous state or recover the volume > group info? > > > We are SLES 7 with the 2.4.7 kernel. > >
