From: Dennis Schridde <devurandom@gmx.net>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Check of pool ernie/cache failed (status:1). Manual repair required!
Date: Tue, 15 May 2018 10:11:36 +0200 [thread overview]
Message-ID: <2230803.usHgyXdh9J@monk> (raw)
In-Reply-To: <2496144.kxeQXG1iRO@monk>
[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]
Hello!
In case the question comes up: Fedora 28 (the live system I am trying to use
for recovery) is using Linux 4.16.3-301.fc28 and `lvm version`:
LVM version 2.02.177(2)
Library version 1.02.146
Driver version 4.37.0
The system I was originally using to break the cache was using Linux 4.16.7-
gentoo, and `LD_LIBRARY_PATH=$PWD/lib64 ./bin/lvm version` from its initrd
reports (running on the Fedora 28 live system):
LVM version: 2.02.173(2)
Library version: 1.02.142
Driver version: 4.37.0
Could someone please give me a hint what is actually broken here? Is it just
the metadata? If so, how can that break -- shouldn't that metadata never be
modified after creating the LV? And could it not be recovered from /etc/lvm/
archive? What does "manual repair" mean in detail? 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?
Best regards,
Dennis
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2018-05-15 8:11 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 [this message]
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
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=2230803.usHgyXdh9J@monk \
--to=devurandom@gmx.net \
--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).