From: Patrick Caulfield <caulfield@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] lvm -- lvm_chr_ioctl: unknown command 0x8004fe97
Date: Tue Oct 22 06:45:01 2002 [thread overview]
Message-ID: <20021022114410.GC1154@tykepenguin.com> (raw)
In-Reply-To: <3DB537AB.642A6854@silicide.dk>
On Tue, Oct 22, 2002 at 01:34:04PM +0200, Jon Bendtsen wrote:
> Patrick Caulfield wrote:
>
> [cut]
>
> > You really don't want to do that... 1.1 is well broken.
>
> uhoh, i'm already doing it, not production yet, but soon.
> I figured that the latest from oktober 3, 1.1-rc2 would be
> good enough.
>
>
> > > and removing those debian packages.
> >
> > The Debian packages should be fine. Plenty of other people are using them.
> >
> > Can you tell which command is issued the illegal ioctl ? It could be that the
> > LVM device has a wrong major/minor or something else has take the LVM
> > major/minor device number, because those are /not/ LVM ioctl numbers.
>
> More than one. vgchange -a y <VG>
> lvremove (snapshopts)
It does sound a lot like an "odd" lvm toolset (or perhaps library) that's
interfering. It's worth checking whicg vgchange (etc) command is being run (ie
is there one in /usr/local or /usr/sbin that's earlier in the PATH than the
"real" one. Also do "ldd" in the library to see which library is being picked
up.
patrick
next prev parent reply other threads:[~2002-10-22 6:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 3:41 [linux-lvm] lvm -- lvm_chr_ioctl: unknown command 0x8004fe97 Jon Bendtsen
2002-10-21 10:13 ` Patrick Caulfield
2002-10-22 6:34 ` Jon Bendtsen
2002-10-22 6:45 ` Patrick Caulfield [this message]
2002-10-22 7:58 ` Jon Bendtsen
2002-10-22 8:04 ` Patrick Caulfield
2002-10-22 8:12 ` Jon Bendtsen
2002-10-22 8:20 ` Patrick Caulfield
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=20021022114410.GC1154@tykepenguin.com \
--to=caulfield@sistina.com \
--cc=linux-lvm@sistina.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