From owner-freebsd-fs@FreeBSD.ORG Sun Nov 11 00:29:26 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 28AE1CC for ; Sun, 11 Nov 2012 00:29:26 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id D60168FC0A for ; Sun, 11 Nov 2012 00:29:25 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap4EAPbvnlCDaFvO/2dsb2JhbABEhhm+Q4IeAQEEASMEUgUWDgoCAg0ZAlkGiBcGqgmRdoEikCqBEwOIWo0ikEODDYF7 X-IronPort-AV: E=Sophos;i="4.80,755,1344225600"; d="scan'208";a="187477971" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 10 Nov 2012 19:29:19 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 1D876B408C; Sat, 10 Nov 2012 19:29:19 -0500 (EST) Date: Sat, 10 Nov 2012 19:29:19 -0500 (EST) From: Rick Macklem To: Xavier Beaudouin Message-ID: <985721960.220092.1352593759104.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: Subject: Re: 9.0-RELEASE-p4 + NFS + ZFS = issues... :/ (probably a memory leak) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.202] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Nov 2012 00:29:26 -0000 Xavier Beaudouin wrote: > Hi Rick, > > I did several nfs mount using the udp patch you gave me and also TCP > mount instead. > > Seem with vmstat -m that : > > NFS fh 1 1K - 342087 64 > > Is going to growing and growing. > It is the first numeric field called "InUse" that indicates how many are currently allocated. The above line indicates "1". Are you saying that field keeps ratcheting up? (342087 is just how many times a malloc of this type has happened. It will normally keep increasing.) For "vmstat -z", it is the 3rd numeric field called "INUSE" that would keep increasing, if there was a leak. If no NFS related items are ratcheting up for the fields mentioned above, then there isn't a malloc() or uma_zalloc() leak. --> Probably a ZFS issue and know nothing about ZFS. (I wouldn't know a zpool, if it jumped up and bit me on the nose;-) Hopefully some ZFS guys may jump in with suggestions on what to check, rick > Umounting the nfs mount free some memory and I getting free memory > again. > > Seems that : > > rsync -r -v -p -o -g --times --specials --delete --exclude=.snapshot > /mnt/ /vol/hosting/ > > is raising this issue on my own (on case B, see previous mails). > > Any another hints? > > /Xavier