From: lembark@wrkhors.com
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Root on LV
Date: Tue, 18 Sep 2001 12:23:08 -0500 [thread overview]
Message-ID: <26260000.1000833788@duke.wrkhors.com> (raw)
In-Reply-To: <OFE0B97CD3.C5A33405-ON85256ACA.004E9D80@raleigh.ibm.com>
-- Steve Pratt <slpratt@us.ibm.com> on 09/17/01 09:26:12 -0500
>>> > dobos_s@IBCnet.hu wrote:
>>> > > My kernel has no modules.
>>> > > Why should I create an ext2 partition for holding an initrd which is
> not
>>> > > doing any essential things except vgscan and vgchange -ay ?
>>>
>>> You don't need vgscan at boot time unless the disks have moved around.
>>> You DO need "vgchange -a y" in order to load the LVM data into the
> kernel.
>
>> If you are running EVMS you don't need that.
>
>> But you need EVMS tools which are not available fo far :-(
>
> Actually that is not entirely true. All of the volume group and physical
> volumes tools are done. We have started on all of the logical volume
> commands. We have stand alone utilities which minic the LVM ones, as well
> as a GUI which integrates LVM function with other volume management
> functions such as partitioning.
Q: Why bother to put 64MB on an LVM?
The root volume doesn't grow much (make it 128MB and it'll never need to
grow).
If you ever have a problem with LVM you'll end up with an unbootable
system...
next prev parent reply other threads:[~2001-09-18 17:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-17 14:26 [linux-lvm] Root on LV Steve Pratt
2001-09-18 17:23 ` lembark [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-19 18:54 Steve Pratt
2001-09-19 19:43 ` lembark
2001-09-20 5:15 ` Adrian Phillips
2001-09-06 14:03 dobos_s
2001-09-06 14:10 ` josv
2001-09-10 11:31 ` Heinz J . Mauelshagen
2001-09-06 14:42 ` svetljo
2001-09-06 15:37 ` Andreas Dilger
2001-09-06 16:35 ` svetljo
2001-09-06 17:52 ` Luca Berra
2001-09-10 11:29 ` Heinz J . Mauelshagen
2001-09-06 16:53 ` lembark
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=26260000.1000833788@duke.wrkhors.com \
--to=lembark@wrkhors.com \
--cc=linux-lvm@sistina.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