From: "Jeremy Kusnetz" Subject: Chrooted BIND broke on NFS server between kernel 2.4.21 and 2.4.22 Date: Fri, 12 Dec 2003 14:37:35 -0500 Sender: nfs-admin@lists.sourceforge.net Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Return-path: Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.12] helo=sc8-sf-mx2.sourceforge.net) by sc8-sf-list2.sourceforge.net with esmtp (Exim 4.24) id 1AUt6c-0004ax-GB for nfs@lists.sourceforge.net; Fri, 12 Dec 2003 11:37:42 -0800 Received: from outmail.nrtc.org ([204.145.144.17] helo=exchange.nrtc.coop) by sc8-sf-mx2.sourceforge.net with esmtp (Exim 4.24) id 1AUt6c-0006FW-4Q for nfs@lists.sourceforge.net; Fri, 12 Dec 2003 11:37:42 -0800 To: Errors-To: nfs-admin@lists.sourceforge.net List-Unsubscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Post: List-Help: List-Subscribe: , List-Archive: 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? ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs