Date: Sat, 04 Aug 2012 10:22:14 +0100 From: =?UTF-8?B?QXR0aWxhIEJvZ8Ohcg==?= <attila.bogar@linguamatics.com> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: freebsd-fs@freebsd.org Subject: Re: NFS I/O or permission denied errors Message-ID: <501CE9C6.5010507@linguamatics.com> In-Reply-To: <773317506.298535.1344036483624.JavaMail.root@erie.cs.uoguelph.ca> References: <773317506.298535.1344036483624.JavaMail.root@erie.cs.uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?501CE9C6.5010507>