From owner-freebsd-fs@FreeBSD.ORG Wed Jul 25 09:23:49 2007 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DEB1116A4A1 for ; Wed, 25 Jul 2007 09:23:49 +0000 (UTC) (envelope-from M.S.Powell@salford.ac.uk) Received: from abbe.salford.ac.uk (abbe.salford.ac.uk [146.87.0.10]) by mx1.freebsd.org (Postfix) with SMTP id 587DF13C4B5 for ; Wed, 25 Jul 2007 09:23:49 +0000 (UTC) (envelope-from M.S.Powell@salford.ac.uk) Received: (qmail 65884 invoked by uid 98); 25 Jul 2007 10:23:46 +0100 Received: from 146.87.255.121 by abbe.salford.ac.uk (envelope-from , uid 401) with qmail-scanner-2.01 (clamdscan: 0.90/3762. spamassassin: 3.1.8. Clear:RC:1(146.87.255.121):. Processed in 0.045947 secs); 25 Jul 2007 09:23:46 -0000 Received: from rust.salford.ac.uk (HELO rust.salford.ac.uk) (146.87.255.121) by abbe.salford.ac.uk (qpsmtpd/0.3x.614) with SMTP; Wed, 25 Jul 2007 10:23:46 +0100 Received: (qmail 58773 invoked by uid 1002); 25 Jul 2007 09:23:44 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 25 Jul 2007 09:23:44 -0000 Date: Wed, 25 Jul 2007 10:23:44 +0100 (BST) From: "Mark Powell" To: Pawel Jakub Dawidek In-Reply-To: <20070721065204.GA2044@garage.freebsd.pl> Message-ID: <20070725095723.T57231@rust.salford.ac.uk> References: <20070719102302.R1534@rust.salford.ac.uk> <20070719135510.GE1194@garage.freebsd.pl> <20070719181313.G4923@rust.salford.ac.uk> <20070721065204.GA2044@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@freebsd.org Subject: Re: ZfS & GEOM with many odd drive sizes X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jul 2007 09:23:50 -0000 On Sat, 21 Jul 2007, Pawel Jakub Dawidek wrote: Thanks for your reply. > Be sure to turn off debugging, ie. remove WITNESS, INVARIANTS and > INVARIANT_SUPPORT options from your kernel configuration. > Other than that, ZFS may just be more CPU hungry... I have. Makes little difference. Think the idea of using an Athlon XP for ZFS has turned out to be a bridge too far. The new 65nm Athlon 64 x2 are very cheap now. Time for an upgrade. You said that replacing one device with another is not a problem. Just to be clear on this as it's a key factor in me going with this solution. I hope this isn't too naive a question, but the answer will be here for others :) Suppose instead of gconcat I used gstripe on the 250+200 combinations: i.e. (slice 1 on all drives is reserved for ufs gmirror of /boot and block device swap) gs0 ad0s2 ad1s2 gs1 ad2s2 ad3s2 gs2 ad4s2 ad5s2 I use these gstripes and the single 400GB drive to construct the zpool: zpool create tank raidz /dev/mirror/gs0 /dev/mirror/gs1 /dev/mirror/gs2 ad6s2 If for example ad3 fails and thus gs1 fails, how is this replaced in the zpool? e.g. suppose I replace both ad2 and ad3 with a new 500GB drive as ad2. Is fixing this as simple as: zpool replace tank /dev/mirror/gs1 ad2s2 Many thanks. -- Mark Powell - UNIX System Administrator - The University of Salford Information Services Division, Clifford Whitworth Building, Salford University, Manchester, M5 4WT, UK. Tel: +44 161 295 4837 Fax: +44 161 295 5888 www.pgp.com for PGP key