From: Gionatan Danti <g.danti@assyoma.it>
To: "Stuart D. Gathman" <stuart@gathman.org>
Cc: "Dalebjörk, Tomas" <tomas.dalebjork@gmail.com>,
"LVM general discussion and development" <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] exposing snapshot block device
Date: Wed, 23 Oct 2019 08:58:45 +0200 [thread overview]
Message-ID: <df172328d6043d90506718605a4a812e@assyoma.it> (raw)
In-Reply-To: <alpine.LRH.2.21.1910221846190.5121@fairfax.gathman.org>
Il 23-10-2019 00:53 Stuart D. Gathman ha scritto:
> If you can find all the leaf nodes belonging to the root (in my btree
> database they are marked with the root id and can be found by
> sequential
> scan of the volume), then reconstructing the btree data is
> straightforward - even in place.
>
> I remember realizing this was the only way to recover a major
> customer's
> data - and had the utility written, tested, and applied in a 36 hour
> programming marathon (which I hope to never repeat). If this hasn't
> occured to thin pool programmers, I am happy to flesh out the
> procedure.
> Having such a utility available as a last resort would ratchet up the
> reliability of thin pools.
Very interesting. Can I ask you what product/database you recovered?
Anyway, giving similar ability to thin Vols would be awesome.
Thanks.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8
next prev parent reply other threads:[~2019-10-23 6:58 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 10:47 [linux-lvm] exposing snapshot block device Dalebjörk, Tomas
2019-10-22 13:57 ` Zdenek Kabelac
2019-10-22 15:29 ` Dalebjörk, Tomas
2019-10-22 15:36 ` Zdenek Kabelac
2019-10-22 16:13 ` Dalebjörk, Tomas
2019-10-23 10:26 ` Zdenek Kabelac
2019-10-23 10:56 ` Tomas Dalebjörk
2019-10-22 16:15 ` Stuart D. Gathman
2019-10-22 17:02 ` Tomas Dalebjörk
2019-10-22 21:38 ` Gionatan Danti
2019-10-22 22:53 ` Stuart D. Gathman
2019-10-23 6:58 ` Gionatan Danti [this message]
2019-10-23 10:06 ` Tomas Dalebjörk
2019-10-23 10:12 ` Zdenek Kabelac
2019-10-23 10:46 ` Zdenek Kabelac
2019-10-23 11:08 ` Gionatan Danti
2019-10-23 11:24 ` Tomas Dalebjörk
2019-10-23 11:26 ` Tomas Dalebjörk
2019-10-24 16:01 ` Zdenek Kabelac
2019-10-25 16:31 ` Tomas Dalebjörk
2019-11-04 5:54 ` Tomas Dalebjörk
2019-11-04 10:07 ` Zdenek Kabelac
2019-11-04 14:40 ` Tomas Dalebjörk
2019-11-04 15:04 ` Zdenek Kabelac
2019-11-04 17:28 ` Tomas Dalebjörk
2019-11-05 16:24 ` Zdenek Kabelac
2019-11-05 16:40 ` Mikulas Patocka
2019-11-05 20:56 ` Tomas Dalebjörk
2019-11-06 9:22 ` Zdenek Kabelac
2019-11-07 16:54 ` Mikulas Patocka
2019-11-07 17:29 ` Tomas Dalebjörk
2020-09-04 12:09 ` Tomas Dalebjörk
2020-09-04 12:37 ` Zdenek Kabelac
2020-09-07 13:09 ` Mikulas Patocka
2020-09-07 14:14 ` Dalebjörk, Tomas
2020-09-07 14:17 ` Zdenek Kabelac
2020-09-07 16:34 ` Tomas Dalebjörk
2020-09-07 16:42 ` Zdenek Kabelac
2020-09-07 17:37 ` Tomas Dalebjörk
2020-09-07 17:50 ` Zdenek Kabelac
2020-09-08 12:32 ` Dalebjörk, Tomas
2020-09-07 19:56 ` Tomas Dalebjörk
2020-09-07 20:22 ` Tomas Dalebjörk
2020-09-07 21:02 ` Tomas Dalebjörk
2019-10-23 12:12 ` Ilia Zykov
2019-10-23 12:20 ` Ilia Zykov
2019-10-23 13:05 ` Zdenek Kabelac
2019-10-23 14:40 ` Gionatan Danti
2019-10-23 15:46 ` Ilia Zykov
2019-10-23 12:59 ` Zdenek Kabelac
2019-10-23 14:37 ` Gionatan Danti
2019-10-23 15:37 ` Zdenek Kabelac
2019-10-23 17:16 ` Gionatan Danti
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=df172328d6043d90506718605a4a812e@assyoma.it \
--to=g.danti@assyoma.it \
--cc=linux-lvm@redhat.com \
--cc=stuart@gathman.org \
--cc=tomas.dalebjork@gmail.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