From: "Verloove, Olivier" <olivier_verloove@merck.com>
To: linux-lvm@msede.com
Subject: RE: [linux-lvm] Bonehead problem
Date: Thu, 11 Mar 1999 10:27:02 -0500 [thread overview]
Message-ID: <199903111527.QAA08350@e35.msede.com> (raw)
Yes... indeed, creating the device file solved the problem.
Now, I ran vgscan and it hanged the system :-(
Here's what I found in the syslog:
Mar 11 16:07:17 cobalt modprobe: can't locate module char-major-109
Mar 11 16:07:20 cobalt kernel: LVM version 0.6 by Heinz Mauelshagen
(26/02/199
9)
Mar 11 16:07:20 cobalt kernel: lvm -- Module successfully initialized
Mar 11 16:07:24 cobalt kernel: cdrom: open failed.
Mar 11 16:07:24 cobalt modprobe: can't locate module block-major-22
Mar 11 16:07:24 cobalt last message repeated 5 times
Mar 11 16:07:24 cobalt modprobe: can't locate module block-major-33
Mar 11 16:07:24 cobalt last message repeated 5 times
Mar 11 16:07:24 cobalt modprobe: can't locate module block-major-34
Mar 11 16:07:24 cobalt last message repeated 5 times
Mar 11 16:07:24 cobalt kernel: VFS: grow_buffers: size = 16
Mar 11 16:07:25 cobalt last message repeated 2613 times
Mar 11 16:07:25 cobalt kernel: Kernel panic: Free list corrupted Mar 11
16:07:17 cobalt modprobe: can't locate module char-major-109
Mar 11 16:07:20 cobalt kernel: LVM version 0.6 by Heinz Mauelshagen
(26/02/199
9)
Mar 11 16:07:20 cobalt kernel: lvm -- Module successfully initialized
Mar 11 16:07:24 cobalt kernel: cdrom: open failed.
Mar 11 16:07:24 cobalt modprobe: can't locate module block-major-22
Mar 11 16:07:24 cobalt last message repeated 5 times
Mar 11 16:07:24 cobalt modprobe: can't locate module block-major-33
Mar 11 16:07:24 cobalt last message repeated 5 times
Mar 11 16:07:24 cobalt modprobe: can't locate module block-major-34
Mar 11 16:07:24 cobalt last message repeated 5 times
Mar 11 16:07:24 cobalt kernel: VFS: grow_buffers: size = 16
Mar 11 16:07:25 cobalt last message repeated 2613 times
Mar 11 16:07:25 cobalt kernel: Kernel panic: Free list corrupted
I had a look in major.h and 22, 33, 34 corresponds to IDE1_MAJOR, IDE2_MAJOR
and IDE3_MAJOR ?
Any idea.
To summarize, this is a new install (no VG created) of Linux 2.2.2 (without
devfs) + LVM 0.6.
I have MD compiled in the kernel ... but no MD device created.
Thanks.
Olivier
> ----------
> From: Klaus Strebel[SMTP:stb@ep-ag.com]
> Reply To: antivirus@ep-ag.com
> Sent: Thursday, 11 Mar, 1999 15:56
> To: Verloove, Olivier
> Cc: linux-lvm@msede.com
> Subject: Re: [linux-lvm] Bonehead problem
>
> Hi Olivier,
>
> "Verloove, Olivier" wrote:
> >
> > I have the same problem (Linux 2.2.2 + LVM 0.6).
> > With or without lvm module loaded, I get:
> > vgscan -- invalid i/o protocol version
> >
> > Is there another module which should be loaded at the same time ?
> > lsmod gives me:
> > lvm 26960 0 (unused)
> Do you have the char-device /dev/lvm (Major 109, Minor 0) ? The LVM-0.5
> module
> seems to create this device, if it doesn't exist. The LVM-0.6 seems not to
> do
> this, i use devfs and i have to create the device each time before i load
> the
> module.
>
> Cheers
> Klaus
> --
> Klaus Strebel
> stb@ep-ag.com
> EIGNER + PARTNER AG - The Engineering Warehouse Company -
> <http://www.ep-ag.com>
> -----------------------------------------------------------------------
> In Heaven there will be no DOS, no Intel, and above all, no Bill Gates.
>
next reply other threads:[~1999-03-11 15:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-11 15:27 Verloove, Olivier [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-03-11 15:38 [linux-lvm] Bonehead problem Verloove, Olivier
1999-03-11 15:09 Steve_J_Brueggeman
1999-03-11 15:08 Steve_J_Brueggeman
1999-03-11 13:40 Verloove, Olivier
1999-03-11 14:56 ` Klaus Strebel
1999-03-10 23:44 Shawn Leas
1999-03-11 0:25 ` ishamael
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=199903111527.QAA08350@e35.msede.com \
--to=olivier_verloove@merck.com \
--cc=linux-lvm@msede.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.