47976 – vgscan ignores configuration, crashes

Bug 47976 - vgscan ignores configuration, crashes

Summary: vgscan ignores configuration, crashes

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Core system (show other bugs)
Hardware:	x86 Linux

Importance:	High major (vote)
Assignee:	Max Kalika (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2004-04-15 15:35 UTC by Matteo Sasso
Modified:	2004-04-24 11:50 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
strace (xxx,216.83 KB, text/plain) 2004-04-15 15:37 UTC, Matteo Sasso	Details
lvm.conf (lvm.conf,64 bytes, text/plain) 2004-04-15 15:38 UTC, Matteo Sasso	Details
backtrace (bt,1.00 KB, text/plain) 2004-04-15 15:45 UTC, Matteo Sasso	Details
emerge info (info,2.13 KB, text/plain) 2004-04-15 15:47 UTC, Matteo Sasso	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Matteo Sasso 2004-04-15 15:35:27 UTC

I have problems using LVM2. I run vgscan and it simply crashes (SEGFAULT) after the "Reading all physical volumes.  This may take a while..." message.
Strace told me il crashes just after closing /dev/mdd0, so maybe the problem is related to that class of devices. I tried excluding those via lvm.conf but it seems vgscan simply ignores my filter directives.


Reproducible: Always
Steps to Reproduce:
1. vgscan

Actual Results:  
  Reading all physical volumes.  This may take a while... 
Segmentation fault

Comment 1 Matteo Sasso 2004-04-15 15:37:28 UTC

Created attachment 29373 [details]
strace

Comment 2 Matteo Sasso 2004-04-15 15:38:27 UTC

Created attachment 29374 [details]
lvm.conf

Comment 3 Matteo Sasso 2004-04-15 15:45:41 UTC

Created attachment 29376 [details]
backtrace

I recompiled with --enable-debug, and that's what gdb said.

Comment 4 Matteo Sasso 2004-04-15 15:47:21 UTC

Created attachment 29377 [details]
emerge info

By the way...

Comment 5 Matteo Sasso 2004-04-15 15:55:30 UTC

Ok, I found the culprit: lvm2.2.00.12 works!! Sorry, I posted too many attachments before trying the most obvious thing... :/ D'oh!

Please update the LVM2 version and close this bug.

Comment 6 Daniel Black (RETIRED) gentoo-dev

2004-04-15 19:42:14 UTC

see last comment - thanks for providing a solution.

Comment 7 Max Kalika (RETIRED) gentoo-dev

2004-04-24 11:50:53 UTC

2.00.15 is now in portage.  Thanks.