From: Luca Berra <bluca@comedia.it>
To: Linux LVM <linux-lvm@sistina.com>
Subject: Re: [linux-lvm] is devfs required?
Date: Fri Feb 22 14:13:02 2002 [thread overview]
Message-ID: <20020222201251.GG30259@colombina.comedia.it> (raw)
In-Reply-To: <20020221143602.F328@majestic.ukshells.co.uk>
On Thu, Feb 21, 2002 at 02:36:02PM +0000, Vincent AE Scott wrote:
> i'm using LVM on a 2.4.17-19mdk kernel patched up to 1.0.3
> it *appears* that when i boot up without devfs support, i frequently
> cant create/extened/mount filesystems. but when i boot up with devfs
> support it seems to work.
>
> is devfs required to use LVM?
i am also using 2.4.17-19mdk + LVM
the issue is not with the kernel portion but with the tools portion
if you start using lvm with devfs you are stuck with it and vice-versa.
i proposed a workaround about 13 months ago, but never actually got
to code it. :(
> without it, ive seen lvcreate SEGV when attempting to create a new
> volume.
which version of the tools are u using?
if it is current can you provide a debug output?
if you want to build an rpm for recent tools fetch spec and
patch from http://www.comedia.it/bluca/lvm and adapt it
to 1.0.3 (will upgrade the site soon)
the mkinitrd stuff does not work with 2.4.17-19mdk and xfs
> or are there any known problems with using LVM on an SMP host? i cant
> think of anything else that might be causing these strange problems.
no known issues.
L.
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
next prev parent reply other threads:[~2002-02-22 14:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-21 8:36 [linux-lvm] is devfs required? Vincent AE Scott
2002-02-22 3:25 ` Heinz J . Mauelshagen
2002-02-22 8:21 ` Benjamin Scott
2002-02-22 14:15 ` Luca Berra
2002-02-22 14:13 ` Luca Berra [this message]
2002-02-22 15:40 ` Vincent AE Scott
2002-02-23 7:28 ` 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=20020222201251.GG30259@colombina.comedia.it \
--to=bluca@comedia.it \
--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