From: Oliver Rath <rath@mglug.de>
To: linux-lvm@redhat.com
Subject: [linux-lvm] thinpool undeleteable after server crash
Date: Mon, 10 Feb 2014 14:06:50 +0100 [thread overview]
Message-ID: <52F8CEEA.1070105@mglug.de> (raw)
Hi list,
Im using here lvm 2.02.104 with kernel 3.11 and today the server
crashed, so I had to power off and reboot the machin (dont know why at
the mom). After this, the used thinpool-device got an unrecoverable
error (thin_repair didnt help) so i tried to remove the whole vg
including the thinpool and its depending devices, which didnt work.
My only working solution was to overwrite the the first 30MB or the
beginning of the used pv with zeroes (dd if=/dev/zero of=/dev/sda1),
then to reboot and NOW to recreate the whole thing.
This seems not to be the best solution for this, so here my questions:
Is it possible to force recreate of a thinpool device when it is
crashing? What can I do to avoid unrecoverable errors on thinpools? Is
there a better possibility for recreation of pv/vg/thinpools?
Tfh!
Oliver
next reply other threads:[~2014-02-10 13:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 13:06 Oliver Rath [this message]
2014-02-10 16:21 ` [linux-lvm] thinpool undeleteable after server crash Zdenek Kabelac
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=52F8CEEA.1070105@mglug.de \
--to=rath@mglug.de \
--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).