Bug 49231 - /etc/sysconfig/harddisks sets same parameters for all hard-disks
Summary: /etc/sysconfig/harddisks sets same parameters for all hard-disks
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: hdparm
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Karsten Hopp
QA Contact: Aaron Brown
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-07-17 08:42 UTC by Need Real Name
Modified: 2007-04-18 16:34 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-07-17 08:42:37 UTC
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2001-07-17 08:42:33 UTC
Description of Problem:

I have a UDMA hdd and a PIO one.
Used to have a different hdparm command in rc.local for each one.
I tried to use /etc/sysconfig/harddisks and saw that it sets the same
parameters for all hard disks. The PIO one got upset and froze the system.


How Reproducible:
Every time

Steps to Reproduce:
1. Edit /etc/sysconfig/harddisks
2. USE_DMA=1
3. EXTRA_PARAMS=-X662. 


Actual Results:
System freeze


Expected Results:
Optimal hard-disk tunning

Additional Information:
/etc/sysconfig/harddisks should have sections for each hard-disk

[/dev/hda]
USE_DMA=1
EXTRA_PARAMS=-X66

[/dev/hdb]
USE_DMA=0

Comment 1 Karsten Hopp 2001-07-17 10:02:05 UTC
/etc/sysconfig/harddisks sets the default hdparm parameters for all IDE
harddisks in you system, that's correct.
But if you copy this file to /etc/sysconfig/harddiskhda, you can set 
parameters for /dev/hda in it. 
Have a look at the comment in /etc/rc.d/rc.sysinit:
# Turn on harddisk optimization
# There is only one file /etc/sysconfig/harddisks for all disks
# after installing the hdparm-RPM. If you need different hdparm parameters
# for each of your disks, copy /etc/sysconfig/harddisks to
# /etc/sysconfig/harddiskhda (hdb, hdc...) and modify it.
# each disk which has no special parameters will use the defaults.



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