archive mirror
 help / color / mirror / Atom feed
From: David Teigland <>
To: Henk Kraal <>
Subject: Re: [linux-lvm] Failed to update old PV extension headers in VG
Date: Fri, 17 Jul 2020 11:20:32 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, Jul 17, 2020 at 09:04:32AM +0200, Henk Kraal wrote:
> 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

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

I don't think there's a way to tell that version to skip the header
update.  A more recent verson of lvm should work, and let you use the PV
without updating the header.  It will not attempt updates from commands
which are not otherwise updating lvm metadata.

  reply	other threads:[~2020-07-17 16:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-17  7:04 Henk Kraal
2020-07-17 16:20 ` David Teigland [this message]
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).