Bug 1028054 - enterprise-storage profile does not multiply readahead values for dm* devices
Summary: enterprise-storage profile does not multiply readahead values for dm* devices
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: tuned
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jaroslav Škarvada
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-07 14:52 UTC by Branislav Blaškovič
Modified: 2013-11-08 17:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-08 17:03:16 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Branislav Blaškovič 2013-11-07 14:52:59 UTC 
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 15:25:54 UTC 
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 17:03:16 UTC 
Closing per comment 2.
Note You need to log in before you can comment on or make changes to this bug.