From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id A5B5B138350 for ; Mon, 4 May 2020 01:33:39 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 88CCFE09CD; Mon, 4 May 2020 01:33:32 +0000 (UTC) Received: from mail-40135.protonmail.ch (mail-40135.protonmail.ch [185.70.40.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 1C705E0976 for ; Mon, 4 May 2020 01:33:29 +0000 (UTC) Date: Mon, 04 May 2020 01:33:15 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail; t=1588556007; bh=I/xDHqGV6xlYKxedGXQGk/GEWUeYE4+70HuOBgs1uyg=; h=Date:To:From:Reply-To:Subject:In-Reply-To:References:From; b=a+wk7CptXvkroPNcTeARu1F75Su3WQJa6b89wDB5cCJb37TiefxpJKuyoIsrpdAm5 E7NZCnvjTQiLRKUT00iAWLqj1ckXP7NNVCEMftTkt/8FrtW4fUelRyqVUlArfABIzA Uniw+82XEwpIRQKr3eKBdM/jkGQAK/IsrOf6S4O8= To: "gentoo-user@lists.gentoo.org" From: Caveman Al Toraboran Subject: Re: [gentoo-user] which linux RAID setup to choose? Message-ID: In-Reply-To: References: <2251dac1-92cd-7c3b-97ea-6a061fe01eb0@users.sourceforge.net> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mail.protonmail.ch X-Archives-Salt: 46080a5a-3943-4d29-95b5-42d938c9aa91 X-Archives-Hash: fe131067f4c106ccfe13adc899244659 On Monday, May 4, 2020 3:19 AM, antlists wrote: > On 03/05/2020 22:46, Caveman Al Toraboran wrote: > > > On Sunday, May 3, 2020 6:27 PM, Jack ostroffjh@users.sourceforge.net wr= ote: > > curious. how do people look at --layout=3Dn2 in the > > storage industry? e.g. do they ignore the > > optimistic case where 2 disk failures can be > > recovered, and only assume that it protects for 1 > > disk failure? > > You CANNOT afford to be optimistic ... Murphy's law says you will lose > the wrong second disk. so i guess your answer is: "yes, the industry ignores the existence of optimistic cases". if that's true, then the industry is wrong, must learn the following: 1. don't bet that your data's survival is lingering on luck (you agree with this i know). 2. don't ignore statistics that reveal the fact that lucky cases exist. (1) and (2) are not mutually exclusive, and murfphy's law would suggest to not ignore (2). becuase, if you ignore (2), you'll end up adopting a 5-disk RAID10 instead of the superior 6-disk RAID10 and end up being less lucky in practice. don't rely on lucks, but why deny good luck to come to you when it might? --- two different things. > > i see why gambling is not worth it here, but at > > the same time, i see no reason to ignore reality > > (that a 2 disk failure can be saved). > > Don't ignore that some 2-disk failures CAN'T be saved ... yeah, i'm not. i'm just not ignoring that 2-disk failure might get saved. you know... it's better to have a lil window where some good luck may chime in than banning good luck. > Don't forget, if you have a spare disk, the repair window is the length > of time it takes to fail-over ... yup. just trying to not rely on good luck that a spare is available. e.g. considering for the case that no space is there. > > this site [2] says that 76% of seagate disks fail > > per year (:D). and since disks fail independent > > of each other mostly, then, the probabilty of > > having 2 disks fail in a year is: > > 76% seems incredibly high. And no, disks do not fail independently of > each other. If you buy a bunch of identical disks, at the same time, and > stick them all in the same raid array, the chances of them all wearing > out at the same time are rather higher than random chance would suggest. i know. i had this as a note, but then removed it. anyway, some nitpics: 1. dependence !=3D correlation. you mean correlation, not dependence. disk failure is correlated if they are baught together, but other disks don't cause the failure (unless from things like heat from other disks, or repair stress because of other disk failing). 2. i followed the extreme case where a person got his disks purchased at a random time, so that he was maximally lucky in that his disks didn't synchronize. why? (i) offers a better pessimistic result. now we know that this probability is actually lower than reality, which means that we know that the 3.5k bucks is actually even lower. this should scare us more (hence us relying on less luck). (ii) makes calculation easier.