sorry, stupid mistake, simply didn't activate it with vgchange -a y big_cheese On 30, Jun, 2005, Dan B. Phung declared: > I'm trying to recover my file system, and I was able to recreate the PV > and run vgcfgrestore succesfully, but the LV status is 'NOT available'. > Why would this be? > > blade01:root # lvs > LV VG Attr LSize Origin Snap% Move Log Copy% > home_lv big_cheese -wi--- 195.31G > proj_lv big_cheese -wi--- 195.31G > zap_lv big_cheese -wi--- 78.12G > > blade01:root # lvdisplay > --- Logical volume --- > LV Name /dev/big_cheese/proj_lv > VG Name big_cheese > LV UUID lIuJg1-ktEe-02A1-6VtC-uW5n-qIA4-wX4edP > LV Write Access read/write > LV Status NOT available > LV Size 195.31 GB > Current LE 50000 > Segments 1 > Allocation inherit > Read ahead sectors 0 > > --- Logical volume --- > LV Name /dev/big_cheese/home_lv > VG Name big_cheese > LV UUID NJH2DO-wn2A-Xxs7-P3DV-skEf-v4ly-s1LVbw > LV Write Access read/write > LV Status NOT available > LV Size 195.31 GB > Current LE 50000 > Segments 1 > Allocation inherit > Read ahead sectors 0 > > --- Logical volume --- > LV Name /dev/big_cheese/zap_lv > VG Name big_cheese > LV UUID wqAlDs-HwGs-vAY0-CL5n-G9zW-5i4x-ux8wXk > LV Write Access read/write > LV Status NOT available > LV Size 78.12 GB > Current LE 20000 > Segments 2 > Allocation inherit > Read ahead sectors 0 > > > > regards, > dan > > _______________________________________________ > linux-lvm mailing list > linux-lvm@redhat.com > https://www.redhat.com/mailman/listinfo/linux-lvm > read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ > _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
