Bug 1357233

Summary: man entry for 'dmsetup status' is missing
Product: [Community] LVM and device-mapper Reporter: Timur Bakeyev <timur>
Component: lvm2Assignee: Zdenek Kabelac <zkabelac>
lvm2 sub component: dmsetup QA Contact: cluster-qe <cluster-qe>
Status: POST --- Docs Contact:
Severity: low    
Priority: unspecified CC: agk, heinzm, jbrassow, msnitzer, prajnoha, zkabelac
Version: 2.02.165Flags: rule-engine: lvm-technical-solution?
rule-engine: lvm-test-coverage?
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Timur Bakeyev 2016-07-17 00:28:04 UTC
Description of problem:

I suspect that this is fixed in later versions of the product, but just in case:

man dmsetup

...

       stats command [options]
              Manages IO statistics regions for devices.  See dmstats(8) for more details.

       stats command [options]
              Outputs status information for each of the device's targets.  With --target, only information relating to the specified target type any is displayed.
              With --noflush, the thin target (from version 1.3.0) doesn't commit any outstanding changes to disk before reporting its statistics.



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


LVM2 2.0.2.160

How reproducible:

man dmsetup

Actual results:

       stats command [options]
              Manages IO statistics regions for devices.  See dmstats(8) for more details.

       stats command [options]
              Outputs status information for each of the device's targets.  With --target, only information relating to the specified target type any is displayed.
              With --noflush, the thin target (from version 1.3.0) doesn't commit any outstanding changes to disk before reporting its statistics.



Expected results:

I expect that the second entry would say 'status' instead.

Also, it would be nice to get description of all that cryptic fields returned for the dm-cache:

store0-mysql: 0 8589934592 cache 8 16211/261120 128 1381150/8175616 2474 5483 17887084 749892 0 1381150 406522 1 writeback 2 migration_threshold 2048 smq 0 rw -
store0-mysql_corig: 0 8589934592 linear
vg00-var: 0 209715200 linear
store0-mysql_cache_cdata: 0 1046478848 linear
store0-mysql_cache_cmeta: 0 2088960 linear

Additional info:

Comment 1 Timur Bakeyev 2016-09-24 14:50:46 UTC
I see the same bug now in 2.02.165. Please, fix the man page for 166 at least?

Comment 2 Zdenek Kabelac 2016-09-26 10:40:16 UTC
Thanks for noticing.

Fixed by:

https://www.redhat.com/archives/lvm-devel/2016-September/msg00088.html