Weird Linux - FreeBSD/ZFS NFSv4 interoperability problem

Rick Macklem rmacklem at uoguelph.ca
Wed Sep 8 01:27:31 UTC 2010


> On Fri, Sep 3, 2010 at 5:55 PM, Rick Macklem <rmacklem at uoguelph.ca>
> wrote:
> >>
> >> Here's a capture for you. This is a Linux client (192.168.30.30)
> >> working against a FreeBSD 8.1-RELEASE server (192.168.30.102). If
> >> you
> >> need a capture using FreeBSD 9, that'll require some more setup on
> >> my
> >> part and I won't be able to get to it until Monday.
> >
> > Ok, The server is returning NFS4ERR_OLD_STATEID, which means that
> > the
> > seqid# inside the stateid is out of date. I think the original
> > intent
> > of this was to be a debugging aid for client writers, but a
> > discussion
> > on the nfsv4 mailing list pretty much concluded that it was useless.
> > (It is definitely the case that the server doesn't care. A separate
> > seqd# is used to order the open/lock/close ops.)
> >
> > So, please try the attached little patch that just disables the
> > server
> > check for this case for Close. (The line #s will be different than
> > 8.1, but all it is doing is commenting out the test for this case in
> > nfsrv_openupdate(), if the patch won't apply directly.)
> 
> This seems to have changed the problem. Now I get the following error
> during checkouts:
> 
> svn: In directory 'documentation/software-notes'
> svn: Can't copy
> 'documentation/software-notes/.svn/tmp/text-base/directory-server-install-notes.txt.svn-base'
> to
> 'documentation/software-notes/.svn/tmp/directory-server-install-notes.txt.tmp.tmp':
> Input/output error
> 
> I don't see any related errors in the syslog on the client or server.
> 
> This is on FreeBSD 8.1-RELEASE; I'm going to try to test with 9 later
> today.
> 
Ok, if you feel like emailing me another packet capture, I can look and
see where the EIO is being returned.

And good luck with testing the newer ZFS, rick



More information about the freebsd-fs mailing list