From: Ondrej Kozina <okozina@redhat.com>
To: Felix Wagner <felix@wagner-felix.com>, dm-crypt@saout.de
Subject: Re: [dm-crypt] help
Date: Thu, 25 Feb 2016 18:25:57 +0100 [thread overview]
Message-ID: <56CF3925.5060504@redhat.com> (raw)
In-Reply-To: <56CF2938.2010102@redhat.com>
Hi again,
so I'm afraid you've actually found quite ugly bug in
cryptsetup-reencrypt utility. Nevertheless there's still hope for your
data because I believe the utility haven't overwritten any data. Keep
reading.
I tried to reproduce the behaviour you've experienced:
Whenever I run cryptsetup-reencrypt and try to reference the luks device
by /dev/disk/by-uuid symlink the utility fails. What is worse is fact
that after this kind of failure (which is first bug) it removed the log
file and header backup after it marked "dirty" the luks header on your
drive (which much worse)!
I'll take care of these bugs, please follow the steps Milan sent on the
list to recover your header. In fact it's not deleted only dirtied by
the reencrypt utility.
Regards
O.
next prev parent reply other threads:[~2016-02-25 17:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 15:08 [dm-crypt] help Felix Wagner
2016-02-25 16:18 ` Ondrej Kozina
2016-02-25 17:25 ` Ondrej Kozina [this message]
2016-02-25 16:37 ` Milan Broz
2016-02-25 17:05 ` Felix Wagner
2016-02-25 17:20 ` Milan Broz
2016-02-25 17:35 ` Felix Wagner
2016-02-25 17:49 ` Felix Wagner
2016-02-25 17:55 ` Milan Broz
2016-02-25 17:58 ` Felix Wagner
-- strict thread matches above, loose matches on Subject: below --
2016-02-25 14:50 Felix Wagner
2016-01-10 17:07 Eugen Rogoza
2012-04-20 15:58 [dm-crypt] Help Simon Bing
2012-04-22 8:59 ` Arno Wagner
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=56CF3925.5060504@redhat.com \
--to=okozina@redhat.com \
--cc=dm-crypt@saout.de \
--cc=felix@wagner-felix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.