From: haaber <haaber@web.de>
To: lvm-devel@redhat.com
Subject: Data recovery -- thin provisioned LVM metadata (?) problem after hardware failure
Date: Fri, 12 May 2023 20:05:06 +0200 [thread overview]
Message-ID: <a26e4bad-73e9-694c-2f77-cadf2a3ebf87@web.de> (raw)
In-Reply-To: <CALjSBEtkaooosocEAOpa9uuA0d_dYVLhbkfRbTSHGnuixPAyUg@mail.gmail.com>
Dear Ming-Hung,
>
> There's one corrupted leaf node in device #20081, which might possibly
> be caused by the hardware failure and that stops thin_dump or
> lvconvert from working. Running thin_check would show you the details
> (I'm using the v1.0.5):
>
> TRANSACTION_ID=45452
> METADATA_FREE_BLOCKS=11827
> 1 nodes in data mapping tree contain errors
> 0 io errors, 1 checksum errors
> Thin device 20081 has 1 error nodes and is missing 22664 mappings,
> while expected 296263
> Check of mappings failed
>
> The issue is repairable by rolling back to the previous transaction.
> I'm going to patch the program to make it easier to use. It should be
> ready next week, and you can try to learn how to build the Rust
> version for now.
>
> 1. Install the Rust toolchain via the rustup script (https://rustup.rs/)
> 2. Clone the thin-provisioning-tools.git repo, then build it (cargo
> build --release)
> 3. Try the built pdata_tools binary (placed under ./target/release/)
>
thank you for this inspection! ? I now have hope again to recover my data :)
Silly question: I? cloned
https://github.com/jthornber/thin-provisioning-tools and installed that
way successfully 1.0.4 but that is not the 1.0.5 branch you talked
about. Could you point the right 1.0.5 git, please?
thank you, Bernhard
next prev parent reply other threads:[~2023-05-12 18:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 13:49 Data recovery -- thin provisioned LVM metadata (?) problem after hardware failure haaber
2023-04-26 11:10 ` Zdenek Kabelac
2023-04-26 13:12 ` haaber
2023-04-27 9:29 ` Zdenek Kabelac
2023-05-03 16:48 ` haaber
2023-05-04 13:17 ` Zdenek Kabelac
2023-05-04 16:31 ` haaber
2023-05-05 15:14 ` Zdenek Kabelac
2023-05-04 17:06 ` haaber
2023-05-05 9:42 ` Ming Hung Tsai
2023-05-05 15:07 ` Zdenek Kabelac
2023-05-05 16:25 ` Ming Hung Tsai
2023-05-11 7:39 ` haaber
2023-05-12 3:29 ` Ming Hung Tsai
2023-05-12 18:05 ` haaber [this message]
2023-05-13 3:20 ` Ming Hung Tsai
2023-05-17 15:17 ` Ming Hung Tsai
2023-05-20 20:34 ` haaber
2023-05-22 7:40 ` Ming Hung Tsai
2023-05-23 15:24 ` [SOLVED] " haaber
2023-04-26 12:06 ` Ming Hung Tsai
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=a26e4bad-73e9-694c-2f77-cadf2a3ebf87@web.de \
--to=haaber@web.de \
--cc=lvm-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.