On Tue, Feb 21, 2017 at 7:06 PM, Gianluca Cecchi <gianluca.cec...@gmail.com> wrote: > The id of the removed storage domain was > 900b1853-e192-4661-a0f9-7c7c396f6f49 and on the not yet reboted hosts I get > this > The multipath device was 3600a0b80002999020000cd3c5501458f > > With pvs command I get this errors related to them: > > [root@ovmsrv06 ~]# pvs > /dev/mapper/3600a0b80002999020000cd3c5501458f: read failed after 0 of 4096 > at 0: Input/output error > /dev/mapper/3600a0b80002999020000cd3c5501458f: read failed after 0 of 4096 > at 2199023190016: Input/output error > /dev/mapper/3600a0b80002999020000cd3c5501458f: read failed after 0 of 4096 > at 2199023247360: Input/output error > /dev/mapper/3600a0b80002999020000cd3c5501458f: read failed after 0 of 4096 > at 4096: Input/output error > /dev/900b1853-e192-4661-a0f9-7c7c396f6f49/metadata: read failed after 0 of > 4096 at 0: Input/output error > /dev/900b1853-e192-4661-a0f9-7c7c396f6f49/metadata: read failed after 0 of > 4096 at 536805376: Input/output error > /dev/900b1853-e192-4661-a0f9-7c7c396f6f49/metadata: read failed after 0 of > 4096 at 536862720: Input/output error > /dev/900b1853-e192-4661-a0f9-7c7c396f6f49/metadata: read failed after 0 of > 4096 at 4096: Input/output error > /dev/900b1853-e192-4661-a0f9-7c7c396f6f49/outbox: read failed after 0 of > 4096 at 0: Input/output error > /dev/900b1853-e192-4661-a0f9-7c7c396f6f49/outbox: read failed after 0 of > 4096 at 134152192: Input/output error > /dev/900b1853-e192-4661-a0f9-7c7c396f6f49/outbox: read failed after 0 of > 4096 at 134209536: Input/output error > /dev/900b1853-e192-4661-a0f9-7c7c396f6f49/outbox: read failed after 0 of > 4096 at 4096: Input/output error > /dev/900b1853-e192-4661-a0f9-7c7c396f6f49/xleases: read failed after 0 of > 4096 at 0: Input/output error > /dev/900b1853-e192-4661-a0f9-7c7c396f6f49/xleases: read failed after 0 of > 4096 at 1073676288: Input/output error > /dev/900b1853-e192-4661-a0f9-7c7c396f6f49/xleases: read failed after 0 of > 4096 at 1073733632: Input/output error > /dev/900b1853-e192-4661-a0f9-7c7c396f6f49/xleases: read failed after 0 of > 4096 at 4096: Input/output error > /dev/900b1853-e192-4661-a0f9-7c7c396f6f49/leases: read failed after 0 of > 4096 at 0: Input/output error > /dev/900b1853-e192-4661-a0f9-7c7c396f6f49/leases: read failed after 0 of > 4096 at 2147418112: Input/output error > /dev/900b1853-e192-4661-a0f9-7c7c396f6f49/leases: read failed after 0 of > 4096 at 2147475456: Input/output error > /dev/900b1853-e192-4661-a0f9-7c7c396f6f49/leases: read failed after 0 of > 4096 at 4096: Input/output error > /dev/900b1853-e192-4661-a0f9-7c7c396f6f49/ids: read failed after 0 of 4096 > at 0: Input/output error > /dev/900b1853-e192-4661-a0f9-7c7c396f6f49/ids: read failed after 0 of 4096 > at 134152192: Input/output error > /dev/900b1853-e192-4661-a0f9-7c7c396f6f49/ids: read failed after 0 of 4096 > at 134209536: Input/output error > /dev/900b1853-e192-4661-a0f9-7c7c396f6f49/ids: read failed after 0 of 4096 > at 4096: Input/output error > /dev/900b1853-e192-4661-a0f9-7c7c396f6f49/inbox: read failed after 0 of > 4096 at 0: Input/output error > /dev/900b1853-e192-4661-a0f9-7c7c396f6f49/inbox: read failed after 0 of > 4096 at 134152192: Input/output error > /dev/900b1853-e192-4661-a0f9-7c7c396f6f49/inbox: read failed after 0 of > 4096 at 134209536: Input/output error > /dev/900b1853-e192-4661-a0f9-7c7c396f6f49/inbox: read failed after 0 of > 4096 at 4096: Input/output error > /dev/900b1853-e192-4661-a0f9-7c7c396f6f49/master: read failed after 0 of > 4096 at 0: Input/output error > /dev/900b1853-e192-4661-a0f9-7c7c396f6f49/master: read failed after 0 of > 4096 at 1073676288: Input/output error > /dev/900b1853-e192-4661-a0f9-7c7c396f6f49/master: read failed after 0 of > 4096 at 1073733632: Input/output error > /dev/900b1853-e192-4661-a0f9-7c7c396f6f49/master: read failed after 0 of > 4096 at 4096: Input/output error > PV VG > Fmt Attr PSize PFree > /dev/cciss/c0d0p2 cl > lvm2 a-- 67.33g 0 > /dev/mapper/3600a0b8000299aa80000d08b55014119 > 922b5269-ab56-4c4d-838f-49d33427e2ab lvm2 a-- 4.00t 3.49t > [root@ovmsrv06 ~]# > > How to clean?
This is caused by active lvs on the remove storage domains that were not deactivated during the removal. This is a very old known issue. You have remove the remove device mapper entries - you can see the devices using: dmsetup status Then you can remove the mapping using: dmsetup remove device-name Once you removed the stale lvs, you will be able to remove the multipath device and the underlying paths, and lvm will not complain about read errors. Nir > > Gianluca > > > _______________________________________________ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users