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: