Bug 136485 - md/raid1 read retry does not work
md/raid1 read retry does not work
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Doug Ledford
Brian Brock
Depends On:
Blocks: 135876
  Show dependency treegraph
Reported: 2004-10-20 09:52 EDT by Paul Clements
Modified: 2007-11-30 17:07 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-12-13 07:36:38 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
raid1 bio clone on read error (930 bytes, patch)
2004-10-20 09:54 EDT, Paul Clements
no flags Details | Diff

  None (edit)
Description Paul Clements 2004-10-20 09:52:10 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040116

Description of problem:
Currently, the mainline kernel (and therefore 2.6.8, which the RHEL 4
kernel is based on) do not correctly perform raid1 read retry. I
posted a patch to linux-raid on Sept 15 to fix this
Neil Brown has confirmed the problem and just yesterday posted an
expanded patch (including the fix for raid10 also):



(My version of the patch, which applies to the RHEL4 kernel, and which
is basically identical to Neil's patch, is attached).

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

How reproducible:

Steps to Reproduce:
1. create md/raid1 array
2. fail the second drive while doing reads to the array

Actual Results:  read retry will be attempted but will always fail --
additionally the driver is unable to recover from the situation

Expected Results:  read retry should succeed

Additional info:
Comment 1 Paul Clements 2004-10-20 09:54:59 EDT
Created attachment 105507 [details]
raid1 bio clone on read error
Comment 3 Dave Jones 2004-11-04 17:58:31 EST
fixed in cvs
Comment 4 Jay Turner 2004-12-13 07:36:38 EST
Patch is indeed present in 2.6.9-1.903_EL.  Closing out.

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