archive mirror
 help / color / mirror / Atom feed
From: Henk Kraal <>
Subject: [linux-lvm] Failed to update old PV extension headers in VG
Date: Fri, 17 Jul 2020 09:04:32 +0200	[thread overview]
Message-ID: <> (raw)

Hi all,

I’ve run into an issue when trying to activate an LV which resides on a read-only loop device. When I run lvchange -a y <LV Path> I get the following error:

  Error writing device /dev/loop0p5 at 4096 length 512.
  bcache_invalidate: block (4, 0) still dirty
  Failed to write mda header to /dev/loop0p5 fd -1
  Failed to update old PV extension headers in VG recursor02-01-vg.
  Volume group "recursor02-01-vg" not found
  Cannot process volume group recursor02-01-vg

I’ve observed this issue when using LVM version 2.03.02 (Debian 10) to activate the LV. The volume I’m trying to mount comes from a host which has LVM version 2.02.168 which explains why headers are attempted to be updated.

The lvchange commando is part of a file restore procedure. The backup solution we are using (Xen Orchestra) creates chained .vhd files but is unable to access LVM volumes which reside across multiple PV’s. As restoring a full VM is often not required a solution was found in using vhdimount and losetup to access the data and get the required files from the backups.

# vhdimount 20200714T234001Z.vhd /mnt/20200714T234001Z
# losetup -P -r -f /mnt/20200714T234001Z/vhdi1
# lsblk /dev/loop0
loop0       7:0    0   42G  1 loop
|-loop0p1 259:0    0  243M  1 part
|-loop0p2 259:1    0    1K  1 part
`-loop0p5 259:2    0 41.8G  1 part

Given the error I would guess the source of this issue might be caused by the following commit:;a=commit;h=070c0d31ab3847240081e7593f959b03e716923d

Is there a way I can prevent the update of the extension headers when activating the LV?

With kind regards,


             reply	other threads:[~2020-07-17  7:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-17  7:04 Henk Kraal [this message]
2020-07-17 16:20 ` David Teigland
2020-07-18 14:28   ` Henk Kraal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \
    --subject='Re: [linux-lvm] Failed to update old PV extension headers in VG' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).