From: Michael Marxmeier <mike@msede.com>
To: Tobias Reber <tobias.reber@dkfz-heidelberg.de>
Cc: linux-lvm@msede.com
Subject: Re: [linux-lvm] root filesystem in lvm
Date: Wed, 17 Feb 1999 12:09:08 +0100 [thread overview]
Message-ID: <36CAA354.649CFB49@msede.com> (raw)
In-Reply-To: 003401be5a59$6a3c04a0$6630aec1@trpc.dkfz-heidelberg.de
Tobias Reber wrote:
> On a test system I have put the root filesystem into lvm.
I assume you are using initrd?
> Everything works fine, however during shutdown I cannot
> vgchange -a n to the volumegroup, where the root filesystem sits.
> Does that any harm?
I don't think so. All vgchange -an is supposed to do is unregister
the volume group with the kernel. Since you are going to boot anyway
it does not make a difference.
I had a short look at the source and it seems to be a nop anyway.
> Also did anybody out there look into lilo in order to make the
> kernel bootable from an lvm volume? IMHO lvm looks very keen
> especially if you have large disks, where you still have only
> 8 partitions. I prefer having my filesystem spread out into
> several partitions for /, /usr and so forth.
While this should not be too hard i'm not sure if this makes sense.
Why not designate a small boot area on the disk (/boot) which holds
the kernel image and a minimal recovery system and use a initrd?
However it should be possible to use LILO. As far as i understand
LILO uses partition relative block numbers to load the kernel image.
We just need to make sure that they are relative to the dos style
partition. If included statically in the kernel the lvm driver could
execute the equivalent of a vgchange -ay and we should be able to
mount the root file system.
However this will lead to some kernel bloat as some of the code which
currently resides un user space in lvmlib and vgchange must also be
present in the kernel.
For now i would suggest to make a small boot area and use initrd
to switch to lvm. This will also nicely avoid any stupid BIOS
limitations.
Michael
--
Michael Marxmeier Marxmeier Software GmbH
E-Mail: mike@msede.com Besenbruchstrasse 9
Voice : +49 202 2431440 42285 Wuppertal, Germany
Fax : +49 202 2431420 http://www.msede.com/
next prev parent reply other threads:[~1999-02-17 11:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-17 9:39 [linux-lvm] root filesystem in lvm Tobias Reber
1999-02-17 10:30 ` Heinz Mauelshagen
1999-02-17 11:09 ` Michael Marxmeier [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-02-17 12:26 Tobias Reber
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=36CAA354.649CFB49@msede.com \
--to=mike@msede.com \
--cc=linux-lvm@msede.com \
--cc=tobias.reber@dkfz-heidelberg.de \
/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.