I want to run
thin_check. They say they cannot be ran on live metadata. That's fine by me. The problem is I don't know how to make the metadata not live, while still being able to give
thin_check an argument on what to be ran on.
I see there's an alternative way to use a metadata snapshot, for live metadata, but I don't want to do it that way. I don't want to change anything on the drive at this time.
# lvs -a disk1thin lvm twi-aot--- <4.53t 92.10 83.47 [disk1thin_tdata] lvm Twi-ao---- <4.53t [disk1thin_tmeta] lvm ewi-ao---- 640.00m # # Need to de-activate the metadata - this is the only way I know how, but must not be right # lvchange -an lvm/disk1thin # lvs -a disk1thin lvm twi---t--- <4.53t [disk1thin_tdata] lvm Twi------- <4.53t [disk1thin_tmeta] lvm ewi------- 640.00m # thin_dump <uhh, what goes here?> # thin_dump lvm/disk1thin Couldn't stat path # thin_dump lvm/disk1thin_tdata Couldn't stat path # thin_dump lvm/disk1thin_tmeta Couldn't stat path # thin_dump lvm/disk1thin-tpool Couldn't stat path # ls -la /dev/mapper # crw------- 1 root root 10, 236 May 31 00:28 control # # Not listed # ls -la /dev/lvm/ ls: cannot access '/dev/lvm/': No such file or directory # lvchange -ay lvm/disk1thin_tmeta Operation not permitted on hidden LV lvm/disk1thin_tmeta # # Nope, that didn't work...
I also tried after having them active, running
dmsetup suspend on them, but that does suspend all reads from them like its manpage says, so although they exist in
thin_check can't be ran on them.
I also tried, once the thin pool is deactivated:
# thin_dump /dev/sdh3 bad checksum in superblock, wanted 3832019051
And it says bad checksum for any other device that has a thin volume on it. I know all disks haven't gone bad, so I'm pretty sure this isn't a proper option. Although the thin pool is on this device, the device starts with a smaller non-thin lv, so the option isn't really telling it to look in the right place for the thin volume.