Re: LVM1 - "VGDA in kernel and lvmtab are NOT consistent"error following lvm operations

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello Heinz and any others who might know the answer to this question,

One other question...  As I mentioned in a separate message, I currently have a volume group which seen as "inactive" and "exported" by two separate systems, both of which have physical access to the volume group over fibre to a SAN.  In this two node cluster, one node should always have the volume group as "active".  In fact, currently one node does have the volume group in use, because they are visible using df and mounted.

I would like to make sure that the status displayed by pvscan is corrected to "active" on that node.  Is it safe to run "vgimport" and "vgchange -ay" on the volume that is active, even though pvscan shows it as "inactive" and "exported"???  Will this cause any problem to the file system that is running on top of that volume group???

Thanks!!
Dave


----- Original Message ----
From: Heinz Mauelshagen <mauelshagen@redhat.com>
To: Dave <davo_muc@yahoo.com>; LVM general discussion and development <linux-lvm@redhat.com>
Sent: Monday, July 31, 2006 4:09:20 PM
Subject: Re:  LVM1 - "VGDA in kernel and lvmtab are NOT consistent"error following lvm operations

On Mon, Jul 31, 2006 at 01:50:16AM -0700, Dave wrote:
> 
> 
> Hello,
> 
> I have slightly more info re: this error message I'm seeing.  After running vgdisplay and getting the message:
> 
>     VGDA in kernel and lvmtab are NOT consistent
> 
> I issued an $? to see the exit code and it was 98, which is explained as:
> 
>     invalid lvmtab (run vgscan(8))

E.g. because your root fs is full.
FYI: all lvm commands changing the configuration write the lvmtab.

Have you tried running vgscan yet ?

Heinz

> 
> in the vgdisplay man page.  How does the lvmtab become invalid?  
> 
> I do not want to have to reboot (because this will cause an outage for our customers), but I know from previous experience that the error message will disappear following a reboot.  I'm also hesitant to add new disks, vg's, lv's, and file systems until I can run vgdisplay without an error.  Should I be concerned re: this message???
> 
> 
> Thanks!
> Dave
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Red Hat GmbH
Consulting Development Engineer                   Am Sonnenhang 11
Storage Development                               56242 Marienrachdorf
                                                  Germany
Mauelshagen@RedHat.com                            PHONE +49  171 7803392
                                                  FAX   +49 2626 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-



_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

[Index of Archives]     [Gluster Users]     [Kernel Development]     [Linux Clusters]     [Device Mapper]     [Security]     [Bugtraq]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]

  Powered by Linux