DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] cryptsetup-reencode: LUKS-${UUID}.new is too small
Date: Fri, 14 Mar 2014 14:22:57 +0100	[thread overview]
Message-ID: <20140314132256.GA31187@tansi.org> (raw)
In-Reply-To: <loom.20140314T085159-184@post.gmane.org>

I doubt it. Restore your backup. (And meditate on
the wisdom of those that have recomended it...).

The IO error is worrying though, it should _not_ happen.
Have a look into the system error log to see if this is 
some lower-level error. It may also be some problem 
with your LVM setup. (I cannot help there, in my opinion
LVM is too complicated and causes more trouble than it
has benefits.)

Arno

On Fri, Mar 14, 2014 at 08:59:28 CET, PePa wrote:
> 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
> 
> 
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt

-- 
Arno Wagner,     Dr. sc. techn., Dipl. Inform.,    Email: arno@wagner.name
GnuPG: ID: CB5D9718  FP: 12D6 C03B 1B30 33BB 13CF  B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -  Plato

  reply	other threads:[~2014-03-14 13:22 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 ` [dm-crypt] cryptsetup-reencode: LUKS-${UUID}.new " PePa
2014-03-14 13:22   ` Arno Wagner [this message]
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=20140314132256.GA31187@tansi.org \
    --to=arno@wagner.name \
    --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