From: Patrick Caulfield <caulfield@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] lvm -- lvm_chr_ioctl: unknown command 0x8004fe97
Date: Mon Oct 21 10:13:02 2002 [thread overview]
Message-ID: <20021021151240.GG838@tykepenguin.com> (raw)
In-Reply-To: <3DB3BDA4.75B552B6@silicide.dk>
On Mon, Oct 21, 2002 at 10:41:08AM +0200, Jon Bendtsen wrote:
> Since i want to run with ext3 and use snapshots, i applied the
> linux-2.4.18-VFS-lock.patch
> to my default 2.4.18 kernel. I just did that file since making
> the patches, and applying that would fail during compilation.
> (something about md driver ?, which i dont use)
>
> So, after just getting the VFS-lock patch to work, i've tried
> to use it on my debian woody, with
> lvm-common 1.5.5
> lvm10 1.0.4-4
> installed. But i get alot of errors :/
> lvm -- lvm_chr_ioctl: unknown command 0x8004fe97
> lvm -- lvm_chr_ioctl: unknown command 0x8004fe97
> lvm -- lvm_chr_ioctl: unknown command 0x8004fe97
> lvm -- lvm_chr_ioctl: unknown command 0x8004fe97
>
> And sometimes vgscan cant find my VG, and i cant activate it with
> vgchange -a y ...
>
>
> It _MIGHT_ be because i'm running lvm ontop of a loop-AES, but it does
> work most of the time.
>
>
>
> JonB
> ps: right now i'm starting all over with
> 2.4.19
> lvm_1.1-rc2.tar.gz
You really don't want to do that... 1.1 is well broken.
> 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.
If you can determine what command is issuing those odd ioctls then you're
probably half-way to finding the culprit.
patrick
next prev parent reply other threads:[~2002-10-21 10:13 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 [this message]
2002-10-22 6:34 ` Jon Bendtsen
2002-10-22 6:45 ` Patrick Caulfield
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=20021021151240.GG838@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