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.

+++ This bug was initially created as a clone of Bug #1458061 +++

lvs -a -o+name
  LV   
  lvol0
  [lvol1]

lvs -a -o+name,attr
  LV    Attr      
  lvol0 Owi-a-s---
  lvol0 Owi-a-s---

The output changes according to which columns you select!

Due to this commit which incorrectly overwrites the LV being reported upon when kernel device-mapper status information is queried:

commit 6fd20be629b6dceb96702c5f875a2e612e6f465d
Author: Zdenek Kabelac <zkabelac>
Date:   Mon Dec 5 14:31:25 2016 +0100

    activation: lv_info_with_seg_status API change
    
    Drop LV from passed API arg - it's always segment being checked.
    Also use_layer is now in full control of lv_info_with_seg_status().
    It decides which device needs to be checked to get 'the most info'.
    
    TODO: future version should be able to expose status from


Sometimes the status comes from a different LV from the rest of the data - it is incorrect to change it affecting the caller!

-                       lv = origin_from_cow(lv);
+                       status->lv = lv = origin_from_cow(lv);

Restoring some reported info for old snapshot with:

https://www.redhat.com/archives/lvm-devel/2017-June/msg00027.html

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.

https://access.redhat.com/errata/RHBA-2017:2222