From owner-freebsd-questions@freebsd.org Wed Apr 13 15:23:17 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C1C0CB0E51D for ; Wed, 13 Apr 2016 15:23:17 +0000 (UTC) (envelope-from freebsd-lists@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A2DAB106F for ; Wed, 13 Apr 2016 15:23:17 +0000 (UTC) (envelope-from freebsd-lists@gromit.dlib.vt.edu) Received: from pmather.lib.vt.edu (pmather.lib.vt.edu [128.173.126.193]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id BAB91643; Wed, 13 Apr 2016 11:15:50 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: ZFS with errors From: Paul Mather In-Reply-To: Date: Wed, 13 Apr 2016 11:15:50 -0400 Cc: luciano@vespaperitivo.it Content-Transfer-Encoding: quoted-printable Message-Id: <6DF8015A-9976-4DDE-BC9B-236F97470A36@gromit.dlib.vt.edu> References: To: freebsd-questions@freebsd.org X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Apr 2016 15:23:17 -0000 Luciano, > Date: Wed, 13 Apr 2016 16:22:51 +0200 > From: Luciano Mannucci > To: freebsd-questions@freebsd.org > Subject: Re: ZFS with errors > Message-ID: <3qlQxr34YhzRRqQ@baobab.bilink.it> > Content-Type: text/plain; charset=3Diso-8859-1 >=20 > On Wed, 13 Apr 2016 15:56:20 +0200 (CEST) > Trond Endrest?l wrote: >=20 >> There's no redundancy in this pool, making it hard for ZFS to=20 >> automatically repair your files. >>=20 >> Maybe you should destroy your pool and recreate it using a mirrored=20= >> configuration. Maybe, mirror disks 1 & 2, and disks 3 & 4, e.g. > They are of different sizes. I don't know if I can add redundancy > without loosing the bits that exeed the smallest one... > I'm a zfs newbie, just experimenting by now... :) >=20 > Thanks anyway, >=20 > Luciano. The only way you can add redundancy to the type of pool you have (i.e., = several drives concatenated together without any mirroring or raidz = redundancy) is to set the "copies=3D..." property on datasets for which = you want some redundancy: copies=3D1 | 2 | 3 Controls the number of copies of data stored for this dataset. = These copies are in addition to any redundancy provided by the pool, = for example, mirroring or RAID-Z. The copies are stored on = different disks, if possible. The space used by multiple copies is = charged to the associated file and dataset, changing the used property and counting against quotas and reservations. Changing this property only affects newly-written data. = Therefore, set this property at file system creation time by using the -o copies=3DN option. Note the "Changing this property only affects newly-written data" part, = though. You could also apply this selectively if you don't want to lose = too much pool space, e.g., to impart some redundancy to files in your = home directory but not to other areas where data loss can easily be = remedied or isn't as much of a problem (/usr/src; /usr/ports; /usr/obj; = etc.). Cheers, Paul.=