[linux-lvm] LVM 0.9.1beta1 vgscan segfault when run with -d

[linux-lvm] LVM 0.9.1beta1 vgscan segfault when run with -d

[Charles Duffy]

[-- Attachment #1: Type: text/plain, Size: 761 bytes --]

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.

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Re: [linux-lvm] LVM 0.9.1beta1 vgscan segfault when run with -d

[Heinz J. Mauelshagen]

Charles, is this under devfs?
Side remark: you probably run "vgscan -d", right?

Didn't get the attachement, sorry. Send it again please.

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

Re: [linux-lvm] LVM 0.9.1beta1 vgscan segfault when run with -d

[Heinz J. Mauelshagen]

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

Re: [linux-lvm] LVM 0.9.1beta1 vgscan segfault when run with -d

[Charles Duffy]

[-- Attachment #1.1: Type: text/plain, Size: 1414 bytes --]

No, I am not using devfs.

Yes, I ran 'vgscan -d'. Indeed, I meant to attach the associated log
(unless it was stripped by the list software). I'll try again.

Also, I misreported the version number. It was 0.9.1beta1 under which
this occured.

On Sat, Jan 13, 2001 at 12:11:43PM +0000, Heinz J. Mauelshagen wrote:
> 
> Charles, is this under devfs?
> Side remark: you probably run "vgscan -d", right?
> 
> Didn't get the attachement, sorry. Send it again please.
> 
> 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.

[-- Attachment #1.2: lvmlog.bz2 --]
[-- Type: application/x-bzip2, Size: 2095 bytes --]

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]