> > You can apply the 2.2.6 patches to 2.2.10. But it is not working
> > correctly. Normal operation is ok, but if a raid comes out of sync and
> > need a resync (like when you reboot without a proper shutdown), this
> > would fail.
This doesn't in fact have anything to do with RAID0, and anyway, the one
liner patch has been posted to the list...
> I will take a backup before proceeding, but I would also like to get
> concensus from linux-raid participants and particularly Ingo...
I think it's not quite 'production' but that may be because of generic
bugs in linux-2.2.10 or in the raid code, which IMHO is ALMOST but not
quite production quality. I run raid0 against 2.2.9, and the system is
still running since I first booted. However, I have gotten two oopses
accessing the RAID0 which resulted in:
1) the accessing process crashed or
2) the accessing process hung in 'D' state
That being said, I have HEAVILY pounded the volume for a month, and this
is the sum total of my problems. The performance is great, but not
perfectly stable. For my purposes, I can live with it until the powers
that be stomp the last critters out.
N.B. There is a supposed lingering bug in the vanilla 2.2.10 kernel that
hasn't been tracked down yet w.r.t filesystem corruption, or invalid block
accesses, so that could be the root of all evil here, but at worst adds to
the problems...
David
--
/==============================\
| David Mansfield |
| [EMAIL PROTECTED] |
\==============================/
