From owner-freebsd-stable@FreeBSD.ORG  Thu Mar 31 19:11:16 2005
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3E46616A4CE
	for <freebsd-stable@freebsd.org>;
	Thu, 31 Mar 2005 19:11:16 +0000 (GMT)
Received: from mailserver.sandvine.com (sandvine.com [199.243.201.138])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A848343D3F
	for <freebsd-stable@freebsd.org>;
	Thu, 31 Mar 2005 19:11:15 +0000 (GMT)
	(envelope-from don@SANDVINE.com)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 31 Mar 2005 14:11:14 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Message-ID: <2BCEB9A37A4D354AA276774EE13FB8C23A6903@mailserver.sandvine.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Adaptec 3210S, 4.9-STABLE, corruption when disk fails
Thread-Index: AcUePN4jCNifqq9+QfaKvb5a3QmG4wANR28ABezPRgA=
From: "Don Bowman" <don@SANDVINE.com>
To: "Don Bowman" <don@SANDVINE.com>,
	"Uwe Doering" <gemini@geminix.org>
cc: freebsd-stable@freebsd.org
Subject: RE: Adaptec 3210S, 4.9-STABLE, corruption when disk fails
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2005 19:11:16 -0000

From: owner-freebsd-stable@freebsd.org=20
> From: Uwe Doering [mailto:gemini@geminix.org]  ...
> > >=20
> > > Did you merge 1.3.2.3 as well?  This actually should have
> > been one MFC
>=20
> Yes, merged from RELENG_4.
>=20
> I will post later if this happens again, but it will be quite
> a long time. The machine has 7 drives in it, there are only
> 3 ones left old enough they might fail before I take it out
> of service (it originally had 7 1999-era IBM drives, now
> it has 4 2004-era seagate drives and 3 of the old IBM's.
> The drives have been in continuous service, so they've lead
> a pretty good life!)
>=20
> Thanks for the suggestion on the cam timeout, I've set that
> value.

Another drive failed and the same thing happened.
After the failure, the raid worked in degrade mode just
fine, but many files had been corrupted during the failure.

So I would suggest that this merge did not help, and the
cam timeout did not help either.

This is very frustrating, again I rebuild my postgresql install
from backup :(

--don