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 7F5B013933E for ; Sun, 4 Jul 2021 10:56:19 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BDAF6E0829; Sun, 4 Jul 2021 10:56:11 +0000 (UTC) Received: from mout01.posteo.de (mout01.posteo.de [185.67.36.65]) (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 158C3E081B for ; Sun, 4 Jul 2021 10:56:09 +0000 (UTC) Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id 60D4F240026 for ; Sun, 4 Jul 2021 12:56:07 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1625396167; bh=74LuAThEIDeZ/P+StXsU2NsJJMjw9cnBZCpTAR/j3Hw=; h=From:To:Cc:Subject:Date:From; b=X6CJdxSd9G3+mJ20GE4wDvx5UNF3EFqTJedG53+rkiZ+9oMxtbRYGvf+hQV3Lspej 27SkYoa3S8OOohRkFlMfaUUBrXCQnRwjHfGx9MgWsYe7p3A/xEL7do4iazuUaUzFi7 kJ1kI6vowgmK5Oomyq+Bwxrcv045Uqp72xs/nOYgBzL+R8JvzR9ZVN3wSVEn1YAZDv kiwXi7pDghLcVaMYE+jZpC8WC9tGl5PNWn8CAg2QPSIuqZ1y0q6Z/S9OI2NTx/cvIz EDsSrNSbFDhOHIIWTervNqaiqdwBcHlDHg09VZUfE3Rp64XVGtzYZpnWPP9n9f+VR9 2koD5oQAzvUvw== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4GHm2Z3lJ0z6tmG; Sun, 4 Jul 2021 12:56:06 +0200 (CEST) From: Robert David To: gentoo-user@lists.gentoo.org Cc: antlists Subject: Re: [gentoo-user] [OT] Using an odd number of drives in ZFS RaidZ Date: Sun, 04 Jul 2021 10:56:05 +0000 Message-ID: <8267067.vXUDI8C0e8@robert-notebook> In-Reply-To: <5d972c64-3803-9e14-9302-3cb8ca4eb09e@youngman.org.uk> References: <7622209.dfAi7KttbR@robert-notebook> <5d972c64-3803-9e14-9302-3cb8ca4eb09e@youngman.org.uk> 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-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Archives-Salt: ce991b78-d531-4cef-a038-23d54f29af2e X-Archives-Hash: 85f35179bca333f02cede424acc083ff On Thursday, July 1, 2021 5:01:25 PM CEST antlists wrote: > On 01/07/2021 14:47, Robert David wrote: > > Hi Frank, > > > > > > > > In any of my data arrays I have long time migrated off the RAIDZ to the > > MIRROR or RAID10. You will find finally that the RAIDZ is slow and not > > very flexible. Only think you gain is the extra space in constrained > > array spaces. For RAID10 it is much easier to raise the size, just > > resilvering to new bigger disks, removing old and expanding. The > > resilvering speed is magnitude faster. > > > > And anyway much easier to recover > > in cases of failure. > > ARE YOU SURE??? > > The standard mirror does not cope with corruption very well. Lose a disk > and resilvering is fast. Corrupt the data, and you'll be tearing your > hair out why things go wrong randomly, with no automated way, even once > you've realised what's happened, to recover your data other than a > restore from backup. Yes I'm sure. What I meant easier is that the pool is much easier to handle and recover. For RAIDZ1 the thing you mention for MIRROR is the same, only it is multiplied with the amount of disks. So if 1 disk fail and you resilver, then all the remaining disks spinning to populate the spare. If any of them fails, then you are screwed. RAIDZ2 is better in this space and in case of 4 disks it is better when it comes to resiliency (for 10 disks it may not be true), but you lose the flexibility. Also time to resilver under RAIDZ is much slower, which means longer time under unprotected pool. It is always needed to decide what workload you are serving and how precious the data are. For data like movies RAIDZ1 is enough I think. Also it is good to check the SMART data time to time to see the amount of error corrections (some are ok, but highly rising no). Solaris has FMA for this to kick in spare. Under home environment it is fine to check it time to time and consider new disk before the old one completely dies. This reminds me I need to buy new disk to my home NAS :) (because of the rising corrections). And finally, always do backups for the data you are about to save. I got raspberry pi with attached USB JBOD with two disks serving as backup station. It is not fast to be a real NAS, but to do send/receive of incremental snapshots it is enough. I automaticly sync there the datasets that are worth not to lose (photos, documents, etc), many times these datasets are also the ones that are not such big. Ideally put this backup station to some remote location (or at least different room). Robert. > > > If you really need the additional space, consider adding second jbod > > with another disks. > > That'd be my approach - migrate a load of stuff off onto another disk > elsewhere, but that's not what the OP wants to do. > > > Robert. > > Cheers, > Wol