From: rich turner <rich@storix.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] lvm/devfs bug?
Date: Wed Apr 9 18:58:01 2003 [thread overview]
Message-ID: <1049932652.7946.4.camel@rich-laptop> (raw)
In-Reply-To: <20030409072130.GD1366@tykepenguin.com>
i dont completely agree with that because even when i use a kernel that
does not have devfs i still get the same symptoms. even though
/proc/partitions does not have a partition for a disk pvcreate still
complains that there is one. pvcreate must be looking someplace else or
there is a bug within lvm.
now, if i create a pv within a partition there are no complaints, lvm
will continue normally. it appears to only happen when i want to create
a pv on the entire disk.
why does pvcreate think there is a partition when there clearly isnt
one?
On Wed, 2003-04-09 at 00:21, Patrick Caulfield wrote:
> On Tue, Apr 08, 2003 at 02:22:23PM -0700, Rich Turner wrote:
> > even though devfs is compiled in the kernel it actually is not mounted
> > at this time. i have tried it using devfs long names also with no
> > success.
>
> If devfs is in the kernel you MUST have it mounted for LVM. It's to do with the
> interaction between /proc/partitions and LVM.
>
>
>
> patrick
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2003-04-09 18:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 14:22 [linux-lvm] lvm/devfs bug? Rich Turner
2003-04-08 14:33 ` Alasdair G Kergon
2003-04-08 15:06 ` rich turner
2003-04-08 15:43 ` Luca Berra
2003-04-08 16:22 ` Rich Turner
2003-04-08 16:57 ` Rich Turner
2003-04-09 2:21 ` Patrick Caulfield
2003-04-09 18:58 ` rich turner [this message]
2003-04-10 13:08 ` rich turner
2003-04-10 14:58 ` Kevin P. Fleming
2003-04-10 16:10 ` rich turner
2003-04-10 16:22 ` 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=1049932652.7946.4.camel@rich-laptop \
--to=rich@storix.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