--nextPart12565624.rhC4FBC7UD
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
On Thu, 20 Mar 2008, Stef Walter wrote:
> Don't duplicate the RAID amoeba style if you boot with a drive
> present that was detached from a RAID. This can happen if you manage
> to get past the above panic problem. You'll end up with two devices
> like ar0 and ar1. This can be a major mess if ar1 was already
> contained active file systems.
I have seen this bug in other ATA RAID implementations (VIA & Promise)=20
too. From what I can tell this part of your patch is general to all ATA=20
RAID arrays, right?
I can be bad even with just ar0 - you can end up with ar0 & ar1 after a=20
boot where ar0 is stale, it's awesome fun to debug :(
=2D-=20
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
--nextPart12565624.rhC4FBC7UD
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)
iD8DBQBH5D+15ZPcIHs/zowRAkysAKCDdwSxI3WSSOqY8FHpNmiqDQnXPQCeML30
O6V96hMxXzcGm9tW/TrU4WE=
=XTc5
-----END PGP SIGNATURE-----
--nextPart12565624.rhC4FBC7UD--