Bug 1429016 - [RFE] provide easier solution to display LVs grouped with their SubLVs
Summary: [RFE] provide easier solution to display LVs grouped with their SubLVs
Keywords:
Status: NEW
Alias: None
Product: LVM and device-mapper
Classification: Community
Component: lvm2
Version: unspecified
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: Fedora
: ---
Assignee: LVM Team
QA Contact: cluster-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-03 20:36 UTC by Heinz Mauelshagen
Modified: 2023-08-10 15:40 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:
rule-engine: lvm-technical-solution?
rule-engine: lvm-test-coverage?


Attachments (Terms of Use)

Description Heinz Mauelshagen 2017-03-03 20:36:28 UTC
Description of problem:
If I want to list e.g. a RaidLV together with its SUbLVs (rimage/rmeta pairs),
I have to do something like "lvs -aS "name=~(^${lv_name}$|^${lvname}_)".

Asimper way to tell lvm2 to "list the LV grouped with its SubLVs would be valuable.

Version-Release number of selected component (if applicable):

All

How reproducible:

Always

Steps to Reproduce:
1. Run aformentioned lvs command witht -S ...
2.
3.

Actual results:

Display the LV with ist SubLVs

Expected results:

Same but simpler command line interface.

E.g. "lvs --sublvs $LV"


Additional info:

Comment 1 Fedora End Of Life 2018-05-03 08:43:57 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.


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