From: "Joe Harvell" <harvell@nortelnetworks.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] lvm_chr_ioctl
Date: Fri, 25 May 2001 18:00:10 -0500 [thread overview]
Message-ID: <3B0EE3FA.6CD4E1ED@americasm01.nt.com> (raw)
In-Reply-To: 004901c0e56b$1e8d1e00$5300000a@cavecreek.net
Justin:
I saw this exact same message (either when doing a vgscan or vgchange -a
y). Well, I'm not 100% sure about the number reported in the error message,
but it looks the same.
In my case it was because i was running the beta2 version of the kernel code
and the beta7 version of the user-space software. I had recompiled my
kernel and forgotten to re-apply the kernel patch. I fixed the problem by
patching the kernel code up to the beta 7 version.
Justin Booth wrote:
> I seem to be getting some errors for
> lvm_chr_ioctl: unknown command 4004fe0a
>
> When I do a vgcreate. I also noticed that if a partition is under heavy
> strain and I take a snapshot, the snapshot seg. faults, and all subseqent
> lvscans will also until I lvremove the volume and re-create it.
>
> Should I be worried about the lvm_chr_ioctl???
>
> Thanks in advance, Justin Booth
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
next prev parent reply other threads:[~2001-05-25 23:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-24 11:24 [linux-lvm] Raid5 sync problem Kaj-Michael Lang
2001-05-24 16:46 ` Austin Gonyou
2001-05-25 10:55 ` Kaj-Michael Lang
2001-05-25 19:46 ` Andreas Dilger
2001-05-25 22:36 ` [linux-lvm] lvm_chr_ioctl Justin Booth
2001-05-25 23:00 ` Joe Harvell [this message]
2001-05-24 17:04 ` [linux-lvm] Raid5 sync problem Andreas Dilger
2001-05-24 18:28 ` Austin Gonyou
2001-05-24 20:00 ` Jos� Luis Domingo L�pez
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=3B0EE3FA.6CD4E1ED@americasm01.nt.com \
--to=harvell@nortelnetworks.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