Bug 1193682
| Summary: | throughput-performance profile triggers hdparm commands on hotplug events | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Scott Dodson <sdodson> |
| Component: | tuned | Assignee: | Jaroslav Škarvada <jskarvad> |
| Status: | CLOSED ERRATA | QA Contact: | Tereza Cerna <tcerna> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.1 | CC: | jeder, jscotka, jskarvad, tcerna |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | tuned-2.5.1-3.el7 | Doc Type: | Bug Fix |
| Doc Text: |
Cause:
Previously hotplug events triggered by insertion of block devices could cause hdparm calls even if hdparm related settings aren't specified in Tuned profile.
Consequence:
APM and spindown settings of the newly attached rotary disks could be changed to non-requested values or related errors may be logged to Tuned log (e.g. if APM or spindown settings are not supported by the block device or hdparm package is not installed).
Fix:
The problem was that the hotplug event could initiate the code path for initialization of dynamic tuning even if the dynamic tuning was disabled. The code was fixed and now if the dynamic tuning is disabled the execution don't go the path for dynamic tuning.
Result:
Hdparm is now not called on hotplug events if dynamic tuning is disabled and hdparm related parameters are not set in the Tuned profile.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-11-19 12:21:42 UTC | 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
Scott Dodson
2015-02-17 21:29:01 UTC
Upstream commit fixing this problem: https://git.fedorahosted.org/cgit/tuned.git/commit/?id=6c155396eecc0258ad2429e44656f1664872d9f6 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-2375.html |