| After googling a lot I figure out what to do and it worked - at least I can access the most critical data.
However, I have no idea what was the root cause of this. I hope I can fully recover the volumes w/o re-creating the whole VG. In case I did something terribly wrong that looked like the solution now, but may cause issues in future - I would appreciate any hints.
—
Best Regards,
Łukasz Czerpak
Hi,
I cannot get my LVM working.
The structure is as follows:
vg1 -> thinpool1 -> 11x lvs
I extended size of one of child LVs, after that ran xfs_growfs which got stuck. After 1hr I did cold reboot and thinpool reported the following:
$ lvchange -ay vg1
WARNING: Not using lvmetad because a repair command was run.
Thin pool vg1-thinpool1-tpool (253:3) transaction_id is 549, while expected 505.
Thin pool vg1-thinpool1-tpool (253:3) transaction_id is 549, while expected 505.
Thin pool vg1-thinpool1-tpool (253:3) transaction_id is 549, while expected 505.
Thin pool vg1-thinpool1-tpool (253:3) transaction_id is 549, while expected 505.
Thin pool vg1-thinpool1-tpool (253:3) transaction_id is 549, while expected 505.
Thin pool vg1-thinpool1-tpool (253:3) transaction_id is 549, while expected 505.
Thin pool vg1-thinpool1-tpool (253:3) transaction_id is 549, while expected 505.
Thin pool vg1-thinpool1-tpool (253:3) transaction_id is 549, while expected 505.
Thin pool vg1-thinpool1-tpool (253:3) transaction_id is 549, while expected 505.
Thin pool vg1-thinpool1-tpool (253:3) transaction_id is 549, while expected 505.
Thin pool vg1-thinpool1-tpool (253:3) transaction_id is 549, while expected 505.
Thin pool vg1-thinpool1-tpool (253:3) transaction_id is 549, while expected 505.
I tried lvconvert —repair vg1/thinpool1 but it always throws transaction id mismatch error:
$ lvconvert --repair vg1/thinpool1
WARNING: Disabling lvmetad cache for repair command.
WARNING: Not using lvmetad because of repair.
Transaction id 505 from pool "vg1/thinpool1" does not match repaired transaction id 549 from /dev/mapper/vg1-lvol2_pmspare.
WARNING: LV vg1/thinpool1_meta3 holds a backup of the unrepaired metadata. Use lvremove when no longer required.
WARNING: New metadata LV vg1/thinpool1_tmeta might use different PVs. Move it with pvmove if required.
I have no idea on how to proceed and more importantly *how to access/recover data in LVs*. I desperately looking for any help :(
—
Best regards,
Łukasz Czerpak
|
_______________________________________________
linux-lvm mailing list
linux-lvm@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
