* [linux-lvm] lvm -- lvm_chr_ioctl: unknown command 0x8004fe97
@ 2002-10-21 3:41 Jon Bendtsen
2002-10-21 10:13 ` Patrick Caulfield
0 siblings, 1 reply; 8+ messages in thread
From: Jon Bendtsen @ 2002-10-21 3:41 UTC (permalink / raw)
To: linux-lvm
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
and removing those debian packages.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [linux-lvm] lvm -- lvm_chr_ioctl: unknown command 0x8004fe97
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
0 siblings, 1 reply; 8+ messages in thread
From: Patrick Caulfield @ 2002-10-21 10:13 UTC (permalink / raw)
To: linux-lvm
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
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [linux-lvm] lvm -- lvm_chr_ioctl: unknown command 0x8004fe97
2002-10-21 10:13 ` Patrick Caulfield
@ 2002-10-22 6:34 ` Jon Bendtsen
2002-10-22 6:45 ` Patrick Caulfield
0 siblings, 1 reply; 8+ messages in thread
From: Jon Bendtsen @ 2002-10-22 6:34 UTC (permalink / raw)
To: linux-lvm
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)
> If you can determine what command is issuing those odd ioctls then you're
> probably half-way to finding the culprit.
Well, it's not just one command.
JonB
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [linux-lvm] lvm -- lvm_chr_ioctl: unknown command 0x8004fe97
2002-10-22 6:34 ` Jon Bendtsen
@ 2002-10-22 6:45 ` Patrick Caulfield
2002-10-22 7:58 ` Jon Bendtsen
0 siblings, 1 reply; 8+ messages in thread
From: Patrick Caulfield @ 2002-10-22 6:45 UTC (permalink / raw)
To: linux-lvm
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
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [linux-lvm] lvm -- lvm_chr_ioctl: unknown command 0x8004fe97
2002-10-22 6:45 ` Patrick Caulfield
@ 2002-10-22 7:58 ` Jon Bendtsen
2002-10-22 8:04 ` Patrick Caulfield
0 siblings, 1 reply; 8+ messages in thread
From: Jon Bendtsen @ 2002-10-22 7:58 UTC (permalink / raw)
To: linux-lvm
Patrick Caulfield wrote:
>
> On Tue, Oct 22, 2002 at 01:34:04PM +0200, Jon Bendtsen wrote:
> > Patrick Caulfield wrote:
[cut]
> > 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.
i think it was the debian packages, because it stopped after removing
the
debian packages and make;make install
the lvm-1.1-rc2
JonB
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [linux-lvm] lvm -- lvm_chr_ioctl: unknown command 0x8004fe97
2002-10-22 7:58 ` Jon Bendtsen
@ 2002-10-22 8:04 ` Patrick Caulfield
2002-10-22 8:12 ` Jon Bendtsen
0 siblings, 1 reply; 8+ messages in thread
From: Patrick Caulfield @ 2002-10-22 8:04 UTC (permalink / raw)
To: linux-lvm
On Tue, Oct 22, 2002 at 02:57:29PM +0200, Jon Bendtsen wrote:
> Patrick Caulfield wrote:
> >
> > On Tue, Oct 22, 2002 at 01:34:04PM +0200, Jon Bendtsen wrote:
> > > Patrick Caulfield wrote:
>
>
> [cut]
>
>
> > > 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.
>
> i think it was the debian packages, because it stopped after removing
> the
> debian packages and make;make install
> the lvm-1.1-rc2
Seems unlikely - I'm the maintainer of the Debian packages and I can state
categorically that they don't issue that ioctl :-)
patrick
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [linux-lvm] lvm -- lvm_chr_ioctl: unknown command 0x8004fe97
2002-10-22 8:04 ` Patrick Caulfield
@ 2002-10-22 8:12 ` Jon Bendtsen
2002-10-22 8:20 ` Patrick Caulfield
0 siblings, 1 reply; 8+ messages in thread
From: Jon Bendtsen @ 2002-10-22 8:12 UTC (permalink / raw)
To: linux-lvm
Patrick Caulfield wrote:
>
> On Tue, Oct 22, 2002 at 02:57:29PM +0200, Jon Bendtsen wrote:
[cut]
> > i think it was the debian packages, because it stopped after removing
> > the
> > debian packages and make;make install
> > the lvm-1.1-rc2
>
> Seems unlikely - I'm the maintainer of the Debian packages and I can state
> categorically that they don't issue that ioctl :-)
well, it works now. I did try with another lvm 1.1-rc? maybe thats why?
JonB
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [linux-lvm] lvm -- lvm_chr_ioctl: unknown command 0x8004fe97
2002-10-22 8:12 ` Jon Bendtsen
@ 2002-10-22 8:20 ` Patrick Caulfield
0 siblings, 0 replies; 8+ messages in thread
From: Patrick Caulfield @ 2002-10-22 8:20 UTC (permalink / raw)
To: linux-lvm
On Tue, Oct 22, 2002 at 03:12:09PM +0200, Jon Bendtsen wrote:
> Patrick Caulfield wrote:
> >
> > On Tue, Oct 22, 2002 at 02:57:29PM +0200, Jon Bendtsen wrote:
>
>
> [cut]
>
>
> > > i think it was the debian packages, because it stopped after removing
> > > the
> > > debian packages and make;make install
> > > the lvm-1.1-rc2
> >
> > Seems unlikely - I'm the maintainer of the Debian packages and I can state
> > categorically that they don't issue that ioctl :-)
>
> well, it works now. I did try with another lvm 1.1-rc? maybe thats why?
Could easily be. My guess is that the Debian symlinks got overwritten with
something else so the actual Debian ones (which live in /lib/lvm-10) were not
being called at all.
--
patrick
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2002-10-22 8:20 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.