From: "Brian J. Murrell" <brianjmurrell@gmail.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] device-mapper: thin: 253:2: pool target (4105216 blocks) too small: expected 492672
Date: Fri, 16 Dec 2016 17:11:04 -0500 [thread overview]
Message-ID: <1481926264.487.17.camel@gmail.com> (raw)
I have a bit of an urgent/emergency situation here unfortunately. �It
seems I have run into this:
https://www.redhat.com/archives/linux-lvm/2016-May/msg00092.html
again, this time on a centos7 machine.
When this happened last time, in this message
https://www.redhat.com/archives/linux-lvm/2016-June/msg00003.html
Zdenek Kabelac was able to give me a fixed config that I could
vgcfgrestore to get access to my thin pool back. �Best would be if I
could get an explanation how to get that fixed config. �But if need be
I can provide that 1MB of the disk to be repaired by somebody
else.��I'd really like to learn how to do this myself though, if
somebody would be so kind.
As soon as I send this I will get that 1MB extracted and posted
somewhere in case it's just easier to provide a fixed config rather
than the how-to fix it instructions.
Many many thanks in advance for being able to look at this. �The
machine that suffered this kind of at the center of everything here.
Cheers,
b.
reply other threads:[~2016-12-16 22:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1481926264.487.17.camel@gmail.com \
--to=brianjmurrell@gmail.com \
--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).