From owner-freebsd-fs@FreeBSD.ORG Sat Aug 4 09:22:22 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 17DBD106564A for ; Sat, 4 Aug 2012 09:22:22 +0000 (UTC) (envelope-from attila.bogar@linguamatics.com) Received: from mail.linguamatics.com (mail.linguamatics.com [188.39.80.203]) by mx1.freebsd.org (Postfix) with ESMTP id C2B358FC17 for ; Sat, 4 Aug 2012 09:22:21 +0000 (UTC) Received: from secure.linguamatics.com (guardian.linguamatics.com [10.252.2.1]) by mail.linguamatics.com (Postfix) with ESMTPS id 5400DEFB44C; Sat, 4 Aug 2012 10:22:15 +0100 (BST) Received: from [10.252.2.234] (vpn.abogar.linguamatics.com [10.252.2.234]) by secure.linguamatics.com (Postfix) with ESMTP id 63E928187; Sat, 4 Aug 2012 10:30:26 +0100 (BST) Message-ID: <501CE9C6.5010507@linguamatics.com> Date: Sat, 04 Aug 2012 10:22:14 +0100 From: =?UTF-8?B?QXR0aWxhIEJvZ8Ohcg==?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0 MIME-Version: 1.0 To: Rick Macklem References: <773317506.298535.1344036483624.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <773317506.298535.1344036483624.JavaMail.root@erie.cs.uoguelph.ca> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: NFS I/O or permission denied errors X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Aug 2012 09:22:22 -0000 On 04/08/12 00:28, Rick Macklem wrote: > Oops, I didn't see that the client was a Linux one. I have no idea > what the semantics of a Linux "umount -f" is, although I'd still try > it without "-f" I was you. Thanks, - I tried with the force -f on the Linux and no change, I/O error within 2 mins. I captured the mount/umount requests with tshark and I can see no difference, how the FreeBSD nfs server responds to successful/failed mount requests. In fact the Linux is sending the FIN. Moreover, I could reproduce this between a CentOS 5.8 nfs server and a CentOS 6.3 nfs client. So I think this is a Linux bug - I'll try the linux-nfs@ mailing list to discuss this further. I'm not sure if this is the same bug as I get for the krb5 mounts (there the error message is permission denied), will make a tshark capture too with that. Thanks for the ideas, Attila