From owner-freebsd-current@FreeBSD.ORG Fri Nov 21 20:14:17 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 42B6516A4CE for ; Fri, 21 Nov 2003 20:14:17 -0800 (PST) Received: from smtp.noos.fr (nan-smtp-14.noos.net [212.198.2.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 952EB43FBF for ; Fri, 21 Nov 2003 20:14:13 -0800 (PST) (envelope-from boyd@insultant.net) Received: (qmail 1834 invoked by uid 0); 22 Nov 2003 04:14:12 -0000 Received: from unknown (HELO coma) ([81.64.132.185]) (envelope-sender ) by 212.198.2.122 (qmail-ldap-1.03) with SMTP for ; 22 Nov 2003 04:14:12 -0000 Message-ID: <0a5901c3b0ad$cfb85220$b9844051@insultant.net> From: "boyd, rounin" To: "William Josephson" , References: <2147483647.1069240727@[192.168.42.6]><20031120095214.GA68334@server.vk2pj.dyndns.org><050d01c3afa8$1dfb97a0$b9844051@insultant.net><156539179.20031121001033@andric.com><061f01c3afbd$4692a040$b9844051@insultant.net><3FBD788A.4070809@mindspring.com><20031121025952.GA85809@saboteur.dek.spc.org> <20031121202713.GA4060@mero.morphisms.net> Date: Sat, 22 Nov 2003 05:05:05 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: Re: Unfortunate dynamic linking for everything X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Nov 2003 04:14:17 -0000 From: "William Josephson" > People at Berkeley (and elsewhere) have done user studies to try to > quantify this sort of thing. It is pretty clear that with modern > hardware, most failures are due to human error. That's not to say > that hardware and software faults aren't real problems, too, but it > is more common that someone, say, pulls the wrong drive from the > RAID-5 array, resulting in an unnecessary double disk fault. that means your raid 5 is bust. i've seen raid 5 fail and it just picks another disk in the 'free' pool like nothing has happened. a study? it's bleeding obvious.