From owner-freebsd-fs@FreeBSD.ORG Sun Sep 1 18:16:36 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 AA19290A for ; Sun, 1 Sep 2013 18:16:36 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-ee0-x235.google.com (mail-ee0-x235.google.com [IPv6:2a00:1450:4013:c00::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3C7A02CF9 for ; Sun, 1 Sep 2013 18:16:36 +0000 (UTC) Received: by mail-ee0-f53.google.com with SMTP id b15so1914968eek.40 for ; Sun, 01 Sep 2013 11:16:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=X6Ae8IPXzxQRPmn8gZUOlvSMIusNslEJs5EJPNg03uI=; b=Xk5GcI0rwDgyzueFJhU61uEwJ5C2+Br5ZgknrGEgeJK8BOEHiRtkBKSeOieIL2qqvg Xq34q2qmW8DzFXeTVOAuU9AAOo3UCobHYbk+LlO0YDnOF04g7J9euPauC995TzdNtJVn IIaM2+xt+yiYz82BE87pEEE4lOyBqdhRkDYlhkXAKVZpro22D0eihJvEAz9wX4UEqak6 MQsQTng+UXNrMnvUUwYgOB+AVTcw7xA7ua2o97zphJ6BS11oFkTGiWEJ+VSWav5Muh18 zRBWgPC+R2yfrBaGZ9oVOCZp6E2FvNLCA3O3cmn5v4329G0sKiZJuNbxQodk+Ca7APq8 4HIQ== X-Received: by 10.14.115.133 with SMTP id e5mr30617731eeh.27.1378059394515; Sun, 01 Sep 2013 11:16:34 -0700 (PDT) Received: from localhost ([178.150.115.244]) by mx.google.com with ESMTPSA id b45sm15274066eef.4.1969.12.31.16.00.00 (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 01 Sep 2013 11:16:33 -0700 (PDT) Sender: Mikolaj Golub Date: Sun, 1 Sep 2013 21:16:31 +0300 From: Mikolaj Golub To: Rick Macklem Subject: Re: NFS on ZFS pure SSD pool Message-ID: <20130901181630.GB15654@gmail.com> References: <258054624.15907722.1377905324980.JavaMail.root@uoguelph.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <258054624.15907722.1377905324980.JavaMail.root@uoguelph.ca> User-Agent: Mutt/1.5.21 (2010-09-15) 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:16:36 -0000 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? -- Mikolaj Golub