From owner-freebsd-fs@FreeBSD.ORG Sun Oct 26 19:04:20 2008 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 40AF01065670 for ; Sun, 26 Oct 2008 19:04:20 +0000 (UTC) (envelope-from rec@RCousins.com) Received: from colo7.rcousins.com (colo7.rcousins.com [72.20.110.131]) by mx1.freebsd.org (Postfix) with ESMTP id 318328FC0C for ; Sun, 26 Oct 2008 19:04:19 +0000 (UTC) (envelope-from rec@RCousins.com) Received: from [10.0.2.5] (m206-32.dsl.tsoft.com [198.144.206.32]) by colo7.rcousins.com (Postfix) with ESMTP id E6EA039DD86 for ; Sun, 26 Oct 2008 11:41:15 -0700 (PDT) Message-ID: <4904B998.1030107@RCousins.com> Date: Sun, 26 Oct 2008 11:40:24 -0700 From: Robert Cousins User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: ZFS extended attributes 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: Sun, 26 Oct 2008 19:04:20 -0000 I was trying to run a program over ZFS which runs under UFS. After some tracking, I found that the program was using extended file attributes under UFS2 and that these are not supported under ZFS. Is there a plan to support extended attributes under ZFS? From owner-freebsd-fs@FreeBSD.ORG Sun Oct 26 19:06:06 2008 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 CB25A106566C for ; Sun, 26 Oct 2008 19:06:06 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [76.96.62.80]) by mx1.freebsd.org (Postfix) with ESMTP id 772578FC1B for ; Sun, 26 Oct 2008 19:06:06 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA03.westchester.pa.mail.comcast.net ([76.96.62.27]) by QMTA08.westchester.pa.mail.comcast.net with comcast id XSfG1a00f0bG4ec58X5oxh; Sun, 26 Oct 2008 19:05:48 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA03.westchester.pa.mail.comcast.net with comcast id XX641a00G2P6wsM3PX65lv; Sun, 26 Oct 2008 19:06:05 +0000 X-Authority-Analysis: v=1.0 c=1 a=6I5d2MoRAAAA:8 a=QycZ5dHgAAAA:8 a=NGNjAlau4J909FJsHyAA:9 a=HnooKGEtXXF13Drs24E_DSrEUzEA:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id 59C61C9419; Sun, 26 Oct 2008 12:06:04 -0700 (PDT) Date: Sun, 26 Oct 2008 12:06:04 -0700 From: Jeremy Chadwick To: Robert Cousins Message-ID: <20081026190604.GA1748@icarus.home.lan> References: <4904B998.1030107@RCousins.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4904B998.1030107@RCousins.com> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS extended attributes 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: Sun, 26 Oct 2008 19:06:06 -0000 On Sun, Oct 26, 2008 at 11:40:24AM -0700, Robert Cousins wrote: > I was trying to run a program over ZFS which runs under UFS. After some > tracking, I found that the program was using extended file attributes > under UFS2 and that these are not supported under ZFS. > > Is there a plan to support extended attributes under ZFS? http://wiki.freebsd.org/ZFS See "extattr" in the table near the bottom. Talk to pjd@ if you're interested in helping. :-) -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Sun Oct 26 23:15:12 2008 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 28AE81065675 for ; Sun, 26 Oct 2008 23:15:12 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id D8CD68FC14 for ; Sun, 26 Oct 2008 23:15:11 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1KuEp5-0001ln-7I for freebsd-fs@freebsd.org; Sun, 26 Oct 2008 23:15:03 +0000 Received: from 200.41.broadband11.iol.cz ([90.178.41.200]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 26 Oct 2008 23:15:03 +0000 Received: from gamato by 200.41.broadband11.iol.cz with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 26 Oct 2008 23:15:03 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: martinko Date: Sun, 26 Oct 2008 23:45:09 +0100 Lines: 14 Message-ID: References: <6eb82e0808030743hc41c68bgd0c5121daba95d42@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 200.41.broadband11.iol.cz User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.17) Gecko/20081009 SeaMonkey/1.1.12 In-Reply-To: <6eb82e0808030743hc41c68bgd0c5121daba95d42@mail.gmail.com> Sender: news Subject: Re: journaling filesystem 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: Sun, 26 Oct 2008 23:15:12 -0000 Rong-en Fan wrote: > In NetBSD, they now have metadata journaling support, see > > http://www.netbsd.org/changes/#wapbl > > I'm not a fs guru, I just want to know what are the status of > BluFFS and UFS journaling support which were mentioned > in recent years. > > Thanks, > Rong-En Fan This is very interesting! I can imagine this would be the way for systems where ZFS is not an option but SU are reaching their limits. From owner-freebsd-fs@FreeBSD.ORG Mon Oct 27 11:07:12 2008 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 665D8106569E for ; Mon, 27 Oct 2008 11:07:12 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 537EE8FC13 for ; Mon, 27 Oct 2008 11:07:12 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id m9RB7CSi001934 for ; Mon, 27 Oct 2008 11:07:12 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id m9RB7B8G001930 for freebsd-fs@FreeBSD.org; Mon, 27 Oct 2008 11:07:11 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 27 Oct 2008 11:07:11 GMT Message-Id: <200810271107.m9RB7B8G001930@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-fs@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-fs@FreeBSD.org 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: Mon, 27 Oct 2008 11:07:12 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/128173 fs [ext2fs] ls gives "Input/output error" on mounted ext3 o kern/127420 fs [gjournal] [panic] Journal overflow on gmirrored gjour o kern/127213 fs [tmpfs] sendfile on tmpfs data corruption o kern/127029 fs [panic] mount(8): trying to mount a write protected zi o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file o kern/125536 fs [ext2fs] ext 2 mounts cleanly but fails on commands li o kern/125149 fs [nfs][panic] changing into .zfs dir from nfs client ca o kern/124621 fs [ext3] Cannot mount ext2fs partition o kern/122888 fs [zfs] zfs hang w/ prefetch on, zil off while running t o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386, o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha a kern/119868 fs [zfs] [patch] 7.0 kernel panic during boot with ZFS an o bin/118249 fs mv(1): moving a directory changes its mtime o kern/116170 fs [panic] Kernel panic when mounting /tmp o kern/114955 fs [cd9660] [patch] [request] support for mask,dirmask,ui o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o bin/114468 fs [patch] [request] add -d option to umount(8) to detach o bin/113838 fs [patch] [request] mount(8): add support for relative p o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/93942 fs [vfs] [patch] panic: ufs_dirbad: bad dir (patch from D 22 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Oct 27 13:43:46 2008 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 77A691065673 for ; Mon, 27 Oct 2008 13:43:46 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (unknown [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id E98758FC1B for ; Mon, 27 Oct 2008 13:43:45 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.3/8.14.3) with ESMTP id m9RDhfAH013869; Mon, 27 Oct 2008 14:43:43 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id m9RDhfNQ013868; Mon, 27 Oct 2008 14:43:41 +0100 (CET) (envelope-from olli) Date: Mon, 27 Oct 2008 14:43:41 +0100 (CET) Message-Id: <200810271343.m9RDhfNQ013868@lurza.secnetix.de> From: Oliver Fromme To: freebsd-fs@FreeBSD.ORG, grafan@gmail.com, gamato@users.sf.net In-Reply-To: X-Newsgroups: list.freebsd-fs User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.4-PRERELEASE-20080904 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Mon, 27 Oct 2008 14:43:44 +0100 (CET) Cc: Subject: Re: journaling filesystem X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-fs@FreeBSD.ORG, grafan@gmail.com, gamato@users.sf.net List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2008 13:43:46 -0000 martinko wrote: > Rong-en Fan wrote: > > In NetBSD, they now have metadata journaling support, see > > > > http://www.netbsd.org/changes/#wapbl > > > > I'm not a fs guru, I just want to know what are the status of > > BluFFS and UFS journaling support which were mentioned > > in recent years. > > This is very interesting! I can imagine this would be the way for > systems where ZFS is not an option but SU are reaching their limits. Have you had a look at gjournal(8)? Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "C++ is to C as Lung Cancer is to Lung." -- Thomas Funke From owner-freebsd-fs@FreeBSD.ORG Mon Oct 27 15:09:45 2008 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 40374106567F for ; Mon, 27 Oct 2008 15:09:45 +0000 (UTC) (envelope-from grafan@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.155]) by mx1.freebsd.org (Postfix) with ESMTP id BCB8A8FC12 for ; Mon, 27 Oct 2008 15:09:44 +0000 (UTC) (envelope-from grafan@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so1851936fgb.35 for ; Mon, 27 Oct 2008 08:09:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=Dcenv5kxOxtDrruwlC69gRIoPUtDyspTLuM2TyKCwfg=; b=XXkwEKN6Uvpl4RCuLm48iEjLFYIAHuM4mRjr2kqEGTLwf7PSkwNNiSY1YUr25whIGQ FMWv5eNITtfqtW4GMIrxvaMpd6reNZgcLGRreHN98z7BVcRHtgWf9yvrK6+S/IWcxvUh YpoG0dSFyO/Yr8qc9C7zx51eKogs8St8ViT74= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=DDc5q3VZEdtU1sKVDkoayEnuNkovAKc6Ywts2bCYgs6jwZVwJoFVvfQ/XKkNVX0Nl7 Y/IoOFVvprtT/XKG6yxAsNo+MJBhl64QoHw1nizuPhmYSP/klDyFGzcTAmoTwxScDASU qK1PdVbsCCiPpQIHJWaMJQ4s4cK7b6p6ztem4= Received: by 10.187.202.7 with SMTP id e7mr538212faq.33.1225118714797; Mon, 27 Oct 2008 07:45:14 -0700 (PDT) Received: by 10.187.248.6 with HTTP; Mon, 27 Oct 2008 07:45:14 -0700 (PDT) Message-ID: <6eb82e0810270745w4444b735sca369c0b1d724b48@mail.gmail.com> Date: Mon, 27 Oct 2008 22:45:14 +0800 From: "Rong-en Fan" To: freebsd-fs@freebsd.org, grafan@gmail.com, gamato@users.sf.net In-Reply-To: <200810271343.m9RDhfNQ013868@lurza.secnetix.de> MIME-Version: 1.0 References: <200810271343.m9RDhfNQ013868@lurza.secnetix.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: journaling filesystem 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: Mon, 27 Oct 2008 15:09:45 -0000 On Mon, Oct 27, 2008 at 9:43 PM, Oliver Fromme wrote: > martinko wrote: > > Rong-en Fan wrote: > > > In NetBSD, they now have metadata journaling support, see > > > > > > http://www.netbsd.org/changes/#wapbl > > > > > > I'm not a fs guru, I just want to know what are the status of > > > BluFFS and UFS journaling support which were mentioned > > > in recent years. > > > > This is very interesting! I can imagine this would be the way for > > systems where ZFS is not an option but SU are reaching their limits. > > Have you had a look at gjournal(8)? Actually, gjournal has the problem with fast write load. It panics if the journal overflows... I was told by pjd@ that if I have been played with the sysctls and it still overflows, then there is nothing we can do... Regards, Rong-En Fan From owner-freebsd-fs@FreeBSD.ORG Mon Oct 27 16:00:31 2008 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 ECD251065699 for ; Mon, 27 Oct 2008 16:00:31 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [91.103.162.4]) by mx1.freebsd.org (Postfix) with ESMTP id 6FCCB8FC2D for ; Mon, 27 Oct 2008 16:00:30 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from localhost (localhost.codelab.cz [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 4DCB419E027; Mon, 27 Oct 2008 17:00:29 +0100 (CET) Received: from [192.168.1.2] (r5bb235.net.upc.cz [86.49.61.235]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 8EF5219E023; Mon, 27 Oct 2008 17:00:26 +0100 (CET) Message-ID: <4905E5BD.2020809@quip.cz> Date: Mon, 27 Oct 2008 17:01:01 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: cz, cs, en, en-us MIME-Version: 1.0 To: freebsd-fs@FreeBSD.ORG, grafan@gmail.com, gamato@users.sf.net References: <200810271343.m9RDhfNQ013868@lurza.secnetix.de> In-Reply-To: <200810271343.m9RDhfNQ013868@lurza.secnetix.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: journaling filesystem 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: Mon, 27 Oct 2008 16:00:32 -0000 Oliver Fromme wrote: > martinko wrote: > > Rong-en Fan wrote: > > > In NetBSD, they now have metadata journaling support, see > > > > > > http://www.netbsd.org/changes/#wapbl > > > > > > I'm not a fs guru, I just want to know what are the status of > > > BluFFS and UFS journaling support which were mentioned > > > in recent years. > > > > This is very interesting! I can imagine this would be the way for > > systems where ZFS is not an option but SU are reaching their limits. > > Have you had a look at gjournal(8)? I played with a gjournal, it is simple and working, but not usable where performance matters. A write performance is degraded to about half of a performance without gjournal (with a gjournal on top of a gmirror it is even more slower) Miroslav Lachman From owner-freebsd-fs@FreeBSD.ORG Mon Oct 27 16:15:18 2008 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 CD1E01065674 for ; Mon, 27 Oct 2008 16:15:18 +0000 (UTC) (envelope-from numisemis@yahoo.com) Received: from web36601.mail.mud.yahoo.com (web36601.mail.mud.yahoo.com [209.191.85.18]) by mx1.freebsd.org (Postfix) with SMTP id 7953F8FC0A for ; Mon, 27 Oct 2008 16:15:18 +0000 (UTC) (envelope-from numisemis@yahoo.com) Received: (qmail 1456 invoked by uid 60001); 27 Oct 2008 16:14:31 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=W4UT1u23S2UID8HS1yeKTJya7vdJXNEeK/kZ49uC4lNUktwJRj21YPpETUYxme/vFbVHN33Xydti30GUjbvY6v7KAQ4uIgo3ON+DamyYFQ1cwbR/dKcE1PcWDBRC55WhdegQ/TKGGgzLu4o2z12TFHdYemCybCy1MaPhqHbU4JY=; X-YMail-OSG: bmAklO0VM1masE6gndV_TJ5eDf2w4DkUd2MEm6Ng1TP3eitVkYMmmyHPaOhoQsNmWZH4ZlX6dFTLT_mT_1ASYlpcbu1_dTvKOSDh7.ztOMuzi0Kfa1VszGLz1d4PWDaPsHwZTi4oLtLFgEUycohmrXWfmkOomguDBJnJeaiDKj2nHdw9R8jy70k4EQVE Received: from [213.147.110.159] by web36601.mail.mud.yahoo.com via HTTP; Mon, 27 Oct 2008 09:14:31 PDT X-Mailer: YahooMailWebService/0.7.247.3 Date: Mon, 27 Oct 2008 09:14:31 -0700 (PDT) From: Simun Mikecin To: grafan@gmail.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <169608.99606.qm@web36601.mail.mud.yahoo.com> X-Mailman-Approved-At: Mon, 27 Oct 2008 16:58:51 +0000 Cc: freebsd-fs@freebsd.org, gamato@users.sf.net Subject: Re: journaling filesystem X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: numisemis@yahoo.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2008 16:15:18 -0000 "Rong-en Fan" wrote: >Actually, gjournal has the problem with fast write load. It panics if the >journal overflows... I was told by pjd@ that if I have been played with the >sysctls and it still overflows, then there is nothing we can do... pjd@ should answer this, but AFAIK journal size should be at least 2 * switch_time * transfer_rate where transfer_rate is your HDD bandwidth in MB/s. So for a fictional HDD that has 150MB/s (most real HDDs are much lower than this) and the default switch_time (which is 10) that would be: 2 * 10 * 150 = 3000MB for the journal minimum. I'm sure that increasing journal even more (or reducing switch_time) should make it stable (if it already isn't). From owner-freebsd-fs@FreeBSD.ORG Mon Oct 27 17:03:45 2008 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 E136B1065707 for ; Mon, 27 Oct 2008 17:03:45 +0000 (UTC) (envelope-from lulf@stud.ntnu.no) Received: from bene2.itea.ntnu.no (bene2.itea.ntnu.no [IPv6:2001:700:300:3::57]) by mx1.freebsd.org (Postfix) with ESMTP id 68F5E8FC16 for ; Mon, 27 Oct 2008 17:03:45 +0000 (UTC) (envelope-from lulf@stud.ntnu.no) Received: from localhost (localhost [127.0.0.1]) by bene2.itea.ntnu.no (Postfix) with ESMTP id 9C1BD90002; Mon, 27 Oct 2008 18:03:43 +0100 (CET) Received: from nobby (unknown [IPv6:2001:700:300:3::184]) by bene2.itea.ntnu.no (Postfix) with ESMTP id 5EB0B90001; Mon, 27 Oct 2008 18:03:43 +0100 (CET) Date: Mon, 27 Oct 2008 18:03:43 +0100 From: Ulf Lilleengen To: Robert Cousins Message-ID: <20081027170343.GA11687@nobby.lan> References: <4904B998.1030107@RCousins.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4904B998.1030107@RCousins.com> User-Agent: Mutt/1.5.18 (2008-05-17) X-Virus-Scanned: Debian amavisd-new at bene2.itea.ntnu.no Cc: freebsd-fs@freebsd.org Subject: Re: ZFS extended attributes 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: Mon, 27 Oct 2008 17:03:46 -0000 On Sun, Oct 26, 2008 at 11:40:24AM -0700, Robert Cousins wrote: > I was trying to run a program over ZFS which runs under UFS. After some > tracking, I found that the program was using extended file attributes > under UFS2 and that these are not supported under ZFS. > > Is there a plan to support extended attributes under ZFS? The perforce version that will commited sometime in the future supports extended attributes. -- Ulf Lilleengen From owner-freebsd-fs@FreeBSD.ORG Thu Oct 30 07:32:57 2008 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 4ED40106564A for ; Thu, 30 Oct 2008 07:32:57 +0000 (UTC) (envelope-from k0802647@telus.net) Received: from defout.telus.net (defout.telus.net [204.209.205.13]) by mx1.freebsd.org (Postfix) with ESMTP id 005BF8FC18 for ; Thu, 30 Oct 2008 07:32:56 +0000 (UTC) (envelope-from k0802647@telus.net) Received: from priv-edmwaa05.telusplanet.net ([204.209.205.55]) by priv-edmwes23.telusplanet.net (InterMail vM.7.08.02.00 201-2186-121-20061213) with ESMTP id <20081030065846.HIRD7381.priv-edmwes23.telusplanet.net@priv-edmwaa05.telusplanet.net> for ; Thu, 30 Oct 2008 00:58:46 -0600 Received: from oliver.bc.lan (d75-157-26-132.bchsia.telus.net [75.157.26.132]) by priv-edmwaa05.telusplanet.net (BorderWare Security Platform) with ESMTP id 18AC151530353180 for ; Thu, 30 Oct 2008 00:58:45 -0600 (MDT) Received: from [10.111.111.112] (unknown [10.111.111.112]) by oliver.bc.lan (Postfix) with ESMTP id 3EA04645D; Wed, 29 Oct 2008 23:58:45 -0700 (PDT) Message-ID: <49095B24.6010007@telus.net> Date: Wed, 29 Oct 2008 23:58:44 -0700 From: Carl User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: gmirror with only some partitions gjournal'd, autosync setting? 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: Thu, 30 Oct 2008 07:32:57 -0000 I've built a GEOM mirror on a single slice of a single disk and am currently inserting the second disk. Of the partitions in the mirror, I made only a few of them gjournal'd. From this thread, I understand that auto-synchronization is unnecessary for gjournal on top of gmirror: http://lists.freebsd.org/pipermail/freebsd-hackers/2007-January/019276.html I'm thinking my non-journaled partitions (the ones too small to be journaled) still need to be sync'd after crashes, so how can I enable auto-synch for those partitions and not the ones that are journaled? What is the correct thing to do here? Carl / K0802647 From owner-freebsd-fs@FreeBSD.ORG Fri Oct 31 03:32:10 2008 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 C1EFE106567F for ; Fri, 31 Oct 2008 03:32:10 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [76.96.62.80]) by mx1.freebsd.org (Postfix) with ESMTP id 6D8BB8FC17 for ; Fri, 31 Oct 2008 03:32:10 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA11.westchester.pa.mail.comcast.net ([76.96.62.36]) by QMTA08.westchester.pa.mail.comcast.net with comcast id ZCKS1a0500mv7h058FXopJ; Fri, 31 Oct 2008 03:31:48 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA11.westchester.pa.mail.comcast.net with comcast id ZFY81a00C2P6wsM3XFY8H6; Fri, 31 Oct 2008 03:32:09 +0000 X-Authority-Analysis: v=1.0 c=1 a=aQgbMQmz5TEA:10 a=qMCG-Xc8eBMA:10 a=QycZ5dHgAAAA:8 a=1NznHZZxJBy8A4U4o0sA:9 a=VjeOX3E2aCwusk-sF1gA:7 a=VNbSGEzM3tjgmtdmVJVFkesu6k8A:4 a=EoioJ0NPDVgA:10 a=l5bgqdDrG-gA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id 3DE29C9419; Thu, 30 Oct 2008 20:32:08 -0700 (PDT) Date: Thu, 30 Oct 2008 20:32:08 -0700 From: Jeremy Chadwick To: Danny Carroll Message-ID: <20081031033208.GA21220@icarus.home.lan> References: <490A782F.9060406@dannysplace.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <490A782F.9060406@dannysplace.net> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-fs@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Areca vs. ZFS performance testing. 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: Fri, 31 Oct 2008 03:32:10 -0000 Cross-posting this to freebsd-fs, as I'm sure people there will have other recommendations. (This is one of those rare cross-posting situations.....) On Fri, Oct 31, 2008 at 01:14:55PM +1000, Danny Carroll wrote: > I've just become the proud new owner of an Areca 1231-ML which I plan to > use to set up an office server. > > I'm very curious as to how ZFS compares to a hardware solution so I plan > to run some tests before I put this thing to work. > > The purpose of this email is to find out if anyone would like to see > specific things tested as well as perhaps get some advice on how to get > the most information out of the tests. > > My setup: > Supermicro X7SBE board with 2Gb ram and an E6550 Core 2 Duo. > FreeBSD 7.0-Stable compiled with amd64 sources from mid August. > 1 x ST9120822AS 120gb disk (for the OS) > For the array(s) > 9 x ST31000340AS 1tb disks > 1 x ST31000333AS 1tb disk (trying to swap this for a ST31000340AS) > > My thoughts are to do the following tests with bonnie++: > 1 5 disk Areca Raid5 > 2 5 Disk ZFS RaidZ1 (Connected to Areca in JBOD mode) > 3 5 Disk ZFS RaidZ1 (Connected to ICH9 On board SATA controller) > 4 5 disk Areca Raid6 > 5 5 Disk ZFS RaidZ2 (Connected to Areca in JBOD mode) > 6 5 Disk ZFS RaidZ2 (Connected to ICH9 On board SATA controller) > 7 10 disk Areca Raid5 > 8 10 Disk ZFS RaidZ1 (Connected to Areca in JBOD mode) > 9 10 disk Areca Raid6 > 10 10 Disk ZFS RaidZ2 (Connected to Areca in JBOD mode) > > My aim is to see what sort of performance gain you get by buying an > Areca card for use in JBOD as well as seeing how ZFS compares to the > hardware solution which offers write caching etc. I'm really only > interested in testing ZFS's volume management performance, so for that > reason I will also put ZFS on the Areca Raid drives. Not sure if it's a > good idea to create 2 Raid drives and stripe them or simply use 1 large > disk and give it to ZFS. > > Any thoughts on this setup as well as advice on what options to give to > bonnie++ (or suggestions on another disk testing package) are very welcome. I think these sets of tests are good. There are some others I'd like to see, but they'd only be applicable if the 1231-ML has hardware cache. I can mention what those are if the card does have hardware caching. > I do have some concern about the size of the eventual array and ZFS' use > of system memory. Are there guidelines available that give advice on > how much memory a box should have with large ZFS arrays? The general concept is: "the more RAM the better". However, if you're using RELENG_7, then there's not much point (speaking solely about ZFS) to getting more than maybe 3 or 4GB; you're still limited to a 2GB kmap maximum. Regarding size of the array vs. memory usage: as long as you tune kmem and ZFS ARC, you shouldn't have much trouble. There have been some key people reporting lately that they run very large ZFS arrays without issue, with proper tuning. Also, just a reminder: do not pick a value of 2048M for kmem_size or kmem_size_max; the machine won't boot/work. You shouldn't go above something like 1536M, although some have tuned slightly above that with success. (You need to remember that there is more to kernel memory allocation than just this, so you don't want to exhaust it all assigning it to kmap. Hope that makes sense...) > Can an AMD64 kernel make use of memory above 2g? Only on CURRENT; 7.x cannot, and AFAIK, will never be able to, as the engineering efforts required to fix it are too great. I look forward to seeing your numbers. Someone here might be able to compile them into some graphs and other whatnots to make things easier for future readers. Thanks for doing all of this! -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Fri Oct 31 04:34:14 2008 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 925F31065678 for ; Fri, 31 Oct 2008 04:34:14 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA04.emeryville.ca.mail.comcast.net (qmta04.emeryville.ca.mail.comcast.net [76.96.30.40]) by mx1.freebsd.org (Postfix) with ESMTP id 1F5FC8FC0A for ; Fri, 31 Oct 2008 04:34:13 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA05.emeryville.ca.mail.comcast.net ([76.96.30.43]) by QMTA04.emeryville.ca.mail.comcast.net with comcast id ZCK41a0080vp7WLA4GaDvG; Fri, 31 Oct 2008 04:34:13 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA05.emeryville.ca.mail.comcast.net with comcast id ZGaC1a0072P6wsM8RGaCL5; Fri, 31 Oct 2008 04:34:13 +0000 X-Authority-Analysis: v=1.0 c=1 a=aQgbMQmz5TEA:10 a=qMCG-Xc8eBMA:10 a=6I5d2MoRAAAA:8 a=QycZ5dHgAAAA:8 a=r2IpIlXKJzo0qGbSTxYA:9 a=HyDW3Yd7XQi1SnKOiQQA:7 a=gJmddOa55550gD97BL6kJ_vfTOwA:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id 3EDB8C9419; Thu, 30 Oct 2008 21:34:12 -0700 (PDT) Date: Thu, 30 Oct 2008 21:34:12 -0700 From: Jeremy Chadwick To: Danny Carroll Message-ID: <20081031043412.GA22289@icarus.home.lan> References: <490A782F.9060406@dannysplace.net> <20081031033208.GA21220@icarus.home.lan> <490A849C.7030009@dannysplace.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <490A849C.7030009@dannysplace.net> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-fs@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Areca vs. ZFS performance testing. 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: Fri, 31 Oct 2008 04:34:14 -0000 On Fri, Oct 31, 2008 at 02:07:56PM +1000, Danny Carroll wrote: > Jeremy Chadwick wrote: > > I think these sets of tests are good. There are some others I'd like to > > see, but they'd only be applicable if the 1231-ML has hardware cache. I > > can mention what those are if the card does have hardware caching. > > The card comes standard with 256Mb of cache. I'd like to see the performance difference between these scenarios: - Memory cache enabled on Areca, write caching enabled on disks - Memory cache enabled on Areca, write caching disabled on disks - Memory cache disabled on Areca, write caching enabled on disks - Memory cache disabled on Areca, write caching disabled on disks I don't know if the controller will let you disable use of memory cache, but I'm hoping it does. I'm pretty sure it lets you disable disk write caching in its BIOS or via the CLI utility. > >> I do have some concern about the size of the eventual array and ZFS' use > >> of system memory. Are there guidelines available that give advice on > >> how much memory a box should have with large ZFS arrays? > > > > The general concept is: "the more RAM the better". However, if you're > > using RELENG_7, then there's not much point (speaking solely about ZFS) > > to getting more than maybe 3 or 4GB; you're still limited to a 2GB kmap > > maximum. > > > > Regarding size of the array vs. memory usage: as long as you tune kmem > > and ZFS ARC, you shouldn't have much trouble. There have been some > > key people reporting lately that they run very large ZFS arrays without > > issue, with proper tuning. > > I followed the recommendations here: > http://wiki.freebsd.org/ZFSTuningGuide > > vm.kmem_size="1024M" > vm.kmem_size_max="1024M" > vfs.zfs.debug=1 > > And : kern.maxvnodes=400000 > > I have not added the following because they were listed in the i386 > section. (These values were quoted for a machine with 768Mb of ram) > vfs.zfs.arc_max="40M" > vfs.zfs.vdev.cache.size="5M" > > Am I right in assuming these do not apply to amd64? The article was not > specific. All of the tuning variables apply to i386 and amd64. You do not need the vfs.zfs.debug variable; I'm not sure why you enabled that. I imagine it will have some impact on performance. I do not know anything about kern.maxvnodes, or vfs.zfs.vdev.cache.size. The tuning variables I advocate for a system with 2GB of RAM or more, on RELENG_7, are: vm.kmem_size="1536M" vm.kmem_size_max="1536M" vfs.zfs.arc_min="16M" vfs.zfs.arc_max="64M" vfs.zfs.prefetch_disable="1" You can gradually increase arc_min and arc_max by ~16MB increments as you see fit; you should see general performance improvements as they get larger (more data being kept in the ARC), but don't get too crazy. I've tuned arc_max up to 128MB before with success, but I don't want to try anything larger without decreasing kmem_size_*. > > Also, just a reminder: do not pick a value of 2048M for kmem_size or > > kmem_size_max; the machine won't boot/work. You shouldn't go above > > something like 1536M, although some have tuned slightly above that > > with success. (You need to remember that there is more to kernel > > memory allocation than just this, so you don't want to exhaust it all > > assigning it to kmap. Hope that makes sense...) > > It makes sense. I'm using 1024 at the moment, but I've never really > looked into what memory is actually being used. > > Tuning advice here would be well received :-) The only reason you need to adjust kmem_size and kmem_size_max is to increase the amount of available kmap memory which ZFS relies heavily on. If the values are too low, under heavy I/O, the kernel will panic with kmem exhaustion messages (see the ZFS Wiki for what some look like, or my Wiki). I would recommend you stick with a consistent set of loader.conf tuning variables, and focus entirely on comparing the performance of ZFS on the Areca controller vs. the ICH controller. You can perform a "ZFS tuning comparison" later. One step at a time; don't over-exert yourself quite yet. :-) You can add raidz2 to this comparison list too if you feel it's worthwhile, but I think most people will be using raidz1. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Fri Oct 31 04:46:12 2008 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 73638106564A for ; Fri, 31 Oct 2008 04:46:12 +0000 (UTC) (envelope-from andrew@modulus.org) Received: from email.octopus.com.au (host-122-100-2-232.octopus.com.au [122.100.2.232]) by mx1.freebsd.org (Postfix) with ESMTP id 353998FC14 for ; Fri, 31 Oct 2008 04:46:11 +0000 (UTC) (envelope-from andrew@modulus.org) Received: by email.octopus.com.au (Postfix, from userid 1002) id BE7F217E4F; Fri, 31 Oct 2008 15:46:09 +1100 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au X-Spam-Level: X-Spam-Status: No, score=-1.3 required=10.0 tests=ALL_TRUSTED, DNS_FROM_SECURITYSAGE autolearn=no version=3.2.3 Received: from [10.1.50.60] (ppp121-44-142-25.lns10.syd7.internode.on.net [121.44.142.25]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id 9A71F17E5F; Fri, 31 Oct 2008 15:46:05 +1100 (EST) Message-ID: <490A8D23.6030309@modulus.org> Date: Fri, 31 Oct 2008 15:44:19 +1100 From: Andrew Snow User-Agent: Thunderbird 2.0.0.14 (X11/20080523) MIME-Version: 1.0 To: Jeremy Chadwick References: <490A782F.9060406@dannysplace.net> <20081031033208.GA21220@icarus.home.lan> <490A849C.7030009@dannysplace.net> <20081031043412.GA22289@icarus.home.lan> In-Reply-To: <20081031043412.GA22289@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, Danny Carroll Subject: Re: Areca vs. ZFS performance testing. 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: Fri, 31 Oct 2008 04:46:12 -0000 Jeremy Chadwick wrote: > I would recommend you stick with a consistent set of loader.conf > tuning variables, and focus entirely on comparing the performance of > ZFS on the Areca controller vs. the ICH controller. Its probably worth playing with vfs.zfs.cache_flush_disable when using the hardware RAID. By default, ZFS will flush the entire hardware cache just to make sure the ZFS Intent Log (ZIL) has been written. This isn't so bad on a group of hard disks with small caches, but bad if you have 256mb of controller write cache. From owner-freebsd-fs@FreeBSD.ORG Fri Oct 31 04:47:49 2008 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 78385106564A; Fri, 31 Oct 2008 04:47:49 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from mail.dannysplace.net (mail.dannysplace.net [213.133.54.210]) by mx1.freebsd.org (Postfix) with ESMTP id 282558FC0C; Fri, 31 Oct 2008 04:47:49 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from 203-206-171-212.perm.iinet.net.au ([203.206.171.212] helo=[192.168.10.10]) by mail.dannysplace.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KvlvG-000JWi-9A; Fri, 31 Oct 2008 14:47:48 +1000 Message-ID: <490A8DFB.8030405@dannysplace.net> Date: Fri, 31 Oct 2008 14:47:55 +1000 From: Danny Carroll User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Jeremy Chadwick References: <490A782F.9060406@dannysplace.net> <20081031033208.GA21220@icarus.home.lan> <490A849C.7030009@dannysplace.net> <20081031043412.GA22289@icarus.home.lan> In-Reply-To: <20081031043412.GA22289@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Authenticated-User: danny X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Exim-Version: 4.69 (build at 08-Jul-2008 08:59:40) X-Date: 2008-10-31 14:47:46 X-Connected-IP: 203.206.171.212:1692 X-Message-Linecount: 97 X-Body-Linecount: 83 X-Message-Size: 3915 X-Body-Size: 3244 X-Received-Count: 1 X-Recipient-Count: 3 X-Local-Recipient-Count: 3 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 X-SA-Exim-Connect-IP: 203.206.171.212 X-SA-Exim-Rcpt-To: koitsu@FreeBSD.org, freebsd-fs@freebsd.org, freebsd-hardware@freebsd.org X-SA-Exim-Mail-From: fbsd@dannysplace.net X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on ferrari.dannysplace.net X-Spam-Level: X-Spam-Status: No, score=0.2 required=8.0 tests=ALL_TRUSTED,TVD_RCVD_IP autolearn=disabled version=3.2.5 X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail.dannysplace.net) Cc: freebsd-fs@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Areca vs. ZFS performance testing. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: fbsd@dannysplace.net List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2008 04:47:49 -0000 Jeremy Chadwick wrote: > On Fri, Oct 31, 2008 at 02:07:56PM +1000, Danny Carroll wrote: > - Memory cache enabled on Areca, write caching enabled on disks > - Memory cache enabled on Areca, write caching disabled on disks > - Memory cache disabled on Areca, write caching enabled on disks > - Memory cache disabled on Areca, write caching disabled on disks Does it matter what type of disk we are talking about? What I mean is, do you want to see this with both Raid5 and Raid6 arrays? Also, I'm pretty sure that in JBod mode the cache (on the card) will do nothing. But I am not certain, so I'll do the tests there as well. What about stripe sizes? I mainly use big files so I was going to stripe accordingly. But the bonnie++ tests might give strange results in that case. > I don't know if the controller will let you disable use of memory cache, > but I'm hoping it does. I'm pretty sure it lets you disable disk > write caching in its BIOS or via the CLI utility. > It's been a while since I've had a hardware raid card. I'll see what is available. > All of the tuning variables apply to i386 and amd64. > > You do not need the vfs.zfs.debug variable; I'm not sure why you enabled > that. I imagine it will have some impact on performance. Consider it gone. > I do not know anything about kern.maxvnodes, or vfs.zfs.vdev.cache.size. > At the moment I am not hitting anywhere near the max vnodes setting. So I think it is irrelevant. > The tuning variables I advocate for a system with 2GB of RAM or more, > on RELENG_7, are: > > vm.kmem_size="1536M" > vm.kmem_size_max="1536M" > vfs.zfs.arc_min="16M" > vfs.zfs.arc_max="64M" > vfs.zfs.prefetch_disable="1" > > You can gradually increase arc_min and arc_max by ~16MB increments as > you see fit; you should see general performance improvements as they > get larger (more data being kept in the ARC), but don't get too crazy. > I've tuned arc_max up to 128MB before with success, but I don't want > to try anything larger without decreasing kmem_size_*. What is the arc? Is it the ZFS file cache? > The only reason you need to adjust kmem_size and kmem_size_max is to > increase the amount of available kmap memory which ZFS relies heavily > on. If the values are too low, under heavy I/O, the kernel will panic > with kmem exhaustion messages (see the ZFS Wiki for what some look > like, or my Wiki). > > I would recommend you stick with a consistent set of loader.conf > tuning variables, and focus entirely on comparing the performance of > ZFS on the Areca controller vs. the ICH controller. Once I am settled on a 'starting point' I won't be altering it for the tests. > You can perform a "ZFS tuning comparison" later. One step at a time; > don't over-exert yourself quite yet. :-) Yeah, this is weekend stuff for me at the moment, it will take me some time to get things done. Firstly I need to figure out how I am going to hook up 10 drives to my system. I don't have the drive-bay space and I am not shelling out for a new case so I am hunting around for an ancient external disk cabinet. > You can add raidz2 to this comparison list too if you feel it's > worthwhile, but I think most people will be using raidz1. I might as well do both. -D From owner-freebsd-fs@FreeBSD.ORG Fri Oct 31 04:48:38 2008 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 94C971065675 for ; Fri, 31 Oct 2008 04:48:38 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from mail.dannysplace.net (mail.dannysplace.net [213.133.54.210]) by mx1.freebsd.org (Postfix) with ESMTP id 47C3C8FC2C for ; Fri, 31 Oct 2008 04:48:38 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from 203-206-171-212.perm.iinet.net.au ([203.206.171.212] helo=[192.168.10.10]) by mail.dannysplace.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KvlIb-000JJS-BH; Fri, 31 Oct 2008 14:08:00 +1000 Message-ID: <490A849C.7030009@dannysplace.net> Date: Fri, 31 Oct 2008 14:07:56 +1000 From: Danny Carroll User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Jeremy Chadwick References: <490A782F.9060406@dannysplace.net> <20081031033208.GA21220@icarus.home.lan> In-Reply-To: <20081031033208.GA21220@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Authenticated-User: danny X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Exim-Version: 4.69 (build at 08-Jul-2008 08:59:40) X-Date: 2008-10-31 14:07:50 X-Connected-IP: 203.206.171.212:1636 X-Message-Linecount: 84 X-Body-Linecount: 70 X-Message-Size: 3160 X-Body-Size: 2565 X-Received-Count: 1 X-Recipient-Count: 3 X-Local-Recipient-Count: 3 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 X-SA-Exim-Connect-IP: 203.206.171.212 X-SA-Exim-Rcpt-To: koitsu@FreeBSD.org, freebsd-hardware@freebsd.org, freebsd-fs@freebsd.org X-SA-Exim-Mail-From: fbsd@dannysplace.net X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on ferrari.dannysplace.net X-Spam-Level: X-Spam-Status: No, score=0.2 required=8.0 tests=ALL_TRUSTED,TVD_RCVD_IP autolearn=disabled version=3.2.5 X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail.dannysplace.net) Cc: freebsd-fs@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Areca vs. ZFS performance testing. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: fbsd@dannysplace.net List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2008 04:48:38 -0000 Jeremy Chadwick wrote: > I think these sets of tests are good. There are some others I'd like to > see, but they'd only be applicable if the 1231-ML has hardware cache. I > can mention what those are if the card does have hardware caching. The card comes standard with 256Mb of cache. >> I do have some concern about the size of the eventual array and ZFS' use >> of system memory. Are there guidelines available that give advice on >> how much memory a box should have with large ZFS arrays? > > The general concept is: "the more RAM the better". However, if you're > using RELENG_7, then there's not much point (speaking solely about ZFS) > to getting more than maybe 3 or 4GB; you're still limited to a 2GB kmap > maximum. > > Regarding size of the array vs. memory usage: as long as you tune kmem > and ZFS ARC, you shouldn't have much trouble. There have been some > key people reporting lately that they run very large ZFS arrays without > issue, with proper tuning. I followed the recommendations here: http://wiki.freebsd.org/ZFSTuningGuide vm.kmem_size="1024M" vm.kmem_size_max="1024M" vfs.zfs.debug=1 And : kern.maxvnodes=400000 I have not added the following because they were listed in the i386 section. (These values were quoted for a machine with 768Mb of ram) vfs.zfs.arc_max="40M" vfs.zfs.vdev.cache.size="5M" Am I right in assuming these do not apply to amd64? The article was not specific. > > Also, just a reminder: do not pick a value of 2048M for kmem_size or > kmem_size_max; the machine won't boot/work. You shouldn't go above > something like 1536M, although some have tuned slightly above that > with success. (You need to remember that there is more to kernel > memory allocation than just this, so you don't want to exhaust it all > assigning it to kmap. Hope that makes sense...) It makes sense. I'm using 1024 at the moment, but I've never really looked into what memory is actually being used. Tuning advice here would be well received :-) >> Can an AMD64 kernel make use of memory above 2g? > > Only on CURRENT; 7.x cannot, and AFAIK, will never be able to, as the > engineering efforts required to fix it are too great. > > I look forward to seeing your numbers. Someone here might be able to > compile them into some graphs and other whatnots to make things easier > for future readers. Ahhh, well, that will eventually decide my upgrade path when RELENG_8 is released and stable. > Thanks for doing all of this! No worries, hopefully it will be useful information to future google searches :-P -D From owner-freebsd-fs@FreeBSD.ORG Fri Oct 31 04:50:04 2008 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 163211065670; Fri, 31 Oct 2008 04:50:04 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from mail.dannysplace.net (mail.dannysplace.net [213.133.54.210]) by mx1.freebsd.org (Postfix) with ESMTP id C30368FC14; Fri, 31 Oct 2008 04:50:03 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from 203-206-171-212.perm.iinet.net.au ([203.206.171.212] helo=[192.168.10.10]) by mail.dannysplace.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KvlxQ-000JXO-CF; Fri, 31 Oct 2008 14:50:03 +1000 Message-ID: <490A8E82.1080901@dannysplace.net> Date: Fri, 31 Oct 2008 14:50:10 +1000 From: Danny Carroll User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Andrew Snow References: <490A782F.9060406@dannysplace.net> <20081031033208.GA21220@icarus.home.lan> <490A849C.7030009@dannysplace.net> <20081031043412.GA22289@icarus.home.lan> <490A8D23.6030309@modulus.org> In-Reply-To: <490A8D23.6030309@modulus.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Authenticated-User: danny X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Exim-Version: 4.69 (build at 08-Jul-2008 08:59:40) X-Date: 2008-10-31 14:50:00 X-Connected-IP: 203.206.171.212:1695 X-Message-Linecount: 27 X-Body-Linecount: 13 X-Message-Size: 1059 X-Body-Size: 363 X-Received-Count: 1 X-Recipient-Count: 3 X-Local-Recipient-Count: 3 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 X-SA-Exim-Connect-IP: 203.206.171.212 X-SA-Exim-Rcpt-To: andrew@modulus.org, koitsu@FreeBSD.org, freebsd-fs@freebsd.org X-SA-Exim-Mail-From: fbsd@dannysplace.net X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on ferrari.dannysplace.net X-Spam-Level: X-Spam-Status: No, score=0.2 required=8.0 tests=ALL_TRUSTED,TVD_RCVD_IP autolearn=disabled version=3.2.5 X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail.dannysplace.net) Cc: freebsd-fs@freebsd.org, Jeremy Chadwick Subject: Re: Areca vs. ZFS performance testing. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: fbsd@dannysplace.net List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2008 04:50:04 -0000 Andrew Snow wrote: > Its probably worth playing with vfs.zfs.cache_flush_disable when using > the hardware RAID. > > By default, ZFS will flush the entire hardware cache just to make sure > the ZFS Intent Log (ZIL) has been written. > > This isn't so bad on a group of hard disks with small caches, but bad if > you have 256mb of controller write cache. Ok. From owner-freebsd-fs@FreeBSD.ORG Fri Oct 31 04:55:02 2008 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 1F36B1065670; Fri, 31 Oct 2008 04:55:02 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from mail.dannysplace.net (mail.dannysplace.net [213.133.54.210]) by mx1.freebsd.org (Postfix) with ESMTP id C56ED8FC1D; Fri, 31 Oct 2008 04:55:01 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from 203-206-171-212.perm.iinet.net.au ([203.206.171.212] helo=[192.168.10.10]) by mail.dannysplace.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Kvm2F-000JZ2-9I; Fri, 31 Oct 2008 14:55:01 +1000 Message-ID: <490A8FAD.8060009@dannysplace.net> Date: Fri, 31 Oct 2008 14:55:09 +1000 From: Danny Carroll User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Jeremy Chadwick References: <490A782F.9060406@dannysplace.net> <20081031033208.GA21220@icarus.home.lan> <490A849C.7030009@dannysplace.net> <20081031043412.GA22289@icarus.home.lan> In-Reply-To: <20081031043412.GA22289@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Authenticated-User: danny X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Exim-Version: 4.69 (build at 08-Jul-2008 08:59:40) X-Date: 2008-10-31 14:54:59 X-Connected-IP: 203.206.171.212:1696 X-Message-Linecount: 31 X-Body-Linecount: 17 X-Message-Size: 1347 X-Body-Size: 676 X-Received-Count: 1 X-Recipient-Count: 3 X-Local-Recipient-Count: 3 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 X-SA-Exim-Connect-IP: 203.206.171.212 X-SA-Exim-Rcpt-To: koitsu@FreeBSD.org, freebsd-fs@freebsd.org, freebsd-hardware@freebsd.org X-SA-Exim-Mail-From: fbsd@dannysplace.net X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on ferrari.dannysplace.net X-Spam-Level: X-Spam-Status: No, score=0.2 required=8.0 tests=ALL_TRUSTED,TVD_RCVD_IP autolearn=disabled version=3.2.5 X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail.dannysplace.net) Cc: freebsd-fs@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Areca vs. ZFS performance testing. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: fbsd@dannysplace.net List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2008 04:55:02 -0000 Jeremy Chadwick wrote: > > I'd like to see the performance difference between these scenarios: > > - Memory cache enabled on Areca, write caching enabled on disks > - Memory cache enabled on Areca, write caching disabled on disks > - Memory cache disabled on Areca, write caching enabled on disks > - Memory cache disabled on Areca, write caching disabled on disks > > I don't know if the controller will let you disable use of memory cache, > but I'm hoping it does. I'm pretty sure it lets you disable disk > write caching in its BIOS or via the CLI utility. The manual suggests that the write cache can be disabled. Perhaps there is no read cache for this card. -D From owner-freebsd-fs@FreeBSD.ORG Fri Oct 31 09:21:00 2008 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 DF485106567C for ; Fri, 31 Oct 2008 09:21:00 +0000 (UTC) (envelope-from numisemis@yahoo.com) Received: from web36603.mail.mud.yahoo.com (web36603.mail.mud.yahoo.com [209.191.85.20]) by mx1.freebsd.org (Postfix) with SMTP id 90B468FC1C for ; Fri, 31 Oct 2008 09:21:00 +0000 (UTC) (envelope-from numisemis@yahoo.com) Received: (qmail 18399 invoked by uid 60001); 31 Oct 2008 09:20:59 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Message-ID; b=f0Qkp8pUGu9d1eONa4VW/Zhc7gRmbXGt8jwqT1u8do1nUAmzcKYzok4y5UdzheyNJjRpx1LYkA7Q/mP73mNUKyHLDCQOeRpedosg1P5DQLzwd1uy8SMtpmH7uV3vuOANgwEbHkppIDEqPSGBTIcMiwJoMh0o4p6xJi0p0iYrf6w=; X-YMail-OSG: tE_zPJYVM1nwdJxd.8xh3pfo1Y1WdeEAD4qBiLlqPqNSOlaQlYMdXeuhrZG9W3lgyvZ.xhXBfwtXXSSDqDisLdzLhCPzRcXMT51uqy6uhguBADCyQ9BIkAwLiDys3VbYSI_a Received: from [213.147.110.159] by web36603.mail.mud.yahoo.com via HTTP; Fri, 31 Oct 2008 02:20:59 PDT X-Mailer: YahooMailWebService/0.7.260.1 Date: Fri, 31 Oct 2008 02:20:59 -0700 (PDT) From: Simun Mikecin To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <880498.17704.qm@web36603.mail.mud.yahoo.com> X-Mailman-Approved-At: Fri, 31 Oct 2008 11:23:36 +0000 Subject: Re: Areca vs. ZFS performance testing. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: numisemis@yahoo.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2008 09:21:01 -0000 Jeremy Chadwick wrote: > The tuning variables I advocate for a system with 2GB of RAM or more, > on RELENG_7, are: > vm.kmem_size="1536M" > vm.kmem_size_max="1536M" There is no point in setting vm.kmem_size_max. Setting vm.kmem_size is enough. vm.kmem_size_max is used for auto-tuning of kmem size which is in this case actually overriden by manually setting vm.kmem_size. > vfs.zfs.arc_min="16M" > vfs.zfs.arc_max="64M" > vfs.zfs.prefetch_disable="1" > You can gradually increase arc_min and arc_max by > ~16MB increments as > you see fit; you should see general performance > improvements as they > get larger (more data being kept in the ARC), but > don't get too crazy. > I've tuned arc_max up to 128MB before with > success, but I don't want > to try anything larger without decreasing kmem_size_*. Can you explain why would you have to decrease kmem_size to use larger ARC? AFAIK it should be contrary to what you are saying: when you use larger kmem_size you can also use larger arc_max. My suggestion if you are using kmem_size of 1536M would be to not tune arc_min and arc_max if your system isn't panicing. If it does you should try decreasing arc_max (from it's default value) until it doesn't. From owner-freebsd-fs@FreeBSD.ORG Fri Oct 31 11:57:19 2008 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 232271065691 for ; Fri, 31 Oct 2008 11:57:19 +0000 (UTC) (envelope-from numisemis@yahoo.com) Received: from web36607.mail.mud.yahoo.com (web36607.mail.mud.yahoo.com [209.191.85.24]) by mx1.freebsd.org (Postfix) with SMTP id C43B98FC16 for ; Fri, 31 Oct 2008 11:57:18 +0000 (UTC) (envelope-from numisemis@yahoo.com) Received: (qmail 95792 invoked by uid 60001); 31 Oct 2008 11:57:18 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=Xx5P1H9N7KfCFmOVYMmufYtn1vsNP97B0b0jqM0p5M7X0X6JquHiFx7tLCBXubf0h6Q/We0DICYH3YuidGI49yCl7jLMEbQAzzSLBnmavqo7HHSPR+dFAiqUXmpxVkaOqMJUPFRndPlHMSryBp+dKxFhTd0DQtsSvwttHIGmwpk=; X-YMail-OSG: pGRKbMgVM1nnwL_FxOOUxkTIpyITRbpGf3fq_BkMuHx3YZbgjlGAwbXLMJZ8h_zlaw-- Received: from [213.147.110.159] by web36607.mail.mud.yahoo.com via HTTP; Fri, 31 Oct 2008 04:57:18 PDT X-Mailer: YahooMailWebService/0.7.260.1 Date: Fri, 31 Oct 2008 04:57:18 -0700 (PDT) From: Simun Mikecin To: Jeremy Chadwick MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <174490.95560.qm@web36607.mail.mud.yahoo.com> X-Mailman-Approved-At: Fri, 31 Oct 2008 12:04:26 +0000 Cc: freebsd-fs@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Areca vs. ZFS performance testing. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: numisemis@yahoo.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2008 11:57:19 -0000 Jeremy Chadwick wrote: > Well, my understanding (which is probably wrong) is that the memory > used for the ARC is somehow separate from that of the kmap. I was > under the impression the kmap was used by ZFS for other things, and > did not include ARC. kmem is used by ARC. You can check your total kmem usage by ZFS using 'vmstat -m' under the line that says 'solaris'. > People have advocated increasing arc_min and arc_max in the past, citing > large performance gains as arc_max gets larger; you might see people > mentioning that they see great performance increases when increasing > arc_max from 64M to 128M. My understanding is that increasing the ARC > provides more actual cached data that ZFS can reference (vs. pulling it > off disk). Again, if I'm incorrect, please state so. You are correct about the benefits of increasing arc_max. I don't know of any benefits of tuning arc_min. Maybe someone else can answer this. By default on 7-STABLE arc_max will be 3/4 of kmem_size. So if you are using 1536M for kmem_size, arc_max will be 1152M by default. But some people will maybe need to lower it to avoid panic during heavy I/O since in those scenarios ARC cache size could for short periods of time be larger than arc_max and reach kmem limit. From owner-freebsd-fs@FreeBSD.ORG Fri Oct 31 16:36:32 2008 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 2DC241065674 for ; Fri, 31 Oct 2008 16:36:32 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by mx1.freebsd.org (Postfix) with ESMTP id AFC768FC18 for ; Fri, 31 Oct 2008 16:36:31 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: by nf-out-0910.google.com with SMTP id h3so603760nfh.33 for ; Fri, 31 Oct 2008 09:36:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=Fh+rdL3xA/cT9cqEOyapfBE+rrRPlUNfmNCS35++ouk=; b=lDyVxzJ/6h1P3ghqqn2rYp+cMY+7m91m3nFf8fLzigcOKvMKaWux8xc/2yheBvOOyB L/Vq99qDkittwi5mZydP9eo6BiT9uN3IslcRxZ+BoyOqQm8URkuhFJtcYXfJskTaJIpU 4MSzH5SqoEviX/+b2UJhtpzTzYi63AfpPTMsM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=RApj40rSUVjDSWGYsFDNzLiADmHY8vhHXQSUyfwEEFD4XImmXMcHuqzyHsISIOoxwn HOWoieO23ycQLTuBgZWHIf4xIr0XdgbNtdG9kfePLp72SYRxK1FNSQAoSuKwGWrUqjVq 0w9iMW3l9Iqpsf8P+ODiZKHbKIPdJy/xOIM3E= Received: by 10.210.75.6 with SMTP id x6mr13615054eba.2.1225469677013; Fri, 31 Oct 2008 09:14:37 -0700 (PDT) Received: by 10.210.20.8 with HTTP; Fri, 31 Oct 2008 09:14:36 -0700 (PDT) Message-ID: Date: Fri, 31 Oct 2008 12:14:36 -0400 From: grarpamp To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Benchmark tools: was Areca vs ZFS 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: Fri, 31 Oct 2008 16:36:32 -0000 Hi. Wanted to send an FYI for those who may not know about it. Lots of folks seem to mention Bonnie. There is also Iozone. It has been maintained fairly well and has/had useful features before Bonnie did/may. When compiling iozone change lib -lpthread to gcc option -pthread and you're done. There is also freebsd-performance list. Here are the current links for anyone interested. Happy benching! http://www.iozone.org/ ver : 3.311 port: 3.283 [old] http://www.coker.com.au/bonnie++/ ver : 1.03d port: none [???] http://www.coker.com.au/bonnie++/experimental/ ver : 1.94 port : 1.93d [old] From owner-freebsd-fs@FreeBSD.ORG Sat Nov 1 09:39:07 2008 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 7BA001065677 for ; Sat, 1 Nov 2008 09:39:07 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from fallbackmx08.syd.optusnet.com.au (fallbackmx08.syd.optusnet.com.au [211.29.132.10]) by mx1.freebsd.org (Postfix) with ESMTP id 03EB38FC30 for ; Sat, 1 Nov 2008 09:39:06 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail36.syd.optusnet.com.au (mail36.syd.optusnet.com.au [211.29.133.76]) by fallbackmx08.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m9VKIIlv031191 for ; Sat, 1 Nov 2008 07:18:18 +1100 Received: from server.vk2pj.dyndns.org (c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175]) by mail36.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m9VKIEwF029303 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 1 Nov 2008 07:18:15 +1100 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.3/8.14.3) with ESMTP id m9VKIEJQ054352; Sat, 1 Nov 2008 07:18:14 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.3/8.14.3/Submit) id m9VKIEZc054351; Sat, 1 Nov 2008 07:18:14 +1100 (EST) (envelope-from peter) Date: Sat, 1 Nov 2008 07:18:14 +1100 From: Peter Jeremy To: Pawel Jakub Dawidek Message-ID: <20081031201814.GA54286@server.vk2pj.dyndns.org> References: <20080727125413.GG1345@garage.freebsd.pl> <86tzd490qx.fsf@gmail.com> <20080829074738.GB3026@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PNTmBPCT7hxwcZjr" Content-Disposition: inline In-Reply-To: <20080829074738.GB3026@garage.freebsd.pl> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-fs@FreeBSD.org Subject: Re: ZFS patches. 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: Sat, 01 Nov 2008 09:39:07 -0000 --PNTmBPCT7hxwcZjr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Pawel, On 2008-Aug-28 20:47:30 +0000, Pawel Jakub Dawidek wrote: >On Fri, Aug 29, 2008 at 03:29:58AM +0400, swell.k@gmail.com wrote: >> (CC'ing Attilio, who made the commits) >>=20 >> Pawel Jakub Dawidek writes: >>=20 >> > Hi. >> > >> > http://people.freebsd.org/~pjd/patches/zfs_20080727.patch.bz2 >> > >> > The patch above contains the most recent ZFS version that could be fou= nd >> > in OpenSolaris as of today. Apart for large amount of new functionalit= y, >> > I belive there are many stability (and also performance) improvements >> > compared to the version from the base system. >> [...] >>=20 >> After r182371 and r182383 there are another three rejections. Namely >> cddl/contrib/opensolaris/lib/libzpool/common/sys/zfs_context.h.rej >> sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_file.c.rej >> sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_replay.c.rej >> I'm attaching them in case someone has a quick fix or idea how >> to solve them, especially regarding `+' lines. >>=20 >> In the meantime I'm reverting them locally hoping it will not do any >> harm to me. If this fails then I will stay with r182370 since I already >> upgraded my pools to 11th version and can't go back easily. > >There are some rejections, I know, and I'm tracking everything in >perforce. In the meantime there were two ZFS version bumps in >OpenSOlaris (so I've 13 in perforce at the moment). I probably won't >create new patch, but just commit what I've to HEAD. In the meantime >also I fixes quite a few bugs, mostly reported by kris@. It's now somewhat over two months later and the latest ZFS patchset still appears to be zfs_20080727.patch.bz2. Unfortunately, these patches no longer apply to -current (I tried working through the rejects but must have missed something because I wound up with an unkillable running process). Can you please give us an indication as to when we might expect to see either an updated set of ZFS patches (or, better, the patches committed to -current). --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --PNTmBPCT7hxwcZjr Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkLaAYACgkQ/opHv/APuIcqcQCeOIcBtNvpNjFJvDDn3Gh8xZEL I8sAoJ7JPIdL1pdaahcb4bO/i1dX7WSF =qouH -----END PGP SIGNATURE----- --PNTmBPCT7hxwcZjr-- From owner-freebsd-fs@FreeBSD.ORG Sat Nov 1 23:16:13 2008 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 066DD1065686 for ; Sat, 1 Nov 2008 23:16:13 +0000 (UTC) (envelope-from glavoie@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.226]) by mx1.freebsd.org (Postfix) with ESMTP id CD7EC8FC16 for ; Sat, 1 Nov 2008 23:16:12 +0000 (UTC) (envelope-from glavoie@gmail.com) Received: by rv-out-0506.google.com with SMTP id g9so656673rvb.4 for ; Sat, 01 Nov 2008 16:16:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=mrFwrhfWpk+66F4UF5uWoPMm08HyzpB4TzbhL5dPCKs=; b=l3N43O5n6Jk7kzSeuN8ikK/rgAWhox6GukU/4410Mf+d761UKStb5JHovd+CoTutPO TJK4uc/EzY3nNvGxFx2Ouv/LmqmDp1/e8nxrc2oE8jkNVQEPNu7iMuxt7iZOLPlJIk+B E/Jpm05gXwHPygTxNiBbBRh2P4/mYvIclxzjs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=hqvLk5d/HPTBTMWb67pKYyTWOQLF59QjCX7+2CgeYgILAlyHKy2U8mx7Ol02b+mjLF +q2ntn+2774GFO4IF7QJDrhSXYgU5hrG1E1Y5VeoyV0VlBlEtT1tGn2etExTyzh5fRNB 0wz2qCEpKeyyu0+osN0wmpgO8FSYsd6cNp580= Received: by 10.141.185.3 with SMTP id m3mr7788366rvp.40.1225579926212; Sat, 01 Nov 2008 15:52:06 -0700 (PDT) Received: by 10.141.146.8 with HTTP; Sat, 1 Nov 2008 15:52:06 -0700 (PDT) Message-ID: Date: Sat, 1 Nov 2008 18:52:06 -0400 From: "Gabriel Lavoie" To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: FreeBSD 7.0: gjournal on root filesystem problems 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: Sat, 01 Nov 2008 23:16:13 -0000 Hello, I'm currently making some test to know how to setup a new home fileserver using two 500GB hard drives. I want to create a gmirror/gjournal setup on the complete filesystem. I've been able to setup everything and it works well. Now the problem I have is with the failure test. I create a file with random data on the / filesystem using "dd" and while whe file is being created, I hit the reset button of the computer. Now, it won't boot anymore... I get the following message: GEOM_MIRROR: Device mirror/gm launched (2/2) GEOM_JOURNAL: Journal 3672855181: mirror/gma contains data. GEOM_JOURNAL: Journal 3672855181: mirror/gma contains journal. GEOM_JOURNAL: Journal 3868799910: mirror/gmd contains data. GEOM_JOURNAL: Journal 3868799910: mirror/gmd contains journal. GEOM_JOURNAL: Journal mirror/gmd consistent. Trying to mount root from ufs:/dev/mirror/gma.journal Manual root filesystem specification: : Mount using filesystem eg. ufs:da0s1a ? List valid disk boot devices Abort manual input mountroot> ? List of GEOM managed disk devices: mirror/gmd.journal mirror/gmd mirror/gmc mirror/gma mirror/gm ad10s1c ad10s1b ad8s1c ad8s1b ad10s2 ad10s1 ad8s1 ad10 ad8 acd0 If I boot on the FixIt CD and I try to mount the device, it tells me that it isn't clean and that I must run fsck on it. I do it then I try to mount it again, everything is now OK and now the system will boot again. If I do the same thing on my /usr filesystem (writing random data then reset), there is no problem. The difference is that the GEOM_JOURNAL messages on boot tells me that the journal is consistent instead of clean. When the journalized filesystem isn't clean, I also noticed that "gjournal list" gives me the following line on the provider: Mode: r0w0e0 instead of this line: Mode: r1w1e1 Is it possible that the kernel becomes unable to mount the filesystem read-only to access fsck then remount it read-write to boot the rest of the system when this happens? Here is my configuration. Take note that this setup isn't optimal and I'm making it for testing purpose before making the real thing: /etc/fstab: # Device Mountpoint FStype Options Dump Pass# /dev/ad10s1b none swap sw 0 0 /dev/ad8s1b none swap sw 0 0 /dev/mirror/gma.journal / ufs rw,async 1 1 /dev/mirror/gmd.journal /usr ufs rw,async 2 2 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 /boot/loader.conf geom_mirror_load="YES" geom_journal_load="YES" headless# gmirror status Name Status Components mirror/gm COMPLETE ad8s2 ad10s2 headless# gmirror list Geom name: gm State: COMPLETE Components: 2 Balance: split Slice: 4096 Flags: NOFAILSYNC GenID: 0 SyncID: 1 ID: 1602936318 Providers: 1. Name: mirror/gm Mediasize: 4293595648 (4.0G) Sectorsize: 512 Mode: r2w2e3 Consumers: 1. Name: ad8s2 Mediasize: 4293596160 (4.0G) Sectorsize: 512 Mode: r1w1e1 State: ACTIVE Priority: 0 Flags: HARDCODED GenID: 0 SyncID: 1 ID: 2559388791 2. Name: ad10s2 Mediasize: 4293596160 (4.0G) Sectorsize: 512 Mode: r1w1e1 State: ACTIVE Priority: 0 Flags: HARDCODED GenID: 0 SyncID: 1 ID: 1481264275 headless# gjournal status Name Status Components mirror/gma.journal N/A mirror/gma mirror/gmd.journal N/A mirror/gmd headless# gjournal list Geom name: gjournal 3672855181 ID: 3672855181 Providers: 1. Name: mirror/gma.journal Mediasize: 1073741312 (1.0G) Sectorsize: 512 Mode: r1w1e1 Consumers: 1. Name: mirror/gma Mediasize: 2147483648 (2.0G) Sectorsize: 512 Mode: r1w1e1 Jend: 2147483136 Jstart: 1073741312 Role: Data,Journal Geom name: gjournal 3868799910 ID: 3868799910 Providers: 1. Name: mirror/gmd.journal Mediasize: 1072361472 (1.0G) Sectorsize: 512 Mode: r1w1e1 Consumers: 1. Name: mirror/gmd Mediasize: 2146103808 (2.0G) Sectorsize: 512 Mode: r1w1e1 Jend: 2146103296 Jstart: 1072361472 Role: Data,Journal headless# mount /dev/mirror/gma.journal on / (ufs, asynchronous, local, gjournal) devfs on /dev (devfs, local) /dev/mirror/gmd.journal on /usr (ufs, asynchronous, local, gjournal) Thanks Gabriel Lavoie -- Gabriel Lavoie glavoie@gmail.com