On Tue, Oct 28, 2014 at 05:55:12PM +0400, Vasiliy Tolstov wrote: > thin_dump --repair /dev/mapper/vg1-tp1_tmeta0 thin_dump spits just spits out xml, it doesn't change the device it's reading. So the process is either: thin_dump --repair <dev> > metadata.xml thin_restore -i metadata.xml -o <dev> or you can use the thin_repair tool which does both of these processes. > <superblock uuid="" time="27" transaction="120" data_block_size="128" > nr_data_blocks="7290880"> > </superblock> This is worrying, you seem to have no volumes in your pool? _______________________________________________ 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/