From: "Łukasz Czerpak" <lukasz.czerpak@gmail.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Thin pool vg1-thinpool1-tpool (253:3) transaction_id is 549, while expected 505.
Date: Sun, 8 Dec 2019 21:47:20 +0100 [thread overview]
Message-ID: <8B290F6D-9D0B-4186-9F17-AAAB0BFA8DDA@gmail.com> (raw)
In-Reply-To: <D2CA32A7-3D9D-4490-9B42-89DC00E163FE@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2883 bytes --]
After googling a lot I figure out what to do and it worked - at least I can access the most critical data.
I’ve followed instructions from this blog post: https://blog.monotok.org/lvm-transaction-id-mismatch-and-metadata-resize-error/ <https://blog.monotok.org/lvm-transaction-id-mismatch-and-metadata-resize-error/>
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
> On 8 Dec 2019, at 20:35, Łukasz Czerpak <lukasz.czerpak@gmail.com> wrote:
>
> 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
>
>
>
[-- Attachment #2: Type: text/html, Size: 3995 bytes --]
next prev parent reply other threads:[~2019-12-08 20:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-08 19:35 [linux-lvm] Thin pool vg1-thinpool1-tpool (253:3) transaction_id is 549, while expected 505 Łukasz Czerpak
2019-12-08 20:47 ` Łukasz Czerpak [this message]
2019-12-09 13:36 ` Zdenek Kabelac
2019-12-09 13:50 ` Łukasz Czerpak
2019-12-09 13:52 ` Łukasz Czerpak
2019-12-09 13:59 ` Zdenek Kabelac
2019-12-09 14:18 ` Łukasz Czerpak
2019-12-09 14:25 ` Zdenek Kabelac
-- strict thread matches above, loose matches on Subject: below --
2019-12-08 19:30 Łukasz Czerpak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8B290F6D-9D0B-4186-9F17-AAAB0BFA8DDA@gmail.com \
--to=lukasz.czerpak@gmail.com \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).