From: Alasdair G Kergon <agk@redhat.com>
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: device-mapper development <dm-devel@redhat.com>,
lkml <linux-kernel@vger.kernel.org>,
lvm-devel@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: Sat, 14 Aug 2010 16:54:01 +0100 [thread overview]
Message-ID: <20100814155401.GJ26032@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <AANLkTime9NS3Bk-8ZpovRNy9iEGJxwYw=-aZ38JoRa_3@mail.gmail.com>
On Sat, Aug 14, 2010 at 02:01:47AM +0800, Jeff Chua wrote:
> It seems one of these commits in
> 8357422d4bf33bc2c35884d4016c3fc9efbbc1d2 is causing LVM2
> (LVM2.2.02.72) to fail.
Did you (partially) bisect that or are you just guessing?
The only one there possibly relevant is 7e507eb6432afdd798d4c6dccf949b8c43ef151c.
> Previously good logical volumes cannot be mounted anymore, and new one
> cannot be created. All failed with the error ...
> "device-mapper: version ioctl failed: Inappropriate ioctl for device"
What distribution? What version of udev package?
'lvm version' output?
Provide long listing of /dev/mapper and any dm/lvm devices in /dev.
Add -vvvv to your lvm command for better clues.
> Is there a new LVM2 for this new dm ioctl or the dm is not right?
There's no new dm ioctl.
Alasdair
next prev parent reply other threads:[~2010-08-14 15:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 18:01 Jeff Chua
2010-08-14 15:54 ` Alasdair G Kergon [this message]
2010-08-14 16:16 ` [dm-devel] " 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 ` Zdenek Kabelac
2010-08-16 14:22 ` [lvm-devel] " Alasdair G Kergon
2010-08-16 15:32 ` Jeff Chua
2010-08-16 15:55 ` [dm-devel] [lvm-devel] " Alasdair G Kergon
2010-08-16 16:10 ` 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=20100814155401.GJ26032@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 \
/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
all inboxes | Powered by JetHome®