Sorry about that. The unique errors are the same I posted in the first post: # (pvs -o +pv_uuid,lv_name >/dev/null) 2>&1 | sort -u /dev/vg04/swap: read failed after 0 of 4096 at 0: Input/output error /dev/vg04/swap: read failed after 0 of 4096 at 4096: Input/output error /dev/vg04/swap: read failed after 0 of 4096 at 4294901760: Input/output error /dev/vg04/swap: read failed after 0 of 4096 at 4294959104: Input/output error /dev/vg04/vz: read failed after 0 of 4096 at 0: Input/output error /dev/vg04/vz: read failed after 0 of 4096 at 4096: Input/output error /dev/vg04/vz: read failed after 0 of 4096 at 995903864832: Input/output error /dev/vg04/vz: read failed after 0 of 4096 at 995903922176: Input/output error vg04 was indeed entirely on the missing disk. would 'dmsetup remove vg04-swap' and 'dmsetup remove vg04-vz' not remove these? On Sun, Sep 2, 2012 at 9:13 AM, Scott Merrilees <scott@merrilees.net> wrote: > So noreboot fix wanted. Potentially more difficult. > > What about the other command, to collect the unique errors? It should > show pv_uuids of missing pvs. > > I was hoping to see vg04 config. Since we do not, does that mean vg04 > was entirely on the replaced disk? > > IIRC I have previously recreated a pv with the uuid reported by pvs, > and then removed it cleanly. > > You could also look in /etc/lvm/backup/vg04, and you should be able to > get the pv uuids from there. > -- > Scott Merrilees > > _______________________________________________ > 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/
