lkml.org 
[lkml]   [2010]   [Aug]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [dm-devel] linux-2.6.35+ causes LVM to fail with " device-mapper: version ioctl failed: Inappropriate ioctl for device"
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


\
 
 \ /
  Last update: 2010-08-16 15:59    [W:0.054 / U:0.388 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site