From: Heinz J. Mauelshagen <Heinz.Mauelshagen@t-online.de>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM 0.9.1beta1 vgscan segfault when run with -d
Date: Sat, 13 Jan 2001 12:12:33 +0000 [thread overview]
Message-ID: <20010113121233.J21587@srv.t-online.de> (raw)
In-Reply-To: <20010112223600.A846@mvista.com>; from cduffy@mvista.com on Fri, Jan 12, 2001 at 10:36:00PM -0800
Did you try 0.9.1 beta1 and face the same behaviour?
On Fri, Jan 12, 2001 at 10:36:00PM -0800, Charles Duffy wrote:
> Howdy. I'm experiencing some difficulties while transitioning from LVM
> 0.8i to 0.9.
>
> vgscan reports:
>
> vgscan -- ERROR "vg_read_with_pv_and_lv(): allocated LE of LV": can't
> get data of volume group "vg01" from physical volume(s)
>
> When I try to recieve more info (by running vgscan with "-D"), I
> recieve a segfault.
>
> This appears to be happening inside pv_read_uuidlist, at the memset on
> line 91 (I added some extra debug() calls to determine this). The
> attached log (from the original, unpatched version) should help by
> giving some context.
>
> Frankly, I don't know why this is happening -- more than sufficient
> space appears to be allocated beforehand -- but, as long as one rules
> out a bug in debug(), I don't see any other way 'round it.
>
> Thanks for your help.
--
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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2001-01-13 12:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-13 6:36 [linux-lvm] LVM 0.9.1beta1 vgscan segfault when run with -d Charles Duffy
2001-01-13 12:11 ` Heinz J. Mauelshagen
2001-01-13 21:19 ` Charles Duffy
2001-01-13 12:12 ` 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=20010113121233.J21587@srv.t-online.de \
--to=heinz.mauelshagen@t-online.de \
--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.