[linux-lvm] vgchange -an question with disconnected disks

[John DeFranco]

I have a question regarding the behavior of vgchange -a n on lvm2 when 
there are disk failures. Specifically the following:

1. vgchange -a y vg00
2. disconnect the disks
3. vgchange -a n vg00

Now this fails with many messages, such as:
[root at harris ~]# vgchange -a n vg00
   /dev/sda1: read failed after 0 of 4096 at 0: Input/output error
   /dev/sdb1: read failed after 0 of 4096 at 0: Input/output error
   /dev/sdb2: read failed after 0 of 4096 at 0: Input/output error
   /dev/sdc1: read failed after 0 of 4096 at 0: Input/output error
   /dev/sda: read failed after 0 of 1024 at 0: Input/output error
   /dev/sda: read failed after 0 of 1024 at 312475648: Input/output error
   /dev/sda: read failed after 0 of 2048 at 0: Input/output error
   /dev/sda1: read failed after 0 of 4096 at 1966080: Input/output error
   /dev/sda1: read failed after 0 of 4096 at 0: Input/output error
   /dev/sda2: read failed after 0 of 4096 at 310312960: Input/output error
   /dev/sda2: read failed after 0 of 4096 at 0: Input/output error
   /dev/sdb: read failed after 0 of 1024 at 0: Input/output error
   /dev/sdb: read failed after 0 of 1024 at 312475648: Input/output error
   /dev/sdb: read failed after 0 of 2048 at 0: Input/output error
   /dev/sdb1: read failed after 0 of 4096 at 1966080: Input/output error
   /dev/sdb1: read failed after 0 of 4096 at 0: Input/output error
   /dev/sdb2: read failed after 0 of 4096 at 310312960: Input/output error
   /dev/sdb2: read failed after 0 of 4096 at 0: Input/output error
   /dev/sdc: read failed after 0 of 1024 at 0: Input/output error
   /dev/sdc: read failed after 0 of 1024 at 16384000: Input/output error
   /dev/sdc: read failed after 0 of 2048 at 0: Input/output error
   /dev/sdc1: read failed after 0 of 4096 at 16318464: Input/output error
   /dev/sdc1: read failed after 0 of 4096 at 0: Input/output error
   Unable to find volume group "vg00"
[root at harris ~]#

This the vg is not deactivated. Now this is different behavior that with 
lvm1 which would just proceed as normal. My question is that is there a 
way to force the deactivation to occur in this case?

Thanks!

-- 
===========
John DeFranco                  Hewlett Packard Company
john.defranco at hp.com           Availability Clusters Solution Lab
phone: 408 447-7543            19111 Pruneridge Ave., M/S 4101
fax:   408 447-0056            Cupertino, CA 95014