From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mimecast-mx02.redhat.com (mimecast05.extmail.prod.ext.rdu2.redhat.com [10.11.55.21]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 60A822166B28 for ; Sat, 18 Jul 2020 14:28:42 +0000 (UTC) Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [205.139.110.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 4199D924906 for ; Sat, 18 Jul 2020 14:28:42 +0000 (UTC) Received: from [192.168.2.191] ([62.163.200.225]) (authenticated user h.kraal@exonet.nl) by kerio.exonet.nl (Kerio Connect 9.2.11) with ESMTPSA (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256 bits)) for linux-lvm@redhat.com; Sat, 18 Jul 2020 16:28:36 +0200 From: Henk Kraal Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Date: Sat, 18 Jul 2020 16:28:35 +0200 References: <0B6E7FBE-CE2B-4A2F-8560-A47218C0B511@exonet.nl> <20200717162032.GA12965@redhat.com> In-Reply-To: <20200717162032.GA12965@redhat.com> Message-Id: Content-Type: multipart/alternative; boundary="Apple-Mail=_5633D129-DE75-4F92-AC89-E7810B82B9DB" Subject: Re: [linux-lvm] Failed to update old PV extension headers in VG Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: To: LVM general discussion and development --Apple-Mail=_5633D129-DE75-4F92-AC89-E7810B82B9DB Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On 17 Jul 2020, at 18:20, David Teigland wrote: >=20 > On Fri, Jul 17, 2020 at 09:04:32AM +0200, Henk Kraal wrote: >> Hi all, >>=20 >=20 >> I=E2=80=99ve run into an issue when trying to activate an LV which resid= es on a >> read-only loop device. When I run lvchange -a y I get the >> following error: >>=20 >> 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 >>=20 >> I=E2=80=99ve observed this issue when using LVM version 2.03.02 >=20 >> Is there a way I can prevent the update of the extension headers when >> activating the LV? >=20 > 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. > Dave Hi Dave, Thank you for confirming that skipping the header update probably isn=E2=80= =99t possible as I expected. I just wanted to make sure I wasn=E2=80=99t go= ing down a rabbit hole needlessly. The older LVM headers which I=E2=80=99m dealing with are part of the OS of = hundreds of virtual servers which I don=E2=80=99t control. My task is to ma= ke the data on the read-only PV accesable for retrieval. A parameter to ski= p the update would=E2=80=99t have been the best option but I guess I need f= igure out if I can place a (temporary) writeable layer on top of the device= to work around this. Off course I=E2=80=99m open to idea=E2=80=99s if they come to the table ;) With kind regards, Henk --Apple-Mail=_5633D129-DE75-4F92-AC89-E7810B82B9DB Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8

On 17 Jul 202= 0, at 18:20, David Teigland <teigland@redhat.com> wrote:

On Fri, Jul 17, 2020 at 09:04:32AM +0200= , Henk Kraal wrote:
Hi all,


I=E2=80=99ve run into an issue = when trying to activate an LV which resides on a
read-only lo= op 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: bloc= k (4, 0) still dirty
 Failed to write mda header to /dev= /loop0p5 fd -1
 Failed to update old PV extension header= s in VG recursor02-01-vg.
 Volume group "recursor02-01-v= g" not found
 Cannot process volume group recursor02-01-= vg

I=E2=80=99ve 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?
<= /blockquote>
I don't think the= re's a way to tell that version to skip the header
update.  A more recent verson of lvm shoul= d 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.
Dave

Hi Dave,

Thank you for confirming that skipping the header update probably isn=E2= =80=99t possible as I expected. I just wanted to make sure I wasn=E2=80=99t= going down a rabbit hole needlessly.

T= he older LVM headers which I=E2=80=99m dealing with are part of the OS of h= undreds of virtual servers which I don=E2=80=99t control. My task is to mak= e the data on the read-only PV accesable for retrieval. A parameter to skip= the update would=E2=80=99t have been the best option but I guess I need fi= gure out if I can place a (temporary) writeable layer on top of the device = to work around this.

Off course I=E2=80= =99m open to idea=E2=80=99s if they come to the table ;)

With kind regards,

He= nk

--Apple-Mail=_5633D129-DE75-4F92-AC89-E7810B82B9DB--