linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "John L. Poole" <jlpoole56@gmail.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] 2.03 Volume readable by 2.02?
Date: Sat, 30 Jan 2021 08:14:27 -0800	[thread overview]
Message-ID: <cb4d46f7-2c0c-330d-51bf-48c3b706b2d2@gmail.com> (raw)

I am having problems with a kernel and/or initial ram file system 
booting up in a Xen environment.

The guest virtual machine's root file system is on an lvm volume created 
in Debian.  Dom0 is Debian.
lvm on Debian is: 2.03.02(2).

The guest virtual machine is in Gentoo and I have lvm  2.02.187-r2 
installed therein.  I built my
kernel and initramfs against the 2.02 version of lvm.

My question: should tools of lvm v. 2.02.187 be able to read and access 
a volume created by 2.03.02?

Does the version change between 2.02 and 2.03 mean that the file system 
created by 2.03 tools
may not be readable or accessible by 2.02 tools and libraries?  I'm 
doubting it, but asking.

Gentoo's highest version of lvm is 2.02.187-r2; Gentoo developers have 
lvm 2.03 masked with the note:

      [2.03] Needs LOTS of testing, broke boot on my laptop
      in early attempts, maybe needs matching genkernel work?

source: https://packages.gentoo.org/packages/sys-fs/lvm2

Thank you,

John Poole

_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

             reply	other threads:[~2021-01-30 16:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-30 16:14 John L. Poole [this message]
2021-01-31 23:47 ` [linux-lvm] 2.03 Volume readable by 2.02? John Stoffel
2021-02-02  4:13   ` John L. Poole
2021-02-02 18:02     ` John Stoffel

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=cb4d46f7-2c0c-330d-51bf-48c3b706b2d2@gmail.com \
    --to=jlpoole56@gmail.com \
    --cc=linux-lvm@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).