Re: 2.6.9-mm1: LVM stopped working

From: jfannin1
Date: Tue Oct 26 2004 - 07:42:21 EST


On Mon, Oct 25, 2004 at 09:03:22PM +0200, Christophe Saout wrote:
> Am Sonntag, den 24.10.2004, 01:06 +0200 schrieb Mathieu Segaud:
>
>>Well, I gave a try to last -mm tree. The bot seemed good till it got to
>>LVM stuff. Vgchange does not find any volume groups. I can't say much because
>>lvm is pretty "early stuff" on this box; so it is pretty unusable.

LVM doesn't work with 2.6.9-mm1 here either, complaining that it
can't find all the pv's. I'm not using any sort of encryption. Here,
pvdisplay reports:

--- Physical volume ---
PV Name /dev/hda2
VG Name home
PV Size 24.52 GB / not usable 0
Allocatable yes (but full)
PE Size (KByte) 4096
Total PE 6277
Free PE 0
Allocated PE 6277
PV UUID M8tcls-7Tp7-sAYe-ypH3-if50-00JH-hvvXSL

--- Physical volume ---
PV Name unknown device
VG Name home
PV Size 70.47 GB / not usable 0
Allocatable yes (but full)
PE Size (KByte) 4096
Total PE 18040
Free PE 0
Allocated PE 18040
PV UUID SmreB9-Q3dp-DBBc-q0N9-v762-o6UB-1VUgYw

--- Physical volume ---
PV Name unknown device
VG Name home
PV Size 25.12 GB / not usable 0
Allocatable yes (but full)
PE Size (KByte) 4096
Total PE 6431
Free PE 0
Allocated PE 6431
PV UUID sbbFSh-0MP8-jtir-Jcyx-VtcE-TxNh-tfNwNe

I can open the device nodes for the 'missing' pv's in a hexeditor and see the
uuid magic; if I reboot into 2.6.9-rc4-mm1 they are found without a
problem, and everything works.

Whether or not I'll have time to try to narrow down the change
that causes this depends on things that are out of my control ATM. :-/

--
Joseph Fannin
jfannin1@xxxxxxxxxxxxxxx
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/