archive mirror
 help / color / mirror / Atom feed
From: Dennis Schridde <>
Cc: Zdenek Kabelac <>
Subject: Re: [linux-lvm] Check of pool ernie/cache failed (status:1). Manual repair required!
Date: Wed, 23 May 2018 21:39:47 +0200	[thread overview]
Message-ID: <7415801.S7CYg4Nbn9@monk> (raw)
In-Reply-To: <254418594.lCqEE9x6Ep@monk>

[-- Attachment #1: Type: text/plain, Size: 1558 bytes --]

On Wednesday, 16 May 2018 20:31:15 CEST Dennis Schridde wrote:
> On Tuesday, 15 May 2018 13:15:55 CEST Zdenek Kabelac wrote:
> > Dne 15.5.2018 v 10:11 Dennis Schridde napsal(a):
> > To get direct access to metadata - you could use your latest lvm2 2.02.177
> > build (or even 'git master'). In these recent versions there is added
> > support to activate directly these 'subLVs'.  So with latest lvm2 you can:
> > 
> > lvchange -ay  vg/lv_cmeta
> I tried that (using 2.02.177), but it does not work:
> # lvchange -ay ernie/cache_cmeta
>   Operation not permitted on hidden LV ernie/cache_cmeta.

Does anyone have a suggestion how I can activate this volume in order to 
extract the information Zdenek asked for?

For more context please see the start of this thread.  The gist is that my 
cached LV cannot be activated anymore, and `lvconvert --repair` reports:
bad checksum in superblock
  Repair of cache metadata volume of cache ernie/system failed (status:1). 
Manual repair required!

My most important questions are:
* What is broken?
  - What information does the superblock carry / what is its purpose?
  - Where is it located / which part of my disk was damaged?
  - What will be the consequence of it being irrecoverably lost?
* What does "manual repair" mean in detail?
  - Using a specific tool?
  - Flipping bits using a hex editor?
* Is there some way to recover the cache?  Or is it at least possible to 
uncache the LV forcibly, to hopefully recover the data on the origin LV?
* What is your recommendation to minimise data loss?


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2018-05-23 19:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-11 17:34 [linux-lvm] Check of pool ernie/cache failed (status:1). Manual repair required! Dennis Schridde
2018-05-12 11:30 ` Dennis Schridde
2018-05-15  8:11   ` Dennis Schridde
2018-05-15 11:15     ` Zdenek Kabelac
2018-05-16 18:31       ` Dennis Schridde
2018-05-23 19:39         ` Dennis Schridde [this message]
2018-05-26 10:15           ` Dennis Schridde
2018-06-04 11:50       ` Dennis Schridde
2018-06-05  8:14         ` Marian Csontos
2018-06-05 10:08           ` Dennis Schridde

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7415801.S7CYg4Nbn9@monk \ \ \ \

* 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).