linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Dennis Schridde <devurandom@gmx.net>
To: linux-lvm@redhat.com
Cc: Marian Csontos <mcsontos@redhat.com>,
	Zdenek Kabelac <zkabelac@redhat.com>
Subject: Re: [linux-lvm] Check of pool ernie/cache failed (status:1). Manual repair required!
Date: Tue, 05 Jun 2018 12:08:27 +0200	[thread overview]
Message-ID: <13069944.niihZIYQkx@monk> (raw)
In-Reply-To: <184ec98a-a34a-1338-a520-ff7669007e5d@redhat.com>

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

On Tuesday, 5 June 2018 10:14:16 CEST Marian Csontos wrote:
> On 06/04/2018 01:50 PM, Dennis Schridde wrote:
> > On Tuesday, 15 May 2018 13:15:55 CEST Zdenek Kabelac wrote:
> >> 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
> > 
> > This command was only successful in LVM 2.02.178-rc1, but failed in
> > 2.02.177.> 
> >> and then you can capture content of this LV via 'dd' into file
> >> and compress and attach 'xz' compressed to BZ.
> > 
> > I created a report in bugzilla [4], but since the `cache_cmeta` LV appears
> > to contain parts of my personal files, I cannot attach it.  However, I
> > gained
> It definitely should not. _cdata is where fragments you your data are
> stored, and _cmeta contains only metadata (e.g. counters and references
> to cdata.)
> 
> If there really are fragments of data in _cmeta LV, something must have
> gone wrong elsewhere.

Thanks for the insight.  I attached the first 4890783 bytes (i.e. those before 
the blocks of seemingly unstructured data, which I saw in `hexdump -C`) of 
that LV to the bug report [4].  Hopefully it contains enough information to 
figure out what is broken.

[4]: https://bugzilla.redhat.com/show_bug.cgi?id=1585670

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

      reply	other threads:[~2018-06-05 10:08 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
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 [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=13069944.niihZIYQkx@monk \
    --to=devurandom@gmx.net \
    --cc=linux-lvm@redhat.com \
    --cc=mcsontos@redhat.com \
    --cc=zkabelac@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).