From owner-freebsd-fs@FreeBSD.ORG Mon Apr 14 14:00:46 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DBF7CB04; Mon, 14 Apr 2014 14:00:46 +0000 (UTC) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 61C591A91; Mon, 14 Apr 2014 14:00:45 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqUEAHrpS1ODaFve/2dsb2JhbABZg0FXgxC4W4ZkUYE4dIIlAQEBAwEBAQEgKyALBRYYAgINGQIpAQkmDgcEARwEh1MIDahZolMXgSmMYxACARs0BxaCWYFJBJYJhA6RDYNNITGBPQ X-IronPort-AV: E=Sophos;i="4.97,857,1389762000"; d="scan'208";a="114284475" Received: from muskoka.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.222]) by esa-annu.net.uoguelph.ca with ESMTP; 14 Apr 2014 10:00:17 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 3F114B4069; Mon, 14 Apr 2014 10:00:17 -0400 (EDT) Date: Mon, 14 Apr 2014 10:00:17 -0400 (EDT) From: Rick Macklem To: araujo@FreeBSD.org Message-ID: <936380350.10694814.1397484017247.JavaMail.root@uoguelph.ca> In-Reply-To: Subject: Re: NFSv4: prob err=10036 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.209] X-Mailer: Zimbra 7.2.1_GA_2790 (ZimbraWebClient - FF3.0 (Win)/7.2.1_GA_2790) Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Apr 2014 14:00:46 -0000 Marcelo Araujo wrote: > Hi all, > > Anyone have saw this prob err before when try to mount a NFSv4? > > machine_a# mount -t nfs -o nfsv4 192.168.2.100:/a /mnt/ > machine_a# mount_nfs: /mnt, : Input/output error > machine_a# tail /var/log/messages |grep nfsv4 > Apr 13 17:03:33 ESSD46B6E kernel: nfsv4 client/server protocol prob > err=10036 > Well, 10036 is NFSERR_BADXDR (they are all in sys/fs/nfs/nfsproto.h). This means that the server didn't like the RPC message presented to it. (I have no idea why that would be the case for machine_a?) If you capture packets while attempting the mount, you can look at them in wireshark and maybe see how they are trashed? (I just got home, so I can take a look at a packet capture, if you email it to me as an attachment.) # tcpdump -s 0 -w mnt.pcap host 192.168.1.100 - run on machine_a during the mount attempt, should do it (in mnt.pcap). rick > I have another machine with the same settings that can mount > successfully > the same NFSv4 share. > > machine_c# mount -t nfs -o nfsv4 192.168.2.100:/a /mnt/ > machine_c# > > Best Regards, > -- > Marcelo Araujo > araujo@FreeBSD.org > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >