Date: Tue, 27 Jun 2006 00:51:56 +0200 From: "M.Hirsch" <M.Hirsch@gmx.de> To: "M.Hirsch" <M.Hirsch@hirsch.it> Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.x CVSUP today crashes with zero load ... Message-ID: <44A0650C.7020806@gmx.de> In-Reply-To: <44A06233.1090704@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>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44A0650C.7020806>