Linux LVM users
 help / color / mirror / Atom feed
From: Patrick Caulfield <caulfield@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM with devfs questions and patches
Date: Tue, 13 Feb 2001 16:09:22 +0000	[thread overview]
Message-ID: <20010213160922.G556@tykepenguin.com> (raw)
In-Reply-To: <20010212205229.A3375@trez42.net>; from ben@trez42.net on Mon, Feb 12, 2001 at 08:52:29PM +0100

On Mon, Feb 12, 2001 at 08:52:29PM +0100, Benoit Gaussen wrote:
> Hi,
> 
> I'm running LVM 0.9.1_beta2 from kernel 2.4.1 with devfs and I had some little
> troubles, all related to /dev entries and devfs registration :
> 
> - another trouble I had, and I saw some people here had the same, is the
>   'devfs_register(): device already registered: "group"' message while doing
>   vgchange.
>   I did not find an=y answer about the cause of it. So I looked at the code
>   of vgchange and discovered that the /dev/vg0 and /dev/vg0/group are created
>   by mkdir and mknod (in the function vg_create_dir_and_group() ).
>   So when the kernel code tries to register the group device, the devfs code
>   finds it, since it was already registered by doing the mknod.
>   I understand the group device must exist since the VG_CREATE ioctl uses its
>   minor to select the VG to create. But since the minor is based on
>   vg->vg_number, and the vg structure is passed as argument to the VG_CREATE
>   ioctl, why not using vg->vg_number to select the VG ?
>   So we could open /dev/lvm to do the VG_CREATE ioctl instead of using
>   /dev/vg0/group ?  
> 

Thanks for those, I've reworked them a little but the effect should be the same.

patrick

  parent reply	other threads:[~2001-02-13 16:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-12 19:52 [linux-lvm] LVM with devfs questions and patches Benoit Gaussen
2001-02-13  7:05 ` Dirk Heinrichs
2001-02-13 16:09 ` Patrick Caulfield [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-02-14 18:18 Benoit Gaussen
2001-02-14 19:19 ` Andreas Dilger

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=20010213160922.G556@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox