From: paddy@panici.net
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Best practice: metadata backup
Date: Tue, 7 Aug 2007 21:44:48 +0000 [thread overview]
Message-ID: <20070807214448.GD3732@localhost.localdomain> (raw)
In-Reply-To: <20070807190153.GV2064@agk.fab.redhat.com>
On Tue, Aug 07, 2007 at 08:01:53PM +0100, Alasdair G Kergon wrote:
> > AIX treats the boot LV specially, and ensures
> > that its PEs are contiguous at the beginning of the disk(s).
>
> Nothing is stopping a linux installer doing that today:
> --alloc contiguous and specify the extents.
(its been a long time but) last time I looked there was no facility
to flag an LV in a manner that would accord it treatment from the
various utilities appropriate to it's status as a boot volume
(such as, for example, not moving about). Of course, when I looked
there wasn't any functionality in the utilities that did anything
to worry about :-) (but user-space code is easier written than
on-disk representations are changed)
(unless its already been done ...) by the time anyone gets around to it,
the various bios limitation of PCs, etc will all be just a memory.
> But if grub supports LVM2 properly (add a trivial mapping layer from LV
> extents to physical sectors, then populate it from the LVM2 metadata
> across an agreed interface from a library maintained as part of the lvm2
> package) it won't require anything like that of course - the hardest
> problem I think is actually for it to identify the right disks to use.
(and yet strangely we all manage to boot ... !?!? )
... or everyone uses a boot-loader that reads filesystems, and they all
learn to read LVM too :-)
Regards,
Paddy
prev parent reply other threads:[~2007-08-07 21:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 4:17 [linux-lvm] Best practice: metadata backup Stuart D. Gathman
2007-08-07 19:01 ` Alasdair G Kergon
2007-08-07 20:56 ` Stuart D. Gathman
2007-08-07 21:34 ` Alasdair G Kergon
2007-08-08 19:03 ` Stuart D. Gathman
2007-08-08 21:21 ` Alasdair G Kergon
2007-08-09 7:23 ` John Hearns
2007-08-07 21:44 ` paddy [this message]
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=20070807214448.GD3732@localhost.localdomain \
--to=paddy@panici.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.