From owner-freebsd-stable@FreeBSD.ORG  Mon Jun 26 22:52:01 2006
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: 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 247C116A403
	for <freebsd-stable@freebsd.org>; Mon, 26 Jun 2006 22:52:01 +0000 (UTC)
	(envelope-from M.Hirsch@gmx.de)
Received: from mail.gmx.net (mail.gmx.de [213.165.64.21])
	by mx1.FreeBSD.org (Postfix) with SMTP id 4D9B343D67
	for <freebsd-stable@freebsd.org>; Mon, 26 Jun 2006 22:51:59 +0000 (GMT)
	(envelope-from M.Hirsch@gmx.de)
Received: (qmail invoked by alias); 26 Jun 2006 22:51:59 -0000
Received: from HSI-KBW-085-216-025-126.hsi.kabelbw.de (EHLO [192.168.101.121])
	[85.216.25.126]
	by mail.gmx.net (mp029) with SMTP; 27 Jun 2006 00:51:59 +0200
X-Authenticated: #820862
Message-ID: <44A0650C.7020806@gmx.de>
Date: Tue, 27 Jun 2006 00:51:56 +0200
From: "M.Hirsch" <M.Hirsch@gmx.de>
User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716)
X-Accept-Language: de-DE, de, en-us, en
MIME-Version: 1.0
To: "M.Hirsch" <M.Hirsch@hirsch.it>
References: <E1FuYsL-000HT3-H2@dilbert.firstcallgroup.co.uk>	<20060626100949.G24406@fledge.watson.org>	<20060626081029.L1114@ganymede.hub.org>	<20060626140333.M38418@fledge.watson.org>	<20060626235355.Q95667@atlantis.atlantis.dp.ua>	<44A04FD2.1030001@hirsch.it>	<20060627011512.N95667@atlantis.atlantis.dp.ua>
	<44A06233.1090704@hirsch.it>
In-Reply-To: <44A06233.1090704@hirsch.it>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: freebsd-stable@freebsd.org
Subject: Re: FreeBSD 6.x CVSUP today crashes with zero load ...
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
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: Mon, 26 Jun 2006 22:52:01 -0000


> Ok...
> Does the standard fs, UFS2, do "extra sanity checks", then?
>
Sorry, replying to myself...
No, this does not matter.
If the OS thinks the data is ok, UFS will write OK data...

So, let me rephrase this:
How can I make sure there is no broken hardware in my cluster?
I am not looking for workarounds, like ECC. I want the box to break 
immediately once any single component goes wrong...