From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wols Lists Subject: Re: Fault tolerance with badblocks Date: Tue, 9 May 2017 18:49:08 +0100 Message-ID: <59120114.6080702@youngman.org.uk> References: <03294ec0-2df0-8c1c-dd98-2e9e5efb6f4f@hale.ee> <590B3039.3060000@youngman.org.uk> <84184eb3-52c4-e7ad-cd5b-5021b5cf47ee@hale.ee> <590DC905.60207@youngman.org.uk> <87h90v8kt3.fsf@esperi.org.uk> <1533bba8-41cb-2c50-b28a-52786e463072@turmel.org> <87vapb6s9h.fsf@esperi.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-raid-owner@vger.kernel.org To: Chris Murphy Cc: Nix , Phil Turmel , "Ravi (Tom) Hale" , Linux-RAID List-Id: linux-raid.ids On 09/05/17 17:05, Chris Murphy wrote: >> Yes you have saved a sector sparing. Note that a consumer 3TB drive can >> > return, on average, one error every time it's read from end to end 3 times, >> > and still be considered "within spec" ie "not faulty" by the manufacturer. > All specs say "less than" which means it's a maximum permissible rate, > not an average. We have no idea what the minimum error rate is - we > being consumers. It's possible high volume users (e.g. Backblaze) have > data on this by now. > In other words, an error rate that high is "acceptable". And to design software that quite explicitly expects greater perfection than the hardware itself is guaranteed to provide is, in my humble opinion, downright negligent!!! I'm sorry, but like Linus, I take an *engineering* approach to this stuff, not a mathematical approach. In a mathematical world everything works perfectly. In an engineering world, things go wrong. You should always plan for the worst case. But to fail to plan for "the worst *acceptable* case" is just plain IDIOTIC. Cheers, Wol