I have a VG made from several PV's, one of which (mostly) failed. Anticipating this, I had moved all key LVs to be backed by other disks. The system runs off those LVs. When I try to run LVM commands, I get lots of errors, e.g., # lvs daisy /dev/dm-9: read failed after 0 of 4096 at 0: Input/output error /dev/dm-10: read failed after 0 of 4096 at 0: Input/output error /dev/dm-11: read failed after 0 of 4096 at 0: Input/output error /dev/dm-12: read failed after 0 of 4096 at 0: Input/output error [etc] /dev/sdb: read failed after 0 of 4096 at 0: Input/output error /dev/sdb1: read failed after 0 of 2048 at 0: Input/output error /dev/sdb2: read failed after 0 of 2048 at 0: Input/output error /dev/sdb5: read failed after 0 of 4096 at 0: Input/output error Couldn't find device with uuid 'qqWQc6-Ucv9-8htm-TnOz-n1Va-9L0g-H3WA6o'. Couldn't find all physical volumes for volume group daisy. Volume group "daisy" not found The last message in particular is weird, since many LVs from daisy are successfully mounted. How can I get LVM to overlook the problem, or access the setup enough to remove the bad PV from the VG? I believe sdb5 is the only PV from sdb that is in the VG. It may be relevant that the bad drive sort of comes up: during system startup it was detected and some of its LVs were mounted. This led to an apparently successful replay of the log on one LV, and the start of an fsck on another before errors apparently caused it to be dropped. # vgs --version LVM version: 2.02.39 (2008-06-27) Library version: 1.02.27 (2008-06-25) Driver version: 4.13.0 The failed disk is SATA. Running Debian Lenny with Linux 2.6.26-2-686 kernel. Thanks. Ross Boylan P.S. Yes, I'm thinking about RAID. No, there is no RAID in the current system at any level (lvm, dm, hardware). _______________________________________________ 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/
