From: Alasdair G Kergon <agk@redhat.com>
To: Zdenek Kabelac <zkabelac@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>,
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:22:46 +0100 [thread overview]
Message-ID: <20100816142246.GA11907@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <4C6943A0.9030708@redhat.com>
On Mon, Aug 16, 2010 at 03:56:48PM +0200, Zdenek Kabelac wrote:
> Dne 15.8.2010 16:13, Jeff Chua napsal(a):
> > With 2.6.35++, /dev/mapper/control has moved from 60 to 236!
The latest LVM package made an assumption that it would be set up
correctly by udev (or manually in your case). We are updating
the userspace libdevmapper code to handle your circumstances
automatically.
> > # 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
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=d7824370e26325c881b665350ce64fb0a4fde24a
For those interested, originally we used mlockall() but in non-C locales
on some distributions glibc is configured to map 80MB+ of locale data
into memory without offering any way to unmap it. We don't need
that data locked and it increased the minimum memory required to install
a distribution as well as slowing down the LVM tools! So we had to
write a customised version that tries to skip locking unnecessary pages
like those.
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 14:22 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 [this message]
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=20100816142246.GA11907@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).