Bug 755478

Summary: cryptsetup status on encrypted HP Smart Array can't open device
Product: Red Hat Enterprise Linux 6 Reporter: Michal Kovarik <mkovarik>
Component: cryptsetup-luksAssignee: Ondrej Kozina <okozina>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.1CC: agk, atodorov, mbroz, prajnoha, prockai, zkabelac
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: cryptsetup-luks-1.2.0-7.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-20 14:16:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
lvmdump none

Description Michal Kovarik 2011-11-21 09:37:08 UTC
Description of problem:
Status of Luks device on HP Smart Array partition is not shown.

Version-Release number of selected component (if applicable):
cryptsetup-luks-1.2.0-3.el6_1.2.i686


Steps to Reproduce:
1. run graphical installation on system with HP Smart Array
2. create custom partitioning, encrypt root partition
3. finish installation and run 'cryptsetup status $luks', where luks is device from /dev/mapper/luks-*
  
Actual results:
/dev/mapper/luks-cc9e6ab4-688c-4c67-b09d-0bc6c4687c5b is active and is in use.
Device /dev/fd/4/disk/by-uuid/cc9e6ab4-688c-4c67-b09d-0bc6c4687c5b doesn't exist or access denied.


Expected results:
/dev/mapper/luks-cc9e6ab4-688c-4c67-b09d-0bc6c4687c5b is active and is in use.
  type:  LUKS1
  cipher:  aes-xts-plain64
  keysize: 512 bits
  device:  /dev/cciss/c0d0p3 
  offset:  4096 sectors
  size:    68546560 sectors
  mode:    read/write


Additional info:
/dev/fd/4 doesn't exist
/dev/disk/by-uuid/cc9e6ab4-688c-4c67-b09d-0bc6c4687c5b exists

Comment 1 Milan Broz 2011-11-21 10:53:10 UTC
can you please post output of
cryptsetup status luks-cc9e6ab4-688c-4c67-b09d-0bc6c4687c5b --debug

and "dmsetup info -c luks-cc9e6ab4-688c-4c67-b09d-0bc6c4687c5b" ?

Comment 2 Michal Kovarik 2011-11-21 10:58:29 UTC
cryptsetup status luks-cc9e6ab4-688c-4c67-b09d-0bc6c4687c5b --debug:

# cryptsetup 1.2.0 processing "cryptsetup status luks-cc9e6ab4-688c-4c67-b09d-0bc6c4687c5b --debug"
# Initialising device-mapper backend, UDEV is enabled.
# Detected dm-crypt target of version 1.7.0.
# dm status luks-cc9e6ab4-688c-4c67-b09d-0bc6c4687c5b  OF   [16384]
# Releasing device-mapper backend.
/dev/mapper/luks-cc9e6ab4-688c-4c67-b09d-0bc6c4687c5b is active and is in use.
# Allocating crypt device context by device luks-cc9e6ab4-688c-4c67-b09d-0bc6c4687c5b.
# Initialising device-mapper backend, UDEV is enabled.
# dm status luks-cc9e6ab4-688c-4c67-b09d-0bc6c4687c5b  OF   [16384]
# Releasing device-mapper backend.
# Allocating crypt device /dev/fd/4/disk/by-uuid/cc9e6ab4-688c-4c67-b09d-0bc6c4687c5b context.
Device /dev/fd/4/disk/by-uuid/cc9e6ab4-688c-4c67-b09d-0bc6c4687c5b doesn't exist or access denied.
Command failed with code 15: Device /dev/fd/4/disk/by-uuid/cc9e6ab4-688c-4c67-b09d-0bc6c4687c5b doesn't exist or access denied.


dmsetup info -c luks-cc9e6ab4-688c-4c67-b09d-0bc6c4687c5b

Name                                      Maj Min Stat Open Targ Event  UUID                                                                                  
luks-cc9e6ab4-688c-4c67-b09d-0bc6c4687c5b 253   0 L--w    1    1      0 CRYPT-LUKS1-cc9e6ab4688c4c67b09d0bc6c4687c5b-luks-cc9e6ab4-688c-4c67-b09d-0bc6c4687c5b

Comment 3 Milan Broz 2011-11-21 12:01:01 UTC
Strange, can you attach output tarball of lvmdump from the system so I can reproduce it?

Comment 4 Michal Kovarik 2011-11-21 13:55:25 UTC
Created attachment 534785 [details]
lvmdump

Comment 5 Milan Broz 2011-11-21 15:51:33 UTC
Threre is a bug in translation from major:minor of underlying device back to /dev/ path.

For CCISS, it creates /dev/cciss/ subdir and it confuses current code,
if I add top level (fake) node
mknod /dev/test_dev b 104 3
it works.

Should be easy to fix (uptream uses /sys here, it should be RHEL6 only bug).

Comment 8 Milan Broz 2012-02-29 12:42:29 UTC
Fixed in cryptsetup-luks-1.2.0-7.el6.

Comment 12 Alexander Todorov 2012-04-11 12:04:25 UTC
# cryptsetup status luks-13355be6-9803-413e-ab55-6bd4e01233324
/dev/mapper/luks-13355be6-9803-413e-ab55-6bd4e0123324 is active and is in use.
  type:  LUKS1
  cipher:  aes-xts-plain64
  keysize: 512 bits
  device:  /dev/disk/by-uuid/13355be6-9803-413e-ab55-6bd4e0123324
  offset:  4096 sectors
  size:    121303040 sectors
  mode:    read/write

# rpm -q cryptsetup-luks
cryptsetup-luks-1.2.0-7.el6.x86_64

Comment 13 errata-xmlrpc 2012-06-20 14:16:31 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0886.html