Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 15 Apr 2014 10:21:22 +0800
From:      Marcelo Araujo <araujobsdport@gmail.com>
To:        Rick Macklem <rmacklem@uoguelph.ca>
Cc:        "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org>
Subject:   Re: NFSv4: prob err=10036
Message-ID:  <CAOfEmZg9ejea%2B8Ab-cHS4Y99HZK-pK3kHD3o_Gih0y%2BQY0niJg@mail.gmail.com>
In-Reply-To: <936380350.10694814.1397484017247.JavaMail.root@uoguelph.ca>
References:  <CAOfEmZiUmm9eNww60W1K3EuY5jcfjuNP00h2tbAmEeP2y20GVA@mail.gmail.com> <936380350.10694814.1397484017247.JavaMail.root@uoguelph.ca>

next in thread | previous in thread | raw e-mail | index | archive | help
Hello Rick,

Thanks by the prompt reply, and I'm sorry my late reply, unfortunately I'm
located in Taiwan, so, timezone is an issue.

So here attached is my pcap.

Server IP: 172.17.32.42
Client IP: 172.17.32.54

Something related with RELEASE_LOCKOWNER, I'm still investigating, maybe I
can find a solution before you reply, if yes, I will post here.

Thanks again.


2014-04-14 22:00 GMT+08:00 Rick Macklem <rmacklem@uoguelph.ca>:

> 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"
> >
>



-- 
Marcelo Araujo
araujo@FreeBSD.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOfEmZg9ejea%2B8Ab-cHS4Y99HZK-pK3kHD3o_Gih0y%2BQY0niJg>