Bug 114054 - slow disk access under ServeRaid Card
Summary: slow disk access under ServeRaid Card
Keywords:
Status: CLOSED DUPLICATE of bug 104633
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel
Version: 3.0
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Tom Coughlan
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-01-21 23:17 UTC by Davey Goode
Modified: 2007-11-30 22:07 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-12-21 22:11:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Davey Goode 2004-01-21 23:17:28 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)

Description of problem:
Problem:
Slow disk file access, example copying 119 MB file takes more than 10 
seconds, hdparm only shows read access at 10 - 15 MB/sec, this is 
running on a raid 1 and a raid 1E array
Customer installed ES 3 

Installed:
ES 3, kernel-smp-2.4.21-4.0.1.EL IBM ServeRAID 6M Raid controller and 
4 x 2.8 Ghz processors


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Boot with RedHat Kernel
2. run hdparm
3.
    

Additional info:

Comment 1 Tom Coughlan 2004-02-12 22:30:42 UTC
This looks like a duplicate of BZ 104633.

Try Doug's test RPMs referenced in that bug. If that solves the
problem, please mark this as a dup. 

Comment 2 Doug Ledford 2004-05-21 13:23:25 UTC
Switching state to NEEDINFO.  If this problem still exists with
current kernels, then we need to know that.  Otherwise, the assumption
will be that the 15.EL kernels have solved this issue for you.

Comment 3 Tom Coughlan 2004-12-21 22:11:25 UTC
This has been NEEDINFO for 7 months. If this problem still occurs with
RHEL 4 U4, please re-open. 

Comment 4 Ernie Petrides 2004-12-21 23:05:20 UTC

*** This bug has been marked as a duplicate of 104633 ***


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