Hello,
I have a cluster of machines running BIND that is chrooted on an NFS mounted partition.
I recently upgraded both my NFS server and clients to 2.4.23 due to the security issues. I was running 2.4.20 for my NFS server.
After doing this I found I could no longer start BIND, I would get the following error in syslog.
Dec 12 18:28:17 rs0 named[409]: errno2result.c:109: unexpected error:
Dec 12 18:28:17 rs0 named[409]: unable to convert errno to isc_result: 116: Stale NFS file handle
Dec 12 18:28:17 rs0 named[409]: none:0: open: /etc/named.conf: unexpected error
Dec 12 18:28:17 rs0 named[409]: loading configuration: unexpected error
Dec 12 18:28:17 rs0 named[409]: exiting (due to fatal error)
If I was cded into the chrooted etc directory I would get the following error after doing an ls
/bin/ls: .: Stale NFS file handle
If I cd out and back into the etc directory all works as expected, until I try to start bind again.
I tried downgrading my NFS server back to 2.4.20 and I was able to start bind as expected. Next I tried 2.4.22 and got the same stale NFS handle problem. I then tried 2.4.21 and I was able to start bind as expected.
So there must have been some change between 2.4.21 and 2.4.22 that broke this functionality. Any ideas?