From owner-freebsd-questions@FreeBSD.ORG Tue May 26 18:16:14 2009 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 0B5901065673 for ; Tue, 26 May 2009 18:16:14 +0000 (UTC) (envelope-from Ggatten@waddell.com) Received: from mailhost0.waddell.com (mailhost0.waddell.com [12.154.38.61]) by mx1.freebsd.org (Postfix) with ESMTP id C6F1F8FC1F for ; Tue, 26 May 2009 18:16:13 +0000 (UTC) (envelope-from Ggatten@waddell.com) Received: from mailhost2.waddell.com (mailhost2.waddell.com [10.1.10.30]) by mailhost0.waddell.com (8.13.8/8.13.8) with ESMTP id n4QIFg4Z026753; Tue, 26 May 2009 13:15:57 -0500 (CDT) (envelope-from Ggatten@waddell.com) Received: from mailhost2.waddell.com (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 28DEFB594C; Tue, 26 May 2009 13:15:42 -0500 (CDT) Received: from wadpexf0.waddell.com (wadpexf0.waddell.com [192.168.204.24]) by mailhost2.waddell.com (Postfix) with ESMTP id 1127CB592C; Tue, 26 May 2009 13:15:42 -0500 (CDT) Received: from WADPEXV0.waddell.com ([192.168.204.25]) by wadpexf0.waddell.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 26 May 2009 13:15:41 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 26 May 2009 13:15:41 -0500 Message-ID: <70C0964126D66F458E688618E1CD008A0793ED91@WADPEXV0.waddell.com> In-Reply-To: <200905261238.52979.kirk@strauser.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: FreeBSD & Software RAID Thread-Index: AcneKPKsWyIpFE0wQ0SMXzT6/UCZ5AABP0qA References: <4A1AA3DC.5020300@network-i.net> <200905261238.52979.kirk@strauser.com> From: "Gary Gatten" To: "Kirk Strauser" , X-OriginalArrivalTime: 26 May 2009 18:15:41.0801 (UTC) FILETIME=[FAB7BD90:01C9DE2D] Cc: Subject: RE: FreeBSD & Software RAID 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, 26 May 2009 18:16:14 -0000 Why avoid ZFS on x86? -----Original Message----- From: owner-freebsd-questions@freebsd.org [mailto:owner-freebsd-questions@freebsd.org] On Behalf Of Kirk Strauser Sent: Tuesday, May 26, 2009 12:39 PM To: freebsd-questions@freebsd.org Subject: Re: FreeBSD & Software RAID On Monday 25 May 2009 08:57:48 am Howard Jones wrote: > I'm was half-considering switching to ZFS, but the most positive thing I > could find written about that (as implemented on FreeBSD) is that it > "doesn't crash that much", so perhaps not. That was from a while ago > though. Wojciech hates it for some reason, but I wouldn't let that deter you. I'm=20 using ZFS on several production machines now and it's been beautifully solid=20 the whole time. It has several huge advantages over UFS: - Filesystem sizes are dynamic. They all grow and shrink inside the same=20 pool, so you don't have to worry about making one too large or too small. - You can sort of think of a ZFS filesystem as a directory with a set of=20 configurable, inheritable attributes. Set your /usr/ports to use compression,=20 and tell /home to keep two copies of everything for safety's sake. - Snapshots aren't painful. It's been 100% reliable on every amd64 machine I've put it on (but avoid it on=20 x86!). 7-STABLE hasn't required any tuning since February or so. UFS and gstripe/gmirror/graid* are good, but ZFS has spoiled me and I won't be=20 going back. --=20 Kirk Strauser _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
"This email is intended to be reviewed by only the intended recipient and may contain information that is privileged and/or confidential. If you are not the intended recipient, you are hereby notified that any review, use, dissemination, disclosure or copying of this email and its attachments, if any, is strictly prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system."