From owner-freebsd-fs@FreeBSD.ORG Fri Oct 26 21:30:48 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 165627EC for ; Fri, 26 Oct 2012 21:30:48 +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 C285E8FC08 for ; Fri, 26 Oct 2012 21:30:47 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap4EAOL/ilCDaFvO/2dsb2JhbABEhhi9RoIeAQEFIyYwGw4KAgINGQIjNgYThhCBZAMPC6lpiQANiVSBIIlqZ4VbgRMDlB6BVYEXiheFEIMLgUgXHg X-IronPort-AV: E=Sophos;i="4.80,657,1344225600"; d="scan'208";a="185386444" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 26 Oct 2012 17:30:40 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id EB7EBB4041; Fri, 26 Oct 2012 17:30:40 -0400 (EDT) Date: Fri, 26 Oct 2012 17:30:40 -0400 (EDT) From: Rick Macklem To: Yamagi Burmeister Message-ID: <1276463871.2926827.1351287040945.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <20121026082840.0e909c4ea1c694ac99ef39d9@yamagi.org> Subject: Re: Can not read from ZFS exported over NFSv4 but write to it MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.201] 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: Fri, 26 Oct 2012 21:30:48 -0000 Yamagi Burmeister wrote: > On Fri, 26 Oct 2012 15:15:08 -0700 > YongHyeon PYUN wrote: > > > On Fri, Oct 26, 2012 at 08:07:27AM +0200, Yamagi Burmeister wrote: > > > On Fri, 26 Oct 2012 10:38:47 -0700 > > > YongHyeon PYUN wrote: > > > > > > > Thanks the info. > > > > Would you try attached patch? > > > > > > Still the same problem. With TSO enabled, the NFS4 mount > > > stalls when writing to it. Without it works as aspected. > > > > I have no longer access to age(4) controller so it's hard to verify > > the issue on my box. > > Can you post an URL for captured packets on both sender(age(4)) and > > receiver side with tcpdump? > > http://deponie.yamagi.org/freebsd/misc/age0_pcap.tar.xz > > sender_age0.pcap is the age0 device on the NFS4 server. > receiver_em0.pcap is a em0 NIC on the NFS4 client. > > Those files were created by: > 1. Mount the NFS4 export on the client > 2. Try to copy a file onto it. > 3. Forcefully unmount the NFS4 export on the client > I took a look at the packet traces and all that seems to be on them are a couple of OPEN attempts which reply NFS4ERR_GRACE. This is normal. After starting an NFSv4 server, it remains in a Grace period (where it will only handle lock state recovery operations) for greater than a lease duration. After the lease duration (2 minutes for a FreeBSD server), it will allow other operations like non-reclaim OPENs. I'd suggest you wait at least 2 minutes after doing the mount, before you try to do a file copy (or wait several minutes after starting the first file copy before assuming it is hung). Once Grace is over, the server will no longer reply NFS4ERR_GRACE until it is rebooted. If you capture packets again, but wait 5 minutes before doing the "umount -f", we should be able to see what is going on. rick > -- > Homepage: www.yamagi.org > XMPP: yamagi@yamagi.org > GnuPG/GPG: 0xEFBCCBCB