Bug 1028054 - enterprise-storage profile does not multiply readahead values for dm* devices
enterprise-storage profile does not multiply readahead values for dm* devices
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: tuned (Show other bugs)
7.0
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Jaroslav Škarvada
qe-baseos-daemons
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-07 09:52 EST by Branislav Blaškovič
Modified: 2013-11-08 12:03 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-11-08 12:03:16 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Branislav Blaškovič 2013-11-07 09:52:59 EST
Description of problem:
Applying enterprise-storage profile from tuned-profiles-compat package does not multiply readahead values for dm* devices.

Version-Release number of selected component (if applicable):
tuned-2.2.2-3.el7.noarch
tuned-profiles-compat-2.2.2-3.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. blockdev --getra /dev/dm-0
2. tuned-adm profile enterprise-storage
3. blockdev --getra /dev/dm-0

Actual results:
Readahead values are not changed.

Expected results:
Readahead values should be multiplyied by 4.

Additional info:
This profile is importing throughput-performance profile which has option:

[disk]
devices=sd*,cciss*,dm-*,vd*

and enterprise-storage profile has:

[disk]
readahead_multiply=4

So I assume that it should work.
Comment 2 Jaroslav Škarvada 2013-11-07 10:25:54 EST
In tuned-2.3.0 the
[disk]
devices=sd*,cciss*,dm-*,vd*

was removed from the throughput-performance profile. See bug 922068 comment 12 and bug 922068 comment 17. So this is probably OK.
Comment 3 Jaroslav Škarvada 2013-11-08 12:03:16 EST
Closing per comment 2.

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