Linux LVM users
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] 2.4.20-pre4 and lvm-1.0.5
Date: Wed Aug 28 08:38:53 2002	[thread overview]
Message-ID: <20020828151805.A27323@sistina.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0208271022040.20666-100000@junior.lunanet.biz>; from dlt@lunanet.biz on Tue, Aug 27, 2002 at 10:26:45AM -0600

On Tue, Aug 27, 2002 at 10:26:45AM -0600, Donald Thompson wrote:
> 
> On Tue, 27 Aug 2002, Heinz J . Mauelshagen wrote:
> 
> > On Mon, Aug 26, 2002 at 12:21:52PM -0600, Donald Thompson wrote:
> > >
> > > That is correct. I boot, vgscan fails (I'm assuming it segfaults but I
> > > really can't tell during the normal boot process what actually happened)
> > > to detect my VGs, my system goes into a maintenance mode situation since
> > > my /usr is on an LV, I login and run lsmod and absolutely no modules
> > > appear in the list. I try vgscan and/or pvscan and they fail with a
> > > segmentation fault. So yeah, if no module tree exists system boots fine,
> > > if module tree exists vgscan fails regardless of whether modules are
> > > loaded. Yes it defies logic, but I swear thats how it worked:)
> >
> > I wonder if there might be a single user case disabling lsmod to list?
> 
> Well I doubt that. Originally rtc.o was being loaded and was listed by
> lsmod, so I figured maybe that was the problem. rtc.o gets loaded I think
> automatically when my system is setting the software clock from the
> hardware. But removing rtc.o from the module tree, running depmod -a, and
> rebooting, I got the same result where vgscan segfaults.

Donald,

I figured out that it is the gendisk thing (again).
2.4.20-pre4 even segfaults on "cat /proc/partitions" !!!

Investigating...

> 
> -Don
> 
> 
> _______________________________________________
> 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

      reply	other threads:[~2002-08-28  8:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-24 15:14 [linux-lvm] Everybody is good at something! Handymanweb.com
2002-08-25  3:49 ` [linux-lvm] 2.4.20-pre4 and lvm-1.0.5 Donald Thompson
2002-08-26  5:30   ` Heinz J . Mauelshagen
2002-08-26 13:22     ` Donald Thompson
2002-08-27  2:34       ` Heinz J . Mauelshagen
2002-08-27 11:27         ` Donald Thompson
2002-08-28  8:38           ` Heinz J . Mauelshagen [this message]

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=20020828151805.A27323@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox