From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Unknown command in kernel-log
Date: Fri Jun 28 07:04:02 2002 [thread overview]
Message-ID: <20020628114424.B24660@sistina.com> (raw)
In-Reply-To: <637850703.20020627182114@tnonline.net>; from andewid@tnonline.net on Thu, Jun 27, 2002 at 06:21:14PM +0200
Anders,
those messages show, that LVM1.1 tools access a pre 1.1 driver.
If you downgrade the tools as well, those should be gone.
On Thu, Jun 27, 2002 at 06:21:14PM +0200, Anders Widman wrote:
>
> I am running kernel-2.4.19-rc1. I get an error in the dmesg log
> that looks like this:
>
> 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
>
> What do you think this can be? Is it dangerous?
>
> Thanks,
> Anders Widman
>
>
> _______________________________________________
> 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
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2002-06-28 7:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-27 11:21 [linux-lvm] Unknown command in kernel-log Anders Widman
2002-06-28 7:04 ` Heinz J . Mauelshagen [this message]
2002-06-28 8:39 ` Anders Widman
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=20020628114424.B24660@sistina.com \
--to=mauelshagen@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 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.