[linux-lvm] PV issues with LVM on 2.4.21

[Nathan Hunsperger]

For the archive -

I was able to solve this problem by naming my volume group something
other than 'storage'.  Although vgcreate would allow me to create the
volume group named 'storage', I now suspect that one of my disks
contained an incomplete signature for that volume group, and was
confusing LVM.  After zeroing out the beginning of the drives, I was
able to create a volume group named 'storage' that lasts between
reboots.

- Nathan

On Tue, Jul 08, 2003 at 04:05:24PM -0700, Nathan Hunsperger wrote:
> Hello -
> 
> I'm experiencing an error when trying to scan my volume groups after a
> reboot.  When running vgscan, I get:
> vgscan -- reading all physical volumes (this may take a while...)
> vgscan -- ERROR "pv_read_all_pv_of_vg(): no PV" can't get data of volume group "storage" from physical volume(s)
> vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
> vgscan -- WARNING: This program does not do a VGDA backup of your volume group
> 
> I am running lvm 1.0.7 on top of software raid 5 on 2.4.21.  I grabbed a
> fresh copy of 2.4.21 from kernel.org, configured lvm, made the patchset,
> patched the kernel, configed the kernel, and then made the kernel...so I
> think I'm following all the directions.
> 
> As the raid array is running without problems (all drives online, and
> array is clean), I suspect a problem with lvm.
> 
> Also, just for clarification, on a reboot (after I load the disk
> controller module, but before I run any lvm commands) if I dd /dev/zero
> over /dev/md/0, I am able to pvcreate, vgcreate, lvcreate, mkfs, and
> mount just fine.  After a reboot, however, I get the above error.
> 
> Any ideas?  I don't particularly like the idea of a 1/2TB of volatile
> storage.
> 
> - Nathan
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm at sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/