linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] is devfs required?
Date: Fri Feb 22 03:25:02 2002	[thread overview]
Message-ID: <20020222102259.A16552@sistina.com> (raw)
In-Reply-To: <20020221143602.F328@majestic.ukshells.co.uk>; from linux.lvm@codex.net on Thu, Feb 21, 2002 at 02:36:02PM +0000

On Thu, Feb 21, 2002 at 02:36:02PM +0000, Vincent AE Scott wrote:
> Hi there,
> i've been tinkering with LVM, but i'm having some issues with it, and i
> was wondering if anyone here could help shed some light for me?
> 
> 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?

No, but in case you use devfs, you need to go with the long devfs
device pathes.

> 
> without it, ive seen lvcreate SEGV when attempting to create a new
> volume.  

Hm.
Seems to be more of a tool bug.
Which tool version are you using?
In case of 0.9.1 Beta something, you should update to 1.0.3, which we
released last Monday.

> 
> 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.
> 
> oh, and FYI, it was setup up using 1.0.1-rc4ish

That should be fine but as said, you could still run older tools
which might be causing the SEGV.

> 
> TIA,
> -vince
> 
> -- 
> PGP key:  http://codex.net/pgp/pgp.asc
> 
>  Smash forehead on keyboard to continue... 
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

-- 

Regards,
Heinz    -- The LVM Guy --

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2002-02-22  3:25 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 [this message]
2002-02-22  8:21 ` Benjamin Scott
2002-02-22 14:15   ` Luca Berra
2002-02-22 14:13 ` Luca Berra
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=20020222102259.A16552@sistina.com \
    --to=mauelshagen@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).