From owner-freebsd-fs@FreeBSD.ORG Fri Aug 3 00:03:10 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 9590E106564A for ; Fri, 3 Aug 2012 00:03:10 +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 4CF0F8FC0C for ; Fri, 3 Aug 2012 00:03:09 +0000 (UTC) Received: from secure.linguamatics.com (guardian.linguamatics.com [10.252.2.1]) by mail.linguamatics.com (Postfix) with ESMTPS id 34D5EEFB44C for ; Fri, 3 Aug 2012 01:03:07 +0100 (BST) Received: from [10.252.2.234] (vpn.abogar.linguamatics.com [10.252.2.234]) by secure.linguamatics.com (Postfix) with ESMTP id 48EB28187 for ; Fri, 3 Aug 2012 01:11:12 +0100 (BST) Message-ID: <501B153A.4060408@linguamatics.com> Date: Fri, 03 Aug 2012 01:03:06 +0100 From: =?ISO-8859-1?Q?Attila_Bog=E1r?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0 MIME-Version: 1.0 To: freebsd-fs@FreeBSD.org Content-Type: multipart/mixed; boundary="------------000301090200080809090802" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: 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: Fri, 03 Aug 2012 00:03:10 -0000 This is a multi-part message in MIME format. --------------000301090200080809090802 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, I have an nfs server called "server" in this scenario. This server is running 9.1-PRERELEASE and exports 70+ zfs datasets over NFSv3. I sent an email a month ago, that half of the krb5i mounts fails over tcp. I noticed, that with simple krb5 sec flavour fever of the mounts are failing. I expected, that with sec=sys none will fail. Unfortunately this is not the case. I can get a failed mount with sec=sys to within 2 minutes. See the attached bash script. Within 2 minutes I always get this: mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: trying 10.1.2.3 prog 100003 vers 3 prot TCP port 2049 mount.nfs: prog 100005, trying vers=3, prot=6 mount.nfs: trying 10.1.2.3 prog 100005 vers 3 prot TCP port 719 mount.nfs: mount(2): Input/output error mount.nfs: mount system call failed As soon as I have some time, I'll hook a wireshark and see the trace, what's going on the wire. If you have any ideas how to approach this, please do not hesitate to tell me. Thanks, Attila --------------000301090200080809090802--