Bug 127751 - raid1 mirrors always delay resync when drives readded
Summary: raid1 mirrors always delay resync when drives readded
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel   
(Show other bugs)
Version: 2
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2004-07-13 13:14 UTC by Hrunting Johnson
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version: 2.6.7-1.494.2.2
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-17 20:40:38 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Hrunting Johnson 2004-07-13 13:14:54 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7)
Gecko/20040707 Firefox/0.9.2

Description of problem:
If you have a raid1 mirror that fails, you can remove the drive and
replace it, but when you go to add that drive back, it always goes in
with a delayed resync (it will wait until the next reboot). 
Furthermore, if you have other arrays that also use that drive and you
try to sync them (raid1 or otherwise), they too will be delayed
because of the raid1 array and if you reboot the system, you can then
get fs corruption because that delayed status isn't properly handled.

This is fixed in 2.6.8-rc1 by two patches from Neil Brown:
  o Fix raid1 read_balancing code
  o md: Fix up handling for read error in raid1

If these could make their way into an errata release sooner rather
than later, it would save a lot of grief working with RAID arrays.

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

How reproducible:

Steps to Reproduce:
1. setup raid1
2. hard-fail out a drive
3. try to readd drive

Actual Results:  Drive goes in with a delayed resync

Expected Results:  Drive beings resyncing immediately

Additional info:

Comment 1 Hrunting Johnson 2004-09-17 20:40:38 UTC
This was fixed in subsequent erratas which contained patches from Neil

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