From: Luca Berra <bluca@comedia.it>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Re: putting lvm autodetect into the kernel ala md
Date: Thu, 31 Mar 2005 09:38:17 +0200 [thread overview]
Message-ID: <20050331073816.GD3879@percy.comedia.it> (raw)
In-Reply-To: <c23be1c30503300738690039d8@mail.gmail.com>
On Wed, Mar 30, 2005 at 11:38:16PM +0800, Andy Sy wrote:
>Luca Berra wrote:
>
>> >Just like the kernel is now able to autodetect and
>> >autoenable md RAID arrays, are there plans to make
>
>> kernel autodetection of md arrays is almost always a
>> bad idea, it is far better to use mdadm in user space for that.
>
>Why is this necessarily so? RAID autodetect seems to
>avoid a lot of configuration hassles especially when your
>root partition is involved. Any horror stories to tell?
yes, read the linux-raid mailing list for those, i am tired of beating
the same dead horse.
>> >lvm do the same? (i.e integrate the functionality
>> >of vgscan / vgchange -ay,-an into the kernel)
>
>> no, it is an user space task, there is no reason to
>> burden the kernel with this.
>
>People have recommended against using an LVM
>volume for your root partition citing the hassle of
>a rescue disk as being the main reason. If lvm volume
this is just ridicolous fud.
in what cases you would need a rescue disk?
are those really different from the cases you'd need a rescue disk for a
normal partition-table based system.
besides, every live distro on earth now supports lvm and can be used as
a recovery tool.
>autodetect and enabling were in the kernel, then
>this would no longer be the case.
why?
>I have a good reason for wanting my root partition
>to be a logical volume: this is because I can
i have been using my root partition as a logical volume for several
years now.
>Unless lvm detect/enable functionality were built into
>the kernel though, you will always have to live with a
>physical partition holding /boot - the case today
>with LVM and RAID0, but not RAID1 (from which it is
>possible to boot directly off of).
i don't have a separate partition for /boot on my lvm systems.
the only reason i needed a separate boot partition was when i had a
system using raid5, so i had to have a separate raid1 partition for
booting.
Reading your arguments it appeare you are mis-informed and make a lot of
confusion between a boot loader (which is the only limitation we have in
loading a kernel/initrd/initramfs) and what the kernel can do.
Regards,
Luca
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
next prev parent reply other threads:[~2005-03-31 7:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.11694.1112144246.19557.linux-lvm@redhat.com>
2005-03-30 1:02 ` [linux-lvm] Re: Welcome to the "linux-lvm" mailing list Andy Sy
2005-03-30 6:52 ` Luca Berra
2005-03-30 15:38 ` [linux-lvm] Re: putting lvm autodetect into the kernel ala md Andy Sy
2005-03-31 7:38 ` Luca Berra [this message]
2005-04-01 0:39 Andy Sy
2005-04-01 17:41 ` Luca Berra
-- strict thread matches above, loose matches on Subject: below --
2005-04-01 1:16 Andy Sy
2005-04-01 17:41 ` Luca Berra
2005-04-01 19:59 ` Andy Sy
2005-04-04 22:05 ` Luca Berra
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=20050331073816.GD3879@percy.comedia.it \
--to=bluca@comedia.it \
--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.