From owner-freebsd-fs@FreeBSD.ORG Wed Aug 13 17:48:30 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 997F7106566B; Wed, 13 Aug 2008 17:48:30 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from ns1.jnielsen.net (ns1.jnielsen.net [69.55.238.237]) by mx1.freebsd.org (Postfix) with ESMTP id 514988FC08; Wed, 13 Aug 2008 17:48:30 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from max.local (rrcs-74-218-226-253.se.biz.rr.com [74.218.226.253]) (authenticated bits=0) by ns1.jnielsen.net (8.12.9p2/8.12.9) with ESMTP id m7DHmTVD008968; Wed, 13 Aug 2008 13:48:29 -0400 (EDT) (envelope-from lists@jnielsen.net) From: John Nielsen To: freebsd-current@freebsd.org Date: Wed, 13 Aug 2008 13:48:57 -0400 User-Agent: KMail/1.9.7 References: <20080727125413.GG1345@garage.freebsd.pl> <200807281139.45771.lists@jnielsen.net> In-Reply-To: <200807281139.45771.lists@jnielsen.net> X-Face: #X5#Y*q>F:]zT!DegL3z5Xo'^MN[$8k\[4^3rN~wm=s=Uw(sW}R?3b^*f1Wu*.<=?utf-8?q?of=5F4NrS=0A=09P*M/9CpxDo!D6?=)IY1w<9B1jB; tBQf[RU-R<,I)e"$q7N7 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200808131348.57683.lists@jnielsen.net> X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on ns1.jnielsen.net X-Virus-Status: Clean Cc: freebsd-fs@freebsd.org, Pawel Jakub Dawidek 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: Wed, 13 Aug 2008 17:48:30 -0000 On Monday 28 July 2008, John Nielsen wrote: > On Monday 28 July 2008, David Grochowski wrote: > > Hey, > > > > On Sun, Jul 27, 2008 at 11:24 PM, Adam McDougall > > wrote: > > > On Sun, Jul 27, 2008 at 02:54:13PM +0200, Pawel Jakub Dawidek wrote: > > > > Hi. > > > > > > > > > > > > http://people.freebsd.org/~pjd/patches/zfs_20080727.patch.bz2 > > > > > > Stop in /usr/src. > > > > I had the same issue. Try deleting > > "/usr/src/sys/cddl/compat/opensolaris/sys/acl.h" and > > "/usr/src/sys/cddl/compat/opensolaris/sys/callb.h" (make sure that > > these files have a length of zero first!). When patching, these files > > are supposed to be deleted, but were instead left as empty files. > > Since these files are included before the actual ones in > > "/usr/src/sys/cddl/contrib/opensolaris/uts/common/sys", this will > > cause a problem. > > > > Also, I would like to note that the patch has been working for me > > without any problems. > > Thanks for pointing this out David, I had been scratching my head too. > (Also thanks to those who posted reminders to use patch -p0). > > I'm now up and running with the patch and an upgraded zpool. No issues > thus far. I even tried to reproduce the UDP NFS write lockup issue I > reported recently and was unable to. Thanks PJD! I experienced a couple panics yesterday while working with some video files The panics didn't happen until after an hour or two of sustained activity (heavy reading and writing to/from multiple files about 2GB in size). The panic message (most recent) probably looks familiar: panic:kmem_malloc(65536): kmem_map too small: 757669888 total allocated This is on an i386 8-CURRENT box w/ the recent ZFS mega-patch applied: %uname -a FreeBSD stealth.jnielsen.net 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Mon Jul 28 09:17:49 EDT 2008 john@stealth.jnielsen.net:/usr/obj/usr/src8/src/sys/STEALTH i386 %zfs upgrade This system is currently running ZFS filesystem version 3. All filesystems are formatted with the current version. %zpool upgrade This system is currently running ZFS pool version 11. All pools are formatted using this version. The box has 1.25 GB RAM. The kernel is compiled with KVA_PAGES=384 and vm.kmem_size and kmem_size_max are set to 768M. Since the last panic I have set vfs.zfs.arc_max to 160M and I haven't gotten another one, but I haven't had the same sustained activity since then either. I'll keep an eye on it. Just thought I'd send a report since I'm not sure if this is still expected behavior with the new patch. I am of course also open to tuning suggestions, though I have read the wiki and kept up on the mailing lists and am willing to experiment to see what ends up working best for this system. Thanks, JN