From: PePa <peter@passchier.net>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] cryptsetup-reencode: LUKS-${UUID}.new is too small
Date: Fri, 14 Mar 2014 07:59:28 +0000 (UTC) [thread overview]
Message-ID: <loom.20140314T085159-184@post.gmane.org> (raw)
In-Reply-To: loom.20140312T000413-75@post.gmane.org
Reporting back, I did:
cryptsetup-reencrypt -c aes-xts-plain64 -s 512 -h sha512
--reduce-device-size 4MiB /dev/sda4
It stopped here:
Progress: 99.4%, ETA 02:48, 710848 MiB written, speed 27.0 MiB/s
IO error during reencryption.
Curiously, I did:
cryptsetup luksOpen /dev/sda4 secret
Output>:
Device /dev/sda4 is not a valid LUKS device.
:-( Is there anything I can still try to salvage this situation??
Thanks,
Peter
next prev parent reply other threads:[~2014-03-14 7:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 23:16 [dm-crypt] cryptsetup-reencode: LUKS-${UUID}.new is too small PePa
2014-03-12 0:54 ` Arno Wagner
2014-03-12 21:29 ` PePa
2014-03-12 22:36 ` Arno Wagner
2014-03-13 0:29 ` Matthias Schniedermeyer
2014-03-13 1:31 ` Arno Wagner
2014-03-13 6:34 ` Milan Broz
2014-03-13 7:43 ` PePa
2014-03-18 22:43 ` [dm-crypt] cryptsetup-reencode:LUKS-${UUID}.new " PePa
2014-03-14 7:59 ` PePa [this message]
2014-03-14 13:22 ` [dm-crypt] cryptsetup-reencode: LUKS-${UUID}.new " Arno Wagner
2014-03-14 16:39 ` PePa
2014-03-14 16:46 ` PePa
2014-03-14 17:20 ` Milan Broz
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=loom.20140314T085159-184@post.gmane.org \
--to=peter@passchier.net \
--cc=dm-crypt@saout.de \
/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