Unstable NFS on recent CURRENT

Paul Mather paul at gromit.dlib.vt.edu
Sun Mar 6 02:02:30 UTC 2016


On my BeagleBone Black running 11-CURRENT (r296162) lately I have been having trouble with NFS.  I have been doing a buildworld and buildkernel with /usr/src and /usr/obj mounted via NFS.  Recently, this process has resulted in the buildworld failing at some point, with a variety of errors (Segmentation fault; Permission denied; etc.).  Even a "ls -alR" of /usr/src doesn't manage to complete.  It errors out thus:

=====
[[...]]
total 0
ls: ./.svn/pristine/fe: Permission denied

./.svn/pristine/ff:
total 0
ls: ./.svn/pristine/ff: Permission denied
ls: fts_read: Permission denied
=====

On the console, I get the following:

newnfs: server 'chumby.chumby.lan' error: fileid changed. fsid 94790777:a4385de: expected fileid 0x4, got 0x2. (BROKEN NFS SERVER OR MIDDLEWARE)


I am using a FreeBSD/amd64 10.3-PRERELEASE (r296412) as the NFS server.  On the BeagleBone Black, I am mounting /usr/src and /usr/obj via /etc/fstab as follows:

chumby.chumby.lan:/build/src/head /usr/src nfs rw,nfsv4 0 0
chumby.chumby.lan:/build/obj/bbb /usr/obj nfs rw,nfsv4 0 0


/build/src/head and /build/obj/bbb are both ZFS file systems.

Has anyone else encountered this?  It has only started happening recently for me, it seems.  Prior to this, I have been able to do a buildworld and buildkernel successfully over NFS.

Cheers,

Paul.


More information about the freebsd-arm mailing list