Error Getting Vgda From Kernel
ERROR: VGDA in kernel and lvmtab are NOT consistent Date: Fri Feb 27 18:36:04 2004 When I try to run vgdisplay, I get this error: vgdisplay -- ERROR: VGDA in kernel and lvmtab are NOT consistent; please run vgscan so, I run vgscan: vgscan vgscan -- reading all physical volumes (this may take a while...) vgscan -- found active volume group "rootvg" vgscan -- found active volume group "webvg01" vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created vgscan -- WARNING: This program does not do a VGDA backup of your volume groups then vgdisplay: vgdisplay -- ERROR: VGDA in kernel and lvmtab are NOT consistent; please run vgscan lvscan -- ERROR: VGDA in kernel and lvmtab are NOT consistent; please run vgscan pvscan looks normal, tried doing pvscan, then vgscan/lvscan again, but got the same thing. I rebooted the machine, same thing. I removed webvg01 (it was empty), and redid things, same thing. I tried: mv /etc/lvmtab /tmp pvscan vgscan vgdisplay same problem.... This is debian stable, using kernel 2.4.22 LVM1, things seem to be working fine otherwise... Thanks, micah [Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]
Threads Find All Thanked Posts Go to Page... RedHat 9 (Linux i386) - man page for lvremove (redhat section 8) Linux & Unix Commands - Search Man Pages Man Page or Keyword Search: man All Sections 1 - General Commands 1m - System Admin 2 - System Calls 3 - Subroutines 4 - Special Files 5 - File Formats 6 - Games 7 - Macros and Conventions 8 - Maintenance Commands 9 - Kernel Interface N - New Commands Select Man Page Set: Linux 2.6 RedHat 9 (Linux i386) Debian 7.7 SuSE 11.3 CentOS 7.0 SunOS 5.10 OpenSolaris 2009.06 BSD 2.11 FreeBSD 11.0 https://www.redhat.com/archives/linux-lvm/2004-February/msg00236.html NetBSD 6.1.5 OSX 10.6.2 OpenDarwin 7.2.1 ULTRIX 4.2 PHP 5.6 Minix 2.0 Plan 9 Unix Version 7 OSF1 5.1 (alpha) POSIX 1003.1 X11R7.4 XFree86 4.7.0 all unix.com man page sets apropos Keyword Search (sections above) LVREMOVE(8) LVREMOVE(8) NAME lvremove - remove a logical volume SYNOPSIS lvremove [-A|--autobackup {y|n}] [-d|--debug] [-f|--force] [-h|--help] [-v|--verbose] Log- icalVolumePath [LogicalVolumePath...] DESCRIPTION lvremove allows you to remove one or more inactive logical volumes. OPTIONS -A, --autobackup y/n Controls http://www.unix.com/man-page/redhat/8/lvremove/ automatic backup of VG metadata after the change ( see vgcfgbackup(8) ). Default is yes. -d, --debug Enables additional debugging output (if compiled with DEBUG). -f, --force Force remove without confirmation. -h, --help Print a usage message on standard output and exit successfully. -v, --verbose Gives verbose runtime information about lvremove's activities. Example "lvremove -f /dev/vg00/lvol1" removes that inactive logical volume unconditionally. DIAGNOSTICS lvremove returns an exit code of 0 for success and > 0 for error: 1 no logical volume name on command line 2 invalid logical volume name 3 error checking existence of volume group 4 inactive volume group 5 error getting VGDA from kernel 6 error getting status of logical volume from kernel 7 open logical volume cannot be removed 8 error reading VGDA 9 error removing logical volume from VGDA 10 error removing logical volume from kernel 11 error writing VGDA to physical volume(s) 95 driver/module not in kernel 96 invalid I/O protocol version 97 error locking logical volume manager 98 invalid lvmtab (run vgscan(8)) 99 invalid command line ENVIRONMENT VARIABLES LVM_AUTOBACKUP If this variable is set to "no" then the automatic backup of VG metadata is turned off. LVM_VG_MAX_BACKUPS This variable determines the backup history depth of kept VGDA copy files in /etc/lvmconf. It can be set to a
Resources Linux man pages Notes & Observations Top 10 reasons to run Linux on VM Linux/390 at Princeton University http://linuxvm.org/info/howtos/lvmrecov.html i/370 Port, aka Bigfoot linuxvm.org Archives Community Community Members Linux-390 Listserv Linux/390Presentations Linux/390 Subscribers Linux/390 Survey Results News Enterprise Linux Today Linux Journal Linux Today Linux https://lists.debian.org/debian-user/2001/09/msg01138.html World Kernel Traffic Fun Ubersoft User Friendly Credits Cast of characters LVM Volume Group Descriptor Area (VGDA) Recovery This information was originally posted to the error getting Linux-390 mailing list on January 16, 2005, by Peter Abresch. We ran into an interesting situation. We suddenly lost access to our DASD due to human error. This corrupted the reiser file systems that we had defined under Logical Volume Manager (lvm). After running reiserfsck, we still had corruption of the error getting vgda Volume Group Descriptor Area (VGDA). Our symptom was that /dev/linuxd01/opt and /dev/linuxd01/tmp were the same file system. An excerpt from the SuSE LVM white paper available at http://www.novell.com/products/linuxenterpriseserver8/whitepapers/LVM.pdf states: The volume group descriptor area (or VGDA) holds the metadata of the LVM configuration. It is stored at the beginning of each physical volume. It contains four parts: one PV descriptor, one VG descriptor, the LV descriptors and several PE descriptors. LE descriptors are derived from the PE ones at activation time. Automatic backups of the VGDA are stored in files in /etc/lvmconf/ (please see the commands vgcfgbackup/vgcfgrestore too). Take care to include these files in your regular (tape) backups as well. LVM will backup the configuration automatically when modifications are made to the LVM configuration. The corruption was on the physical volume somewhere. The goal was to recover the VGDA and not lose any data that was residing on the logical v
Sep 2001 23:36:57 -0400 Message-id: <200109082336.AA3013804282@netcentricnj.com> Reply-to: