From owner-freebsd-questions@FreeBSD.ORG Tue Jul 8 20:36:33 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6FE6C1065678 for ; Tue, 8 Jul 2008 20:36:33 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id EAF4E8FC1C; Tue, 8 Jul 2008 20:36:31 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <4873CFD4.3060004@FreeBSD.org> Date: Tue, 08 Jul 2008 22:36:36 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Wojciech Puchar References: <1a5a68400806080604ped08ce8p120fc21107e7de81@mail.gmail.com> <4F9C9299A10AE74E89EA580D14AA10A61A193E@royal64.emp.zapto.org> <20080612132527.K5722@wojtek.tensor.gdynia.pl> <200807060222.40004.lists@jnielsen.net> <20080706085537.J3537@wojtek.tensor.gdynia.pl> In-Reply-To: <20080706085537.J3537@wojtek.tensor.gdynia.pl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: John Nielsen , freebsd-questions@freebsd.org Subject: Re: FreeBSD + ZFS on a production server? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jul 2008 20:36:33 -0000 Wojciech Puchar wrote: >> >> ZFS on FreeBSD is GEOM-ified. While I believe what Wojciech said about >> needing a full disk is correct under Solaris, it's not the case in > > i never said it requires full disk. but it will work very slow sharing a > disk with non-ZFS things. Well, of course if you are loading your disk with too many seeks it will be slow. This has nothing to do with ZFS. >>> to say more: zfs set copies could be usable to selectively mirror given >>> data while not mirroring other (using unprotected storage for ZFS). >>> but it's broken. it writes N copies under write, but don't remake >>> copies in case of failure! > > which make it almost unusable. in case of any failure you have to copy > and delete every file to make it actually repaired. Eh? It happens automatically. Kris