Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

Run this on my laptop:

# cryptsetup status /dev/mapper/luks-a6392fe0-ce8c-4049-9c76-88835e858f82 
/dev/mapper//dev/mapper/luks-a6392fe0-ce8c-4049-9c76-88835e858f82 is active and is in use.
  type:  LUKS1
  cipher:  aes-xts-plain64
  keysize: 512 bits
  device:  /dev/sda3
  offset:  4096 sectors
  size:    192858112 sectors
  mode:    read/write


Notice "/dev/mapper//dev/mapper/" string in the beginning. 


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

How reproducible:
always

Hm. But status really takes just mapped name for argument, not a path.
This should not work at all :)

Fixed in cryptsetup-luks-1.2.0-7.el6.

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

# cryptsetup status /dev/mapper/luks-14e91c9c-3159-444c-bf4d-f7af8814728c
/dev/mapper/luks-14e91c9c-3159-444c-bf4d-f7af8814728c is active and is in use.
  type:  LUKS1
  cipher:  aes-xts-plain64
  keysize: 512 bits
  device:  /dev/vda2
  offset:  4096 sectors
  size:    15747072 sectors
  mode:    read/write

# cryptsetup status luks-14e91c9c-3159-444c-bf4d-f7af8814728c
/dev/mapper/luks-14e91c9c-3159-444c-bf4d-f7af8814728c is active and is in use.
  type:  LUKS1
  cipher:  aes-xts-plain64
  keysize: 512 bits
  device:  /dev/vda2
  offset:  4096 sectors
  size:    15747072 sectors
  mode:    read/write


VERIFIED.

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