From: Zdenek Kabelac <zkabelac@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
Jeff Chua <jeff.chua.linux@gmail.com>,
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: Mon, 16 Aug 2010 15:56:48 +0200 [thread overview]
Message-ID: <4C6943A0.9030708@redhat.com> (raw)
In-Reply-To: <AANLkTinUuphqozgrSMNnrKxJrPWFp77y2TzdEwtuMD42@mail.gmail.com>
Dne 15.8.2010 16:13, Jeff Chua napsal(a):
> On Sun, Aug 15, 2010 at 9:03 PM, Alasdair G Kergon <agk@redhat.com> wrote:
>>> Just a vanilla linux. No udev.
>>
>> So likely a userspace problem where udev is now assumed to be present.
>>
>>>> Provide long listing of /dev/mapper and any dm/lvm devices in /dev.
>>
>> You can do that by running:
>> ls -l /dev/mapper /dev/vg01
>> Also:
>> cat /proc/devices
>
> 253 device-mapper
>
>> cat /proc/misc
>
> 236 device-mapper <== was at 60 before the new kernel
>
>
> Got it! Sorry, it's me being _dumb_!!!
>
> With 2.6.35++, /dev/mapper/control has moved from 60 to 236!
>
> So I fix it by recreating the control file with "mknod
> /var/mapper/control c 10 253".
>
> I got this "internal error" when I activate/deactivate the volume
> group, but it seems ok. I could mount the volumes and so far it's all
> good.
>
> # vgchange -a n vg01
> Internal error: Maps lock 14217216 < unlock 14221312
> Internal error: Maps lock 14221312 < unlock 14225408
> Internal error: Maps lock 14225408 < unlock 14229504
> Internal error: Maps lock 14229504 < unlock 14233600
> Internal error: Maps lock 14233600 < unlock 14237696
> Internal error: Maps lock 14237696 < unlock 14241792
> 0 logical volume(s) in volume group "vg01" now active
>
> # vgchange -a y vg01
> Internal error: Maps lock 14192640 < unlock 14196736
> Internal error: Maps lock 14196736 < unlock 14200832
> Internal error: Maps lock 14200832 < unlock 14204928
> Internal error: Maps lock 14204928 < unlock 14209024
> Internal error: Maps lock 14209024 < unlock 14213120
> Internal error: Maps lock 14213120 < unlock 14217216
> 6 logical volume(s) in volume group "vg01" now active
>
> Hopefully those errors above means no harm.
>
Well error is usually error - so some harm under certain circumstances could
happen (low memory situation)...
But in this case I assume it's related to this kernel commit which should fix
this problem ?
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=d7824370e26325c881b665350ce64fb0a4fde24a
Zdenek
--
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 13:56 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 ` Zdenek Kabelac [this message]
2010-08-16 14:22 ` [dm-devel] " Alasdair G Kergon
2010-08-16 15:32 ` [lvm-devel] " Jeff Chua
2010-08-16 15:55 ` Alasdair G Kergon
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=4C6943A0.9030708@redhat.com \
--to=zkabelac@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;
as well as URLs for NNTP newsgroup(s).