From: lampahome <pahome.chen@mirlab.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Difference between thin_ll_xxx & thin_xxx
Date: Thu, 2 Jul 2020 10:16:42 +0800 [thread overview]
Message-ID: <CAB3eZfs+5vx3T9s5W6tUXPfC9GwYyA5kT2aMWHMO9KoUgvYQ4w@mail.gmail.com> (raw)
In-Reply-To: <CAAYit8Tdw91NM+KaqLMBokBy3v4aSdNz88qmherQX5EqVu-BeA@mail.gmail.com>
> thin_ll_* tools are targeted for recovering missing data mappings
> ignored by thin_dump and thin_restore. The name is an acronym standing
> for low-level processing. Below is the quickstart guide.
> https://www.redhat.com/archives/linux-lvm/2016-February/msg00038.html
>
The page doesn't describe detail about thin_ll_* tools.
After I run it, get some observations.
thin_ll_dump seems dump the tree root & mapping tree and orphans
blocknr.(seems having orphans is normal)
And that info is which thin_dump doesn't get it.
prev parent reply other threads:[~2020-07-02 2:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 8:32 [linux-lvm] Difference between thin_ll_xxx & thin_xxx lampahome
2020-07-01 15:08 ` Ming-Hung Tsai
2020-07-02 2:16 ` lampahome [this message]
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=CAB3eZfs+5vx3T9s5W6tUXPfC9GwYyA5kT2aMWHMO9KoUgvYQ4w@mail.gmail.com \
--to=pahome.chen@mirlab.org \
--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).