Your message dated Wed, 08 Oct 2014 15:48:35 +0200
with message-id <[email protected]>
and subject line Re: [pkg-cryptsetup-devel] Bug#764469: cryptsetup close not
working
has caused the Debian Bug report #764469,
regarding cryptsetup close not working
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
764469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764469
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cryptsetup
Version: 2:1.6.6-1
Severity: normal
Dear Maintainer,
cryptsetup close is not working for me:
> # cryptsetup luksClose cryptbackup
> Device cryptbackup is not active.
Maybe related: even if the file-system is mountet:
> # mount | grep mnt
> /dev/mapper/crypbackup on /mnt type ext4 (rw,relatime,data=ordered)
cryptsetup status still reports inactive:
> # cryptsetup status cryptbackup
> /dev/mapper/cryptbackup is inactive.
Remove with dmsetup works:
> # dmsetup remove /dev/mapper/crypbackup
Regards
Daniel
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages cryptsetup depends on:
ii cryptsetup-bin 2:1.6.6-1
ii debconf [debconf-2.0] 1.5.53
ii dmsetup 2:1.02.90-2
ii libc6 2.19-11
Versions of packages cryptsetup recommends:
ii busybox 1:1.22.0-9
ii console-setup 1.113
ii initramfs-tools [linux-initramfs-tool] 0.118
ii kbd 1.15.5-1
Versions of packages cryptsetup suggests:
ii dosfstools 3.0.26-3
ii keyutils 1.5.9-5
ii liblocale-gettext-perl 1.05-8+b1
-- debconf information:
cryptsetup/prerm_active_mappings: true
--- End Message ---
--- Begin Message ---
Hello Daniel,
Am 2014-10-08 13:26, schrieb Daniel Maier:
cryptsetup close is not working for me:
# cryptsetup luksClose cryptbackup
Device cryptbackup is not active.
Maybe related: even if the file-system is mountet:
# mount | grep mnt
/dev/mapper/crypbackup on /mnt type ext4 (rw,relatime,data=ordered)
cryptsetup status still reports inactive:
# cryptsetup status cryptbackup
/dev/mapper/cryptbackup is inactive.
Apparently, you fell prey to a typo. Your LUKS dm-crypt device is
'crypbackup', not 'cryptbackup' (the 't' is missing). Re-read your
mail thoughfully and you will find the mistake.
Remove with dmsetup works:
# dmsetup remove /dev/mapper/crypbackup
Here you gave the correct device name ;)
Kind regards,
jonas
--- End Message ---
