From owner-freebsd-fs@FreeBSD.ORG Sun Sep 1 18:28:47 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 57550ECB; Sun, 1 Sep 2013 18:28:47 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: from mail-vb0-x231.google.com (mail-vb0-x231.google.com [IPv6:2607:f8b0:400c:c02::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 050E62D91; Sun, 1 Sep 2013 18:28:46 +0000 (UTC) Received: by mail-vb0-f49.google.com with SMTP id w16so2466001vbb.36 for ; Sun, 01 Sep 2013 11:28:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=mp37uCeqZcyF51i7e2WinrPG+vYertUBdPq/AJHWJJs=; b=IpveykH85tegXcwn14GIwbHtXc2KaFCjAMXiD8yRzyiq4M1Xo15iWulo5xdC8ygmjD 3/3TEnFDefuXML8sORH09P4hOi9r/4LkhzFySFGS7ycEvammSkuYrgOobLmiArQgl5Pk Ct9c/VGEbXEXoo+jJTJmtlf29yaJPDGwstTYShLn6nVlPkl1+mLKafCozva+pdQxk+cH vw1covMxAiHlpkO25rPlUamSgqlD9r86b/zNr0BDWs8eCrqvlwXgv0M1iMjN8faBhpM5 KMaJz1FeYP2cw7cF6RYiIdsnb9cBGmITBfUSAAXDAydwawCqdlYUFtFsSnNtHTqecXlG 6UTA== MIME-Version: 1.0 X-Received: by 10.58.201.69 with SMTP id jy5mr265913vec.29.1378060125767; Sun, 01 Sep 2013 11:28:45 -0700 (PDT) Received: by 10.220.96.78 with HTTP; Sun, 1 Sep 2013 11:28:45 -0700 (PDT) In-Reply-To: <20130901181630.GB15654@gmail.com> References: <258054624.15907722.1377905324980.JavaMail.root@uoguelph.ca> <20130901181630.GB15654@gmail.com> Date: Sun, 1 Sep 2013 14:28:45 -0400 Message-ID: Subject: Re: NFS on ZFS pure SSD pool From: "Sam Fourman Jr." To: Mikolaj Golub Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD FS 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, 01 Sep 2013 18:28:47 -0000 On Sun, Sep 1, 2013 at 2:16 PM, Mikolaj Golub wrote: > On Fri, Aug 30, 2013 at 07:28:44PM -0400, Rick Macklem wrote: > > Sam Fourman Jr. wrote: > > > $ cat /var/log/messages | grep failed > > > Aug 30 10:22:20 students nfsd[1978]: accept failed: Software caused > > > connection abort > > > Aug 30 10:27:16 students nfsd[1978]: accept failed: Software caused > > > connection abort > > > Aug 30 11:46:30 students nfsd[1978]: accept failed: Software caused > > > connection abort > > > Aug 30 11:47:10 students nfsd[1978]: accept failed: Software caused > > > connection abort > > > > > Since the master socket that is accepting connections isn't being closed, > > I believe this error (ECONNABORTED returned by accept()) occurs when the > > client closes the new TCP connection before it has been accepted. Why > > would an NFS client do this? I have no idea. > > May be because nfsd is too slow accepting new connections and the > client aborts due to its timeout? May nfssvc(2) block for some > considerable time? > > Sam, you could monitor nfsd listen queue running netstat -nL > periodically and current client connections to nfsd with netstat -na, > to see what is going on. Also enabling ktrace on the nfsd process when > the issue is observed could tell if it is due to nfssvc(2) is slow. > > BTW, I noticed that nfsd sets listen backlog to 5. Isn't it a bit low > for servers that might have hundreds clients? > is there a sysctl to increase the listen backlog for nfsd? > > -- > Mikolaj Golub > -- Sam Fourman Jr.