Maybe "unknown" is the wrong word in this case. You will be able to see this VG using vgs, vgdisplay and so on. But you can't remove when you try a vgremove. You have to import it back (vgimport VolumeGroup) to change it again. I think that unknown means more like "unchangeable". []'s -- Anderson Kaiser (RHCE, RHCVA) Red Hat Brasil - Global Support Services akaiser@redhat.com +55 11 3529-6000 Direct: +55 11 3529-6093 _______________________________________________ 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/ ----- Thanks for the response, Anderson. the use case I'm imagining is the export of a set of disks from one machine (VG intact) and the subsequent import into another machine. The command works perfectly in such a scenario. I can vgexport, yank the disks from one machine, insert into another, scan the scsi bus, vgscan, vgimport, vgchange, mount the lv, and use all my data. However, after doing all this and going back to the original system that created the VG, not only do I see the VG in vgdisplay or vgs, but I get errors from the missing disk. And in typing all this up, it occurrs to me to try a vgscan on the original system. <pause> voila! I still got disk complaints, but I unlinked /dev/sdb1 and /dev/sdb and now we're clean; no complaints anywhere about previously used disks or VGs. Thanks, -- Jess Males _______________________________________________ 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/
