From owner-freebsd-fs@FreeBSD.ORG Thu Nov 8 14:53:17 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 9499AAC1 for ; Thu, 8 Nov 2012 14:53:17 +0000 (UTC) (envelope-from kiwi@oav.net) Received: from mail03.oav.net (mail03.oav.net [IPv6:2001:67c:ec:100::25:3]) by mx1.freebsd.org (Postfix) with ESMTP id 19A1F8FC14 for ; Thu, 8 Nov 2012 14:53:17 +0000 (UTC) Received: from amavis2.local.oav.net (unknown [IPv6:2001:67c:ec:100::25:42]) by mail03.oav.net (Postfix) with ESMTP id 1FD9661C4D; Thu, 8 Nov 2012 15:53:16 +0100 (CET) (envelope-from kiwi@oav.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=oav.net; h= content-transfer-encoding:content-type:content-type:in-reply-to :references:subject:subject:mime-version:user-agent:from:from :date:date:message-id:received:received; s=a; t=1352386389; x= 1354200790; bh=8rZzh5CYxUZZCz56QGO1q6p/qtrltf+eSHjDZvyA6QY=; b=D rUNBYvqQQa3icwEd8CO6Ez6Wx8WDDrlQt+U1npT1GJDzvcIJJsJ5RfocWQ2GRgZ4 nqjnv4RQodqReVrWVwyKY+UqTS1insgbIUvkbJIpQQWMIOMwIQtorCzzOhSV3VWo FM4s800vh7msvL/PSg/cudOnmh+4gYL1YQS3Z+4LqE= X-Virus-Scanned: Amavisd-new at amavis2.local.oav.net.local.oav.net Received: from mail01.oav.net ([172.31.1.1]) by amavis2.local.oav.net (amavis2.local.oav.net [172.31.1.42]) (amavisd-new, port 10026) with LMTP id LxfuBJ1jI78V; Thu, 8 Nov 2012 15:53:09 +0100 (CET) Received: from calchas.nic.fr (calchas.tech.ipv6.nic.fr [IPv6:2001:67c:2219:7::86:40]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: kiwi@oav.net) by mail01.oav.net (Postfix) with ESMTPSA id D872161C5D; Thu, 8 Nov 2012 15:53:09 +0100 (CET) (envelope-from kiwi@oav.net) Message-ID: <509BC6A1.9040102@oav.net> Date: Thu, 08 Nov 2012 15:50:09 +0100 From: Xavier Beaudouin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121031 Thunderbird/16.0.2 MIME-Version: 1.0 To: Rick Macklem Subject: Re: 9.0-RELEASE-p4 + NFS + ZFS = issues... :/ (probably a memory leak) References: <1066915051.120042.1352382998672.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <1066915051.120042.1352382998672.JavaMail.root@erie.cs.uoguelph.ca> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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: Thu, 08 Nov 2012 14:53:17 -0000 Hi Rick, (...) >> Issue is comming when copying from a netapp to this machine a 70G data >> with bunch of big files (eg 600M ~ 8G) and web files. >> >> All NFS clients use NFSv3 and UDP. >> > There is this patch for NFSv3 over UDP: > http://people.freebsd.org/~rmacklem/udp-timer.patch > (It applies to both NFS clients, since it is krpc related.) > I can't remember what the implications of not having this patch is, but > if the client retries NFS RPCs too agressively, it could use a lot of > DRC storage (mbuf clusters mainly) in the NFS server (if the NFS server > is a FreeBSD box). > OR > Try the mounts using TCP and see if the problem goes away. I will try this patch. :) TCP mount... gave me usualy lots of pain (but this is my own experience...) Is there really improovments with tcp ? :) > If it is slow leak, doing "vmstat -z" and "vmstat -m" while the system > is getting constipated might show what is leaking. Will try this patch. Maybe this will fix it... I keep you in touch. >> Tried : >> >> nfs client netapp and freebsd on the same machine : 1srt rsync from >> netapp to freebsd ok : no issue, second rsync : memory leak, swap is >> used (about less than 100Mb, but this trigger the bug. >> >> nfs client of the netapp is the "filer" machine, and the destination >> is >> local zfs spool. The rsync to make up to date data trigger as well the >> issue. >> > I'll admit you lost me w.r.t. what is the NFS client and what is the > NFS server. (Does "netapp" refer to a Netapp Filer or a FreeBSD box?) > I'm not sure that matters, except that it isn't obvious to me if the > leak you are referring to is in the NFS client or NFS server? I was a bit unclear. Sorry :) So let me rephrase :) Scenario A : Netapp server -> FreeBSD 8.x NFS Client -> FreeBSD 9.0-p4 server w/ ZFS Scenario B : Netapp server -> FreeBSD 9.0-p4 server w/ ZFS as NFS client I wanted on my own to remoce the part : the nfs server on freeBSD 9.0-p4 is leaking memory. Will try the udp patch and report. Kind regards, Xavier