On Mon, 2003-07-07 at 13:30, Heinz J . Mauelshagen wrote: > On Mon, Jul 07, 2003 at 11:37:04AM -0400, Greg Freemyer wrote: > > On Fri, 2003-07-04 at 07:49, Heinz J . Mauelshagen wrote: > > > On Thu, Jul 03, 2003 at 01:05:43PM -0400, Greg Freemyer wrote: > > > > > > > > Somehow I inactived a PV > > > > > > Hmm, there's no direct (in)activation of PVs. > > > A bit strange, that both are in diffrent states (they should be either inactive > > > in case the VG is or both active in case the VG got activated). > > > > This is a lab/test machine. I have a couple of others that have a > > similar LVM layout, and all of them have hot-swap drives. I likely > > moved a drive around at the wrong time. > > Ah, the let me assume, that this is the reason why the inactive status > is stored on the PV. > > > > > > > > > > > > > > # pvscan > > > > pvscan -- reading all physical volumes (this may take a while...) > > > > pvscan -- inactive PV "/dev/sda3" of VG "TruStore-Data" [53.63 GB / 48.63 GB free] > > > > pvscan -- ACTIVE PV "/dev/sdb1" of VG "TruStore-Data" [74.54 GB / 13.54 GB free] > > > > pvscan -- total: 2 [128.19 GB] / in use: 2 [128.19 GB] / in no VG: 0 [0] > > > > > > > > What command do I use to make it active? > > > > > > If the VG "TruStore-Data" is inactive, "vgchange -ay TruStore-Data" should turn > > > /dev/sda3 active as well. > > > > It is already active, and I just tried a reboot. sda3 is still > > inactive. > > You might want to create a dummy LV and remove it. > That changes PV state stored on disks. > That did not work. Apparently the VG did not think sda3 was part of it. I ended up doing a 'pvcreate -ff /dev/sda3'. Then a vgextend to re-add it to the VG. I had to recreate and populate the LV I had on there previously, but it was not a huge deal. Thanks for the help. Greg -- Greg Freemyer _______________________________________________ linux-lvm mailing list linux-lvm@sistina.com http://lists.sistina.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
