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.
Bug 1551155 - [RFE] Provide a general listing of all currently open crypt volumes.
Summary: [RFE] Provide a general listing of all currently open crypt volumes.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: cryptsetup
Version: 7.5
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Ondrej Kozina
QA Contact: Storage QE
URL:
Whiteboard:
Depends On:
Blocks: 1733345
TreeView+ depends on / blocked
 
Reported: 2018-03-02 23:13 UTC by Corey Marthaler
Modified: 2021-09-06 15:04 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1733345 (view as bug list)
Environment:
Last Closed: 2021-02-15 07:35:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Corey Marthaler 2018-03-02 23:13:22 UTC
Description of problem:
[root@host-086 ~]# vdo list
vPV4
vPV5
vPV6
vPV7
vPV1
vPV2
vPV3
vPV8

[root@host-086 ~]# pvcreate /dev/mapper/vPV[123456789]
  Physical volume "/dev/mapper/vPV1" successfully created.
  Physical volume "/dev/mapper/vPV2" successfully created.
  Physical volume "/dev/mapper/vPV3" successfully created.
  Physical volume "/dev/mapper/vPV4" successfully created.
  Physical volume "/dev/mapper/vPV5" successfully created.
  Physical volume "/dev/mapper/vPV6" successfully created.
  Physical volume "/dev/mapper/vPV7" successfully created.
  Physical volume "/dev/mapper/vPV8" successfully created.

[root@host-086 ~]# pvs
  PV               VG            Fmt  Attr PSize   PFree  
  /dev/mapper/vPV1               lvm2 ---  <25.95g <25.95g
  /dev/mapper/vPV2               lvm2 ---  <25.95g <25.95g
  /dev/mapper/vPV3               lvm2 ---  <25.95g <25.95g
  /dev/mapper/vPV4               lvm2 ---  <25.95g <25.95g
  /dev/mapper/vPV5               lvm2 ---  <25.95g <25.95g
  /dev/mapper/vPV6               lvm2 ---  <25.95g <25.95g
  /dev/mapper/vPV7               lvm2 ---  <25.95g <25.95g
  /dev/mapper/vPV8               lvm2 ---  <25.95g <25.95g

# Is there an equivalent to 'vdo list' or 'pvs', like 'cryptsetup list' or something that can show me all the crypt volumes, besides playing around with dmsetup?

[root@host-083 ~]# dmsetup status | grep crypt
cPV5: 0 62898096 crypt 
cPV4: 0 62898096 crypt 
cPV3: 0 62898096 crypt 
cPV2: 0 62898096 crypt 
cPV1: 0 62898096 crypt 
cPV8: 0 62898096 crypt 
cPV7: 0 62898096 crypt 
cPV6: 0 62898096 crypt 

# Our test tools need to clean up from old runs that may not have completed properly and it would be nice to have a simple list of what is currently open. Maybe something already exists but it didn't pop out at me from reading the man page.


Version-Release number of selected component (if applicable):
cryptsetup-libs-1.7.4-4.el7.x86_64
cryptsetup-1.7.4-4.el7.x86_64

Comment 3 Milan Broz 2018-03-03 11:26:49 UTC
Why you cannot use lsblk? The TYPE is actually parsed from the DM-UUID field (if set), is is set to crypt here.

(For now it prints crypt even for integrity devices, maybe that need to be fixed though.)

Comment 4 Corey Marthaler 2020-10-12 16:09:58 UTC
Couldn't the same argument be made for lvm, vdo, or mdadm volumes? 

Use the appropriate lvm or vdo or mdadm userspace utilities to create, remove, and alter your devices, but, if you want to display or list your devices, just use "lsblk" or "dmsetup status". The answer is because it's cumbersome. If a utility can create, delete, or alter storage, in my opinion it should be able to display/list those same devices and their attributes.

Comment 8 RHEL Program Management 2021-02-15 07:35:37 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


Note You need to log in before you can comment on or make changes to this bug.