All of lore.kernel.org
 help / color / mirror / Atom feed
* [linux-lvm] Incorrect metadata area header checksum
@ 2008-02-03  2:18 Eckhard Kosin
  2008-02-03  4:15 ` David Robinson
  0 siblings, 1 reply; 14+ messages in thread
From: Eckhard Kosin @ 2008-02-03  2:18 UTC (permalink / raw)
  To: linux-lvm

Hi all,

I just reordered my disk space:  shrunk /dev/hda6, created a new
partition /dev/hda10 with this new space and added /dev/hda10 to the
existing volume group vg_uhu00.  After that I could boot and all seems
to be fine. but running vgscan I get

root@uhu:/home/ecki/backup/uhu# vgscan
  Reading all physical volumes.  This may take a while...
  Incorrect metadata area header checksum
  Incorrect metadata area header checksum
  Couldn't find device with uuid 'Cm961g-X5km-ifdU-r0Cp-ACmd-N9qG-XcieTR'.
  Couldn't find all physical volumes for volume group vg_uhu00.
  Incorrect metadata area header checksum
  Couldn't find device with uuid 'Cm961g-X5km-ifdU-r0Cp-ACmd-N9qG-XcieTR'.
  Couldn't find all physical volumes for volume group vg_uhu00.
  Incorrect metadata area header checksum
  Incorrect metadata area header checksum
  Couldn't find device with uuid 'Cm961g-X5km-ifdU-r0Cp-ACmd-N9qG-XcieTR'.
  Couldn't find all physical volumes for volume group vg_uhu00.
  Incorrect metadata area header checksum
  Couldn't find device with uuid 'Cm961g-X5km-ifdU-r0Cp-ACmd-N9qG-XcieTR'.
  Couldn't find all physical volumes for volume group vg_uhu00.
  Volume group "vg_uhu00" not found

Some additional information:

I'm running Ubuntu 6.06 (dapper)

root@uhu:/home/ecki/backup/uhu# uname -a
Linux uhu 2.6.15-51-386 #1 PREEMPT Thu Dec 6 20:20:49 UTC 2007 i686 GNU/Linux

root@uhu:/home/ecki/backup/uhu# apt-show-versions lvm2
lvm2/dapper uptodate 2.02.02-1ubuntu1.5

root@uhu:/home/ecki/backup/uhu# fdisk -ul

Disk /dev/hda: 40.0 GB, 40007761920 bytes
255 heads, 63 sectors/track, 4864 cylinders, total 78140160 sectors
Units = sectors of 1 * 512 = 512 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1   *          63    14329979     7164958+   7  HPFS/NTFS
/dev/hda2        14329980    78140159    31905090    f  W95 Ext'd (LBA)
/dev/hda5        23438898    25993169     1277136   82  Linux swap / Solaris
/dev/hda6        25993233    38443544     6225156   83  Linux
/dev/hda7        42556248    42684704       64228+  83  Linux
/dev/hda8        42684768    78140159    17727696   8e  Linux LVM
/dev/hda9        14330106    23438834     4554364+  83  Linux
/dev/hda10       38443608    42556184     2056288+  83  Linux

Partition table entries are not in disk order

The volume group vg_uhu00 uses the partitions /dev/hda8, /dev/hda9 and
/dev/hda10 and, I believe, but I'm not sure, /dev/hda5 (swap
partition).  I can't check, because lvdisplay gives the same output as vgscan above.

I have a line

  filter = [ "r|/dev/cdrom|", "r|/dev/hda[1,6,7]|" ]

in my /etc/lvm/lvm.conf

Any suggestions, how to get a clean volume group?

       Thanks a lot

             Ecki

-- 
  Eckhard Kosin
  Kaspar-Kerll-Str. 41
D-81245 München, Germany
  Tel.: (+49)(+89) 88 88 479
  Tel., Fax: (+49)(+89) 835 844
  mailto:Eckhard.Kosin@online.de

^ permalink raw reply	[flat|nested] 14+ messages in thread
* [linux-lvm] Incorrect metadata area header checksum
@ 2014-09-19  3:33 Boylan, Ross
  0 siblings, 0 replies; 14+ messages in thread
From: Boylan, Ross @ 2014-09-19  3:33 UTC (permalink / raw)
  To: linux-lvm@redhat.com

While doing some work on my system I added a new disk, GPT partitioned it, and created a new VG "mongo" out of the big partition (~1TB).  After various operations detailed below, and a few hours of apparent success, things started to go wrong.  My root file system (/, not just /root), in my other VG "turtle", experienced read problems and was remounted read-only.  The new filesystem on mongo also became unreadable.  vgsan and other LVM commands, which had been happy, started reporting
Incorrect metadata area header checksum
although they still reported info on turtle--but not mongo.

First question: If vgdisplay turtle displays the incorrect metadata message, is that a sure sign that turtle's metadata is bad, or could it be from mongo?
At first I thought it meant both VG's (on 2 separate disks) had failed, but now I'm not so sure--I've been able to reboot with turtle, though nothing in mongo is accessible.

Second question: what could cause the problem(s)?

Behind these question I'm wondering what state my system is in, and whether this indicates LVM is unsafe to use in the way I do.  It's worked great before this.  I think I have to reinstall and restore from backups, since bad things were happening to my filesystems.

Thanks.

Ross Boylan

Details:
For both VG's I allocated all free space and wiped it:
lvcreate -l 100%FREE -n tozero turtle
cryptsetup --key-file /etc/crypt/big1ah zero_crypt /dev/turtle/tozero
dd if=/dev/zero of=/dev/mapper/zero_crypt
I then freed the LV's so created and added some of the resulting free space to other LV's.
It seems possible that this may have stressed LVM too far.  "turtle" also had active snapshots (no thin provisioning).

The growth was considerable, e.g., from 20G to 40G.  Maybe the block size changed?  But I made no changes to the root filesystem, and that's what failed first.

The necessary crypto headers disappeared from  some of the LV's, although now that I've rebooted they seem to be back (?) for turtle.  The RAID headers tested fine throughout.  It looks as if the pv for mongo is still recognized, even though the VG is not:
# date; pvdisplay
Thu Sep 18 20:28:22 PDT 2014
  Incorrect metadata area header checksum
  --- Physical volume ---
  PV Name               /dev/md1
  VG Name               turtle
  PV Size               696.68 GB / not usable 2.00 MB
  Allocatable           yes
  PE Size (KByte)       4096
  Total PE              178350
  Free PE               24932
  Allocated PE          153418
  PV UUID               3cc3d1-tvjW-ZVwP-Gegj-NKF3-S2bA-AEQ59e

  "/dev/sda2" is a new physical volume of "931.51 GB"
  --- NEW Physical volume ---
  PV Name               /dev/sda2
  VG Name
  PV Size               931.51 GB
  Allocatable           NO
  PE Size (KByte)       0
  Total PE              0
  Free PE               0
  Allocated PE          0
  PV UUID               iTdabJ-Unml-Qs4h-wIQE-cpo0-7nWQ-tzRlCU


0.90 metadata for RAID.

VG mongo is made of one partition on one physical disk
VG turtle is made of one software RAID-1 disk; the RAID is made of GPT partitions on 2 disks.
The one LV on mongo had crypt (in the cryptsetup sense) on it, and many of the LV's on turtle (including root) used crypto

Debian Lenny (very old--I was getting ready to upgrade) on amd64.
linux kernel 2.6.32-5-amd64 (which is newer than Lenny)
lvm2                             2.02.39-8                              The Linux Logical Volume Manager
cryptsetup                   2:1.0.6-7     (ignore the 2: prefix; it's 1.0.6)               configures encrypted block devices
mdadm                         2.6.7.2-3                              tool to administer Linux MD arrays (software RAID)

^ permalink raw reply	[flat|nested] 14+ messages in thread
* [linux-lvm] Incorrect metadata area header checksum
@ 2006-11-02 13:38 C'est Pierre
  2006-11-02 22:02 ` Luca Berra
  0 siblings, 1 reply; 14+ messages in thread
From: C'est Pierre @ 2006-11-02 13:38 UTC (permalink / raw)
  To: LVM general discussion and development

Hello,

I am running through this error in CentOS 4.3, has anyone gone through
this situation?

I added a disk to the VG, initialized it with pvcreate and vgextended
our VG. However, it's constantly showing these messages:

# vgdisplay
  Incorrect metadata area header checksum
  /var/lock/lvm/V_VG00: open failed: No space left on device
  Can't lock VG00: skipping

which don't seem to be true at all:

Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VG00-LogVol00
                      9.0G  7.0G  1.6G  83% /
/dev/sda1              99M  9.0M   85M  10% /boot
/dev/mapper/VG00-LogVol01
                       14G  510M   13G   4% /opt/lampp/var
/dev/mapper/VG00-LogVol02
                      977M   18M  910M   2% /tmp


Not of the disks is fully used, yet I can't even write to /root

# >foobar
-bash: foobar: No space left on device

Any idea?

Thanks
Pierre

^ permalink raw reply	[flat|nested] 14+ messages in thread
* [linux-lvm] Incorrect metadata area header checksum
@ 2006-03-11  2:43 Bernard Fay
  0 siblings, 0 replies; 14+ messages in thread
From: Bernard Fay @ 2006-03-11  2:43 UTC (permalink / raw)
  To: LVM general discussion and development

For any LVM commands I run I receive the following message:

Incorrect metadata area header checksum

and/or 

Volume group mapper doesn't exist


Someone knows why and how it could be fixed?  I run Debian etch with
kernel 2.6.12-1-386 and lvm2 version 2.01.04-5.

TIA,
Bernard

^ permalink raw reply	[flat|nested] 14+ messages in thread
* [linux-lvm] Incorrect metadata area header checksum
@ 2005-10-18 12:24 Eric S. Johansson
  0 siblings, 0 replies; 14+ messages in thread
From: Eric S. Johansson @ 2005-10-18 12:24 UTC (permalink / raw)
  To: LVM general discussion and development

I could really use some advice here.  Is this something to worry about 
something I can fix?

  pvdisplay
   Incorrect metadata area header checksum
   Incorrect metadata area header checksum
   Incorrect metadata area header checksum
   Incorrect metadata area header checksum
   --- Physical volume ---
   PV Name               /dev/md0
   VG Name               raid_vg
   PV Size               232.88 GB / not usable 0
   Allocatable           yes
   PE Size (KByte)       4096
   Total PE              59618
   Free PE               1960
   Allocated PE          57658
   PV UUID               5o1utA-eN0O-yJqx-4N0Q-NrjT-EpRn-dxyAyT

   --- NEW Physical volume ---
   PV Name               /dev/sda1
   VG Name
   PV Size               232.88 GB
   Allocatable           NO
   PE Size (KByte)       0
   Total PE              0
   Free PE               0
   Allocated PE          0
   PV UUID               Q2UgM6-QG6D-Lrdi-KnAT-Uw7w-6j75-kAO0l3


   Incorrect metadata area header checksum

^ permalink raw reply	[flat|nested] 14+ messages in thread
* [linux-lvm] incorrect metadata area header checksum
@ 2005-05-12  0:44 Geoff
  0 siblings, 0 replies; 14+ messages in thread
From: Geoff @ 2005-05-12  0:44 UTC (permalink / raw)
  To: linux-lvm

[-- Attachment #1: Type: text/plain, Size: 1271 bytes --]

Hi,
 
OK, here goes the story, hope someone can help (disclaimer, I am relatively
new to linux and VERY new to LVM).
 
Was using linux kernel 2.4.30 with LVM2 - initialised PV, created VG no
problem. Couldnt create LV due to device mapper. Turns out that for some
reason it didnt compile into the kernel correctly. Tried recompiling a few
times, still no go.
 
Thought, blow it, try 2.6 so compiled and booted off 2.6.11.8. 
 
Everything seemed ok, except I couldnt create the LV due to a read/write
error. Search archives, no luck.
Decided to remove VG and recreate it.
Removed VG got read/write errors.
Now, I cant do anything getting "incorrect metadata area header checksum"
messages.
pvscan says:
"incorrect metadata area header checksum"
"incorrect metadata area header checksum"
"incorrect metadata area header checksum"
"incorrect metadata area header checksum"
PV /dev/sda7                      lvm2 [198.35 GB]
Total: 1 [198.35 GB] / in use: 0 [0  ] /in no VG: 1 [198.35 GB]
 
So, I have 2 problems:
1. resolving this error and initialising the PV and creating the VG again,
2. Creating the LV.
 
help! :P
 
thanks
Geoff
Webmaster
Maxnet Systems Administration
PH 0508 MAXNET
Mobile: 021 919 220
Fax +64-9-3007227
www.maxnet.co.nz <http://www.maxnet.co.nz/> 
 

[-- Attachment #2: Type: text/html, Size: 4213 bytes --]

^ permalink raw reply	[flat|nested] 14+ messages in thread
* [linux-lvm] Incorrect metadata area header checksum
@ 2003-06-02  9:34 jeff
  2003-06-02 10:23 ` Alasdair G Kergon
  0 siblings, 1 reply; 14+ messages in thread
From: jeff @ 2003-06-02  9:34 UTC (permalink / raw)
  To: linux-lvm

hi-

what does this error mean, and how do i rectify it? i have existing lvm
volumes on this box, but creating this big one (~350gb) on my new
software-raid5 array is giving me grief. i can mke2fs /dev/md2 just
fine, but when i try to install lvm2..:

root@cerulean:~# pvscan
  PV /dev/md1   VG raid1   lvm1 [15.65 GB / 0    free]
  Total: 1 [0   ] / in use: 1 [0   ] / in no VG: 0 [0   ]

root@cerulean:~# pvcreate /dev/md2
  Failed to read label on physical volume /dev/md2
  Physical volume "/dev/md2" successfully created

root@cerulean:~# vgcreate raid5 /dev/md2
  Incorrect metadata area header checksum
  Incorrect metadata area header checksum
  Volume group "raid5" successfully created

root@cerulean:~# vgdisplay raid5
  Incorrect metadata area header checksum
  Incorrect metadata area header checksum
  Volume group "raid5" doesn't exist

more info:

root@cerulean:~# uname -a
Linux cerulean 2.4.21-rc2-ac2 #1 Sun May 18 12:08:13 PDT 2003 i686 GNU/Linux

root@cerulean:~# egrep 'DEV_DM|DEV_LVM' /boot/config-2.4.21-rc2-ac2 
# CONFIG_BLK_DEV_LVM is not set
CONFIG_BLK_DEV_DM=y

root@cerulean:~# dpkg -s lvm2 | grep Version
Version: 1.95.15-1

root@cerulean:~# dpkg -s raidtools2 | grep Version
Version: 1.00.3-2

root@cerulean:~# cat /proc/mdstat 
Personalities : [raid1] [raid5] 
read_ahead 1024 sectors
md0 : active raid1 sdb1[1] sda1[0]
      976768 blocks [2/2] [UU]
      
md1 : active raid1 sdb3[1] sda3[0]
      16418752 blocks [2/2] [UU]
      
md2 : active raid5 sdd1[3] sdc1[2] hdc1[1] hda1[0]
      351654528 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
      
unused devices: <none>

thanks,

jeff

^ permalink raw reply	[flat|nested] 14+ messages in thread
end of thread, other threads:[~2014-09-19  3:33 UTC | newest]

Thread overview: 14+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-02-03  2:18 [linux-lvm] Incorrect metadata area header checksum Eckhard Kosin
2008-02-03  4:15 ` David Robinson
2008-02-03 12:21   ` Alasdair G Kergon
2008-02-03 18:14     ` Eckhard Kosin
2008-02-04  3:06       ` David Brown
2008-02-04 10:36         ` Alasdair G Kergon
  -- strict thread matches above, loose matches on Subject: below --
2014-09-19  3:33 Boylan, Ross
2006-11-02 13:38 C'est Pierre
2006-11-02 22:02 ` Luca Berra
2006-03-11  2:43 Bernard Fay
2005-10-18 12:24 Eric S. Johansson
2005-05-12  0:44 [linux-lvm] incorrect " Geoff
2003-06-02  9:34 [linux-lvm] Incorrect " jeff
2003-06-02 10:23 ` Alasdair G Kergon

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.