DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "shmick@riseup.net" <shmick@riseup.net>
To: dm-crypt@saout.de
Subject: [dm-crypt] 1.6.2 - waiting for zero, luksFormat hung
Date: Thu, 21 Nov 2013 03:44:07 +1100	[thread overview]
Message-ID: <528CE6D7.8030005@riseup.net> (raw)

hello all,

any advice to overcome this?

i don't want to change ciphers or other crypto options

ive tried both --cipher twofish-xts-plain64 and --cipher aes-xts-plain64

prior i did modprobe relevant ciphers, hashes

appart for waiting for zero issues, i also cannot benchmark

please see below

running from an amd-64 linux mint 13 system 3 disk software raid 5





cryptsetup --debug --hash sha512 --cipher twofish-xts-plain64
--use-random --key-size 256 --iter-time 2000 luksFormat /dev/md0
# cryptsetup 1.6.2 processing "cryptsetup --debug --hash sha512 --cipher
twofish-xts-plain64 --use-random --key-size 256 --iter-time 2000
luksFormat /dev/md0"
# Running command luksFormat.
# Locking memory.
# Installing SIGINT/SIGTERM handler.
# Unblocking interruption on signal.

WARNING!
========
This will overwrite data on /dev/md0 irrevocably.

Are you sure? (Type uppercase yes): YES
# Allocating crypt device /dev/md0 context.
# Trying to open and read device /dev/md0.
# Initialising device-mapper backend, UDEV is enabled.
# Detected dm-crypt version 1.11.1, dm-ioctl version 4.22.0.
# Timeout set to 0 miliseconds.
# Iteration time set to 2000 miliseconds.
# RNG set to 1 (random).
# Interactive passphrase entry requested.
Enter passphrase:
Verify passphrase:
# Formatting device /dev/md0 as type LUKS1.
# Initialising gcrypt crypto backend.
# Topology: IO (131072/262144), offset = 0; Required alignment is
1048576 bytes.
# Generating LUKS header version 1 using hash sha512, twofish,
xts-plain64, MK 32 bytes
# PBKDF2: 109673 iterations per second using hash sha512.
# Data offset 4096, UUID dcdd4e2c-c8c9-4c62-aaf7-e417506c5f44, digest
iterations 26750
# Updating LUKS header of size 1024 on device /dev/md0
# Reading LUKS header of size 1024 from device /dev/md0
# Adding new keyslot -1 using volume key.
# Calculating data for key slot 0
# Key slot 0 use 107101 password iterations.
# Using hash sha512 for AF in key slot 0, 4000 stripes
# Updating key slot 0 [0x1000] area on device /dev/md0.
# DM-UUID is CRYPT-TEMP-temporary-cryptsetup-6322
# Udev cookie 0xd4dac4c (semid 294919) created
# Udev cookie 0xd4dac4c (semid 294919) incremented
# Udev cookie 0xd4dac4c (semid 294919) incremented
# Udev cookie 0xd4dac4c (semid 294919) assigned to dm_task type 0 with
flags 0xe
# dm create temporary-cryptsetup-6322
CRYPT-TEMP-temporary-cryptsetup-6322 OF   [16384]
# temporary-cryptsetup-6322: Stacking NODE_ADD (252,0) 0:6 0660
# dm reload temporary-cryptsetup-6322  OF   [16384]
# dm resume temporary-cryptsetup-6322  OF   [16384]
# temporary-cryptsetup-6322: Stacking NODE_READ_AHEAD 1024 (flags=1)
# Udev cookie 0xd4dac4c (semid 294919) decremented
# Udev cookie 0xd4dac4c (semid 294919): Waiting for zero


./configure --with-crypto_backend=openssl --enable-dev-random

cryptsetup benchmark

# Tests are approximate using memory only (no storage IO).
cryptsetup: relocation error: cryptsetup: symbol crypt_benchmark_kdf,
version CRYPTSETUP_1.0 not defined in file libcryptsetup.so.4 with link
time reference

             reply	other threads:[~2013-11-20 16:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-20 16:44 shmick [this message]
2013-11-20 19:05 ` [dm-crypt] 1.6.2 - waiting for zero, luksFormat hung Milan Broz
2013-11-21 14:55   ` shmick
2013-11-21 18:58     ` Milan Broz
2013-11-22  7:40       ` shmick
2013-11-22  8:13         ` Milan Broz
2013-11-22  8:38           ` shmick
2013-11-22  9:17             ` Milan Broz
2013-11-22 11:56               ` shmick
2013-11-22 13:11                 ` 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=528CE6D7.8030005@riseup.net \
    --to=shmick@riseup.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