Bug 1464739 - Cache & thin pool target always commits data even for unused devices
Cache & thin pool target always commits data even for unused devices
Status: NEW
Product: LVM and device-mapper
Classification: Community
Component: device-mapper (Show other bugs)
2.02.172
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Joe Thornber
cluster-qe@redhat.com
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-25 05:39 EDT by Zdenek Kabelac
Modified: 2017-06-25 05:41 EDT (History)
6 users (show)

See Also:
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: ---
rule-engine: lvm‑technical‑solution?


Attachments (Terms of Use)

  None (edit)
Description Zdenek Kabelac 2017-06-25 05:39:53 EDT
Description of problem:

When user creates thin-pool with unused  thin LV, or  caches a volume, then every call a flushing  'dmsetup status' cause  very small i/o batch to pass on actual real device.

This is not a big deal in case performance, but it prevents unused 'devices' to stay in sleep eventually wakes them up whenever admin runs: 

dmsetup status.

As a workaround to keep disks sleeping - user may 'add --noflush' arg...



Version-Release number of selected component (if applicable):
4.12.0-0.rc6.git3.2.fc27.x86_64

How reproducible:


Steps to Reproduce:
1. create  thinLV  (lvcreate -L10 -V10 -T vg/pool -n thinLV)  (or cache some LV)
2. iostat -d 1
3. observe i/o load with every 'dmsetup status' call

Actual results:


Expected results:


Additional info:

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