All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: lvm-devel@redhat.com
Subject: Data recovery -- thin provisioned LVM metadata (?) problem after hardware failure
Date: Fri, 5 May 2023 17:07:54 +0200	[thread overview]
Message-ID: <2b1b2d49-fe46-e544-03d3-79b831df4a52@gmail.com> (raw)
In-Reply-To: <6c1b291d-b4e4-4698-b9b4-63c43e9e484d@web.de>

Dne 04. 05. 23 v 19:06 haaber napsal(a):
> Dear Zdenek,
> 
> here https://we.tl/t-41PiPG2V1G???? is the output of
> 
> #thin_dump?? /dev/qubes_dom0/pool00_tmeta? > pool00_tmeta
> 

Hi

We need the exact binary copy of _tmeta  LV  - thus just use

dd if=/dev/qubes_dom0/pool00_tmeta  /tmp/tmeta_copy  bs=512K
bzip2 /tmp/tmeta_copy

With this data - also provide full lvm2 metadata for this VG
(should be as a file in  /etc/lvm/backup  - or you could run
just vgcfgbackup)

thin_dump is already 'processed' result - so not usable for futher investigation.

(Although it might interesting idea to add some 'option' to actually provide 
the above 'binary backup' is  built-in feature of this tool for bug reporting...)


Regards

Zdenek


  parent reply	other threads:[~2023-05-05 15:07 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 [this message]
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
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=2b1b2d49-fe46-e544-03d3-79b831df4a52@gmail.com \
    --to=zdenek.kabelac@gmail.com \
    --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.