Bug 201155 - NFS4 exports are blocked when NIS master server is unreachable
Summary: NFS4 exports are blocked when NIS master server is unreachable
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 10.1-STABLE
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-fs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-27 23:14 UTC by Ahmed Kamal
Modified: 2025-02-10 23:34 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ahmed Kamal 2015-06-27 23:14:52 UTC 
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
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2025-02-10 23:34:08 UTC 
^Triage: to submitter: is this still a problem on supported versions of FreeBSD?