From: Patrick Caulfield <caulfield@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] help: can't read name(s) of physical volumes (Debian kernel weirdness also involved)
Date: Sun Dec 15 10:00:02 2002 [thread overview]
Message-ID: <20021215160028.GA7519@tykepenguin.com> (raw)
In-Reply-To: <Pine.GSO.4.44L-027.0212142036200.10732-100000@unix3.andrew.cmu.edu>
On Sat, Dec 14, 2002 at 08:53:21PM -0500, Daniel J Hannum wrote:
> Hi. I feel dumb for subscribing to the list just so I can yell out my
> problem and hopefully someone can help, but I'm at the end of my rope
> here.
>
> Here's the situation. I just installed Debian 3.0 testing and I set it up
> so that I was using their lvm10 package (version 1.0.4-6) for /usr, /var
> /home, etc. (NOT /) It works fine off the kernel that Debian uses in its
> install (2.4.18-bf2.4). BUT, if I install a stock Debian kernel with
> apt-get (kernel-image-2.4.18-k7), lvm cannot see my physical volumes at
> boot-time.
The stock debian kernel has devfs compiled into it. :(
So if you look in /proc/partitions it will show devfs device names
rather than the "traditional" ones, although the devfs names are not
actually avaiable to you. This confuses LVM.
What you will need to do is to mount devfs at boot time (devfs=mount on
the kernel command-line) on /dev and run devfsd (apt-get install devfsd) and
things should work.
--
patrick
next prev parent reply other threads:[~2002-12-15 10:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.4.44L-027.0212142036200.10732-100000@unix3.andrew.cmu. edu>
2002-12-14 19:53 ` [linux-lvm] help: can't read name(s) of physical volumes (Debian kernel weirdness also involved) Daniel J Hannum
2002-12-14 22:29 ` Steven Lembark
2002-12-15 7:27 ` Daniel J Hannum
2002-12-15 10:00 ` Patrick Caulfield [this message]
2002-12-15 17:25 ` Daniel J Hannum
2002-12-16 2:17 ` Patrick Caulfield
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=20021215160028.GA7519@tykepenguin.com \
--to=caulfield@sistina.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 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.