From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mimecast-mx02.redhat.com (mimecast01.extmail.prod.ext.rdu2.redhat.com [10.11.55.17]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 1AFE472908 for ; Sun, 8 Dec 2019 19:35:59 +0000 (UTC) Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [205.139.110.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id E4F5A804831 for ; Sun, 8 Dec 2019 19:35:58 +0000 (UTC) Received: by mail-wm1-f41.google.com with SMTP id f4so13824494wmj.1 for ; Sun, 08 Dec 2019 11:35:56 -0800 (PST) Received: from [192.168.200.100] (80.49.186.102.ipv4.supernova.orange.pl. [80.49.186.102]) by smtp.gmail.com with ESMTPSA id k127sm11000928wmk.31.2019.12.08.11.35.55 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 08 Dec 2019 11:35:55 -0800 (PST) From: =?utf-8?Q?=C5=81ukasz_Czerpak?= Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Message-Id: Date: Sun, 8 Dec 2019 20:35:52 +0100 Content-Transfer-Encoding: 8bit Subject: [linux-lvm] Thin pool vg1-thinpool1-tpool (253:3) transaction_id is 549, while expected 505. Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="utf-8" To: linux-lvm@redhat.com 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