NFS4 exports are blocked when NIS master server is unreachable

Ahmed Kamal email.ahmedkamal at googlemail.com
Thu Jul 2 23:24:18 UTC 2015


I opened this ticket [
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201155] a week ago, but
haven't heard since. I thought to discuss it here. Here's a paste of the
bug for convenience. Thanks all!

My Setup is:
* A FreeBSD 10.1 with ZFS exporting NFS4 to a Linux server
* That Linux server is a NIS master for the FreeBSD box

The issue is:
* Upon power failure .. Both servers starting fresh
* FreeBSD boots faster (grin)
* FreeBSD doesn't find NIS master and bombards logs with hundreds of
thousands of messages!! like
  Jun 27 13:47:53 nas /usr/sbin/ypbind[827]: NIS server
[192.168.10.254] for domain "SIVISION" not responding
  Jun 27 13:48:24 nas last message repeated 51704 times
  Jun 27 13:49:26 nas last message repeated 104381 times
* In this state, FreeBSD does not allow any other machine to NFS4
mount its shares. This includes the NIS master Linux box
* Linux boot hangs waiting for the NFS share to allow it to mount it
* We are in a deadlock. Linux waiting for the NFS share to mount,
while FreeBSD is waiting for the NIS server on Linux to start


More information about the freebsd-fs mailing list