From: Alasdair G Kergon <agk@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Problems resizing physical volume
Date: Wed, 14 Apr 2010 23:27:40 +0100 [thread overview]
Message-ID: <20100414222740.GE13021@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1004141752130.14791@bmsred.bmsi.com>
On Wed, Apr 14, 2010 at 05:57:05PM -0400, Stuart D. Gathman wrote:
> This reduces LVM to the equivalent of a partition as far as the
> boot code is concerned.
That's been discussed, but nothing happened. It's pretty easy to do.
Instead a primitive parser was written for grub2 independently of the
LVM2 developers that can read a subset of LVM2 metadata while being
unaware of its own limitations - so it is straightforward to generate
correct LVM2 metadata that the parser will misinterpret and use to
activate volumes jumbling up your data. Don't use it without first
testing it processes your specific metadata correctly.
A supportable redesign would see the code that grubN uses provided
by the upstream LVM2 package (in some agreed form - library or
source) so that the grub package itself has no specific LVM2 knowledge,
but imports what it needs through some agreed interface.
If people want to work on this - i.e. liase with the grub and lvm
developers to design and code up a suitable interface - please step
forward and start talking to us!
Alasdair
next prev parent reply other threads:[~2010-04-14 22:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 9:42 [linux-lvm] Problems resizing physical volume Avi Kivity
2010-04-14 14:47 ` Phillip Susi
2010-04-14 14:59 ` Avi Kivity
2010-04-14 15:04 ` Avi Kivity
2010-04-14 15:14 ` Phillip Susi
2010-04-14 20:05 ` Stuart D. Gathman
2010-04-14 21:12 ` Phillip Susi
2010-04-14 21:28 ` Alasdair G Kergon
2010-04-14 21:57 ` Stuart D. Gathman
2010-04-14 22:27 ` Alasdair G Kergon [this message]
2010-04-24 1:39 ` Ron Johnson
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=20100414222740.GE13021@agk-dp.fab.redhat.com \
--to=agk@redhat.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).