mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolinux.com>
To: List User <lists@chaven.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Any reason why we can't auto-start LVM (vg's) in the kernel?
Date: Wed, 31 Jan 2001 18:14:04 -0700 (MST)	[thread overview]
Message-ID: <200102010114.f111E4213892@webber.adilger.net> (raw)
In-Reply-To: <033201c08be7$d8e22760$160912ac@stcostlnds2zxj> from List User at "Jan 31, 2001 06:42:20 pm"

Steve, writes:
> Is there any reason why we can't auto-detect/bring up volume-groups in the
> kernel instead of creating a ramdisk volume to do a vgscan and then mount a
> rootlv?

Um, yes, because it won't work.  The user tools do the I/O of LVM state
information to the disk.  The kernel LVM module has no concept of how
LVM information is stored on disk.

> Just trying to see if there is a way (or would make sense) to skip the
> ramdisk stage in mounting a root logical volume.

Need to re-write (or at least seriously enhance) the LVM kernel code to do
this.  Sorry.

Cheers, Andreas
-- 
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-02-01  1:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-01  0:37 Keyboard Scancode Problems Udo A. Steinberg
2001-02-01  0:42 ` Any reason why we can't auto-start LVM (vg's) in the kernel? List User
2001-02-01  1:14   ` Andreas Dilger [this message]
2001-02-01 18:55 ` Keyboard Scancode Problems Pierre Rousselet
2001-02-02  7:11 ` Stefan Frank

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=200102010114.f111E4213892@webber.adilger.net \
    --to=adilger@turbolinux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@chaven.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

all inboxes | Powered by JetHome®