How did your cache-pool get broken? Power lost or other cause? lvconvert --repair is for thin-pools only, so you might need to repair the cache-pool manually, by using cache_repair and other tools in the package thin-provisioning-tools. I'm not familiar with dm-cache, so I don't know whether there's any limitation in cache_repair. Removing the cache layer might also work, but for safety, you can try to activate the cache origin manually at first (it might be data-lv_corig), to see whether the data is fine or not. Ming-Hung Tsai 2016-12-25 1:44 GMT+08:00 Matt Joyce <mttjocy@gmail.com>: > $ sudo lvchange -ay hdd-vg/data-lv > Check of pool hdd-vg/data-lv_cache failed (status:1). Manual repair required! > > $ sudo lvconvert --repair hdd-vg/data-lv > Can't repair LV "data-lv" of segtype cache. > > $ sudo lvconvert --repair hdd-vg/data-lv_cache > Internal error: pool_is_active called with non-pool LV data-lv_cache. > bad checksum in superblock > Repair of thin metadata volume of thin pool hdd-vg/data-lv_cache > failed (status:1). Manual repair required! > > $ sudo lvremove hdd-vg/data-lv_cache > Do you really want to remove and DISCARD logical volume data-lv_cache? [y/n]: y > Check of pool hdd-vg/data-lv_cache failed (status:1). Manual repair required! > Failed to active cache locally hdd-vg/data-lv. _______________________________________________ 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/
