From: Alasdair G Kergon <agk@redhat.com>
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: device-mapper development <dm-devel@redhat.com>,
lvm-devel@redhat.com, lkml <linux-kernel@vger.kernel.org>,
Zdenek Kabelac <zkabelac@redhat.com>
Subject: Re: [dm-devel] linux-2.6.35+ causes LVM to fail with " device-mapper: version ioctl failed: Inappropriate ioctl for device"
Date: Mon, 16 Aug 2010 16:55:16 +0100 [thread overview]
Message-ID: <20100816155516.GD11907@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <AANLkTik0naaXsicwLgLeBUA0u2+BQQbww-44Fs_cHXHH@mail.gmail.com>
On Mon, Aug 16, 2010 at 11:32:15PM +0800, Jeff Chua wrote:
> It'll be nice if lvm returns a more meanful message like "ioctl
> failed. Check /proc/misc to ensure the device is mapped correctly."
No need - LVM should be quite capable of detecting/dealing with the problem.
> To take care of it automatically with udev, I'm doing this in rc.S
> if [ -f /sys/devices/virtual/misc/device-mapper/dev ]
> then
> NODE=$(</sys/devices/virtual/misc/device-mapper/dev)
> rm -f /dev/mapper/control
> mknod /dev/mapper/control c ${NODE/:/ }
The whole point of this change was to trigger the loading of dm-mod
automatically for people using it as a module, based on using a known
major/minor number instead of a dynamic one only known after the module
has been loaded. That needs to happen regardless of whether someone is
using udev or not.
This can all be fixed easily enough in userspace.
Alasdair
--
lvm-devel mailing list
lvm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/lvm-devel
next prev parent reply other threads:[~2010-08-16 15:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 18:01 linux-2.6.35+ causes LVM to fail with " device-mapper: version ioctl failed: Inappropriate ioctl for device" Jeff Chua
2010-08-14 15:54 ` [dm-devel] " Alasdair G Kergon
2010-08-14 16:16 ` Alasdair G Kergon
2010-08-15 5:23 ` Jeff Chua
2010-08-15 13:03 ` Alasdair G Kergon
2010-08-15 14:13 ` Jeff Chua
2010-08-16 13:56 ` [dm-devel] " Zdenek Kabelac
2010-08-16 14:22 ` Alasdair G Kergon
2010-08-16 15:32 ` [lvm-devel] " Jeff Chua
2010-08-16 15:55 ` Alasdair G Kergon [this message]
2010-08-16 16:10 ` [lvm-devel] " Jeff Chua
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=20100816155516.GD11907@agk-dp.fab.redhat.com \
--to=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=jeff.chua.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lvm-devel@redhat.com \
--cc=zkabelac@redhat.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).