Bug 88770 - Software raid constantly out of sync
Summary: Software raid constantly out of sync
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 9
Hardware: athlon
OS: Linux
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2003-04-13 20:41 UTC by Zenon Panoussis
Modified: 2007-04-18 16:53 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2004-09-30 15:40:47 UTC

Attachments (Terms of Use)

Description Zenon Panoussis 2003-04-13 20:41:49 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225

Description of problem:

I run Phoebe (8.0.93 and 8.0.94) on an athlon with three RAID1 partitions across
two drives. Everything run smoothly.

I upgraded that installation to Shrike a week ago. Ever since, my drives have
been crunching for long streches and the system log is full of messages like 
Apr 13 21:18:41 pig kernel: raid1: raid set md2 not clean; reconstructing mirrors
This happened invariably after heavy write activity, like massive copying of
data, but sometimes also after moderate writing.

A rumour in IRC-land has it that kernel-2.4.20-8 can't manage the combination of
ext3 and software raid. I was not able to find any official RH confirmation, but
downgraded to kernel-2.4.18-14.athlon anyway. 

The crunching is gone. The error messages are gone. Everything works smoothly
again. Heavy copying has no abnormal side-effects whatsoever. I can only draw
the conclusion that the problem was not in my hardware or configuration and that
the rumour is probably correct.

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

How reproducible:
Didn't try (fear loss of data)

Comment 1 Bugzilla owner 2004-09-30 15:40:47 UTC
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/

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