First the second problem. If I use "chmod 0000 dummyfile" I am still able to read and write the file (execution is not possible) with nfs4. Using nfs a "Permission denied" message occurs, which would be the right thing (in my opinion). I don't know if it is a config error or a bug in nfs4 or if it is only a feature I don't understand. The first problem: I know it is not very sophisticated to use "/etc/init.d/nfs restart" instead of "/etc/init.d/nfs", when a lot of people have files open on the server, but things happen and then nfs should be able to restart itself without a message "BUG". I don't know if it is fixed in kernel 2.6.18 (if it is a kernel bug). nfs-utils version is 1.0.10 The messages from /var/log/messages are appended. /proc/version is Linux version 2.6.17-gentoo-r5 (root@) (gcc version 3.4.6 (Gentoo 3.4.6-r1, ssp-3.4.5-1.0, pie-8.7.9)) #1 SMP Wed Aug 16 15:29:30 CEST 2006 Sep 28 10:52:50 slab error in kmem_cache_destroy(): cache `nfsd4_files': Ca n't free all objects Sep 28 10:52:50 Sep 28 10:52:50 Call Trace: <ffffffff80274ae1>{kmem_cache_destroy+174} Sep 28 10:52:50 <ffffffff8030c2aa>{nfsd4_free_slab+17} <ffffffff8030c2f8>{n fsd4_free_slabs+26} Sep 28 10:52:50 <ffffffff80310343>{nfs4_state_shutdown+451} <ffffffff802f61 01>{nfsd+0} Sep 28 10:52:50 <ffffffff802f6412>{nfsd+785} <ffffffff8020a70e>{child_rip+8 } Sep 28 10:52:50 <ffffffff802f6101>{nfsd+0} <ffffffff802f6101>{nfsd+0} Sep 28 10:52:50 <ffffffff8020a706>{child_rip+0} Sep 28 10:52:50 BUG: warning at fs/nfsd/nfs4state.c:1016/nfsd4_free_slab() Sep 28 10:52:50 Sep 28 10:52:50 Call Trace: <ffffffff8030c2f8>{nfsd4_free_slabs+26} Sep 28 10:52:50 <ffffffff80310343>{nfs4_state_shutdown+451} <ffffffff802f61 01>{nfsd+0} Sep 28 10:52:50 <ffffffff802f6412>{nfsd+785} <ffffffff8020a70e>{child_rip+8 } Sep 28 10:52:50 <ffffffff802f6101>{nfsd+0} <ffffffff802f6101>{nfsd+0} Sep 28 10:52:50 <ffffffff8020a706>{child_rip+0} Sep 28 10:52:50 slab error in kmem_cache_destroy(): cache `nfsd4_delegation s': Can't free all objects Sep 28 10:52:50 Sep 28 10:52:50 Call Trace: <ffffffff80274ae1>{kmem_cache_destroy+174} Sep 28 10:52:50 <ffffffff8030c2aa>{nfsd4_free_slab+17} <ffffffff80310343>{n fs4_state_shutdown+451} Sep 28 10:52:50 <ffffffff802f6101>{nfsd+0} <ffffffff802f6412>{nfsd+785} Sep 28 10:52:50 <ffffffff8020a70e>{child_rip+8} <ffffffff802f6101>{nfsd+0} Sep 28 10:52:50 <ffffffff802f6101>{nfsd+0} <ffffffff8020a706>{child_rip+0} Sep 28 10:52:50 BUG: warning at fs/nfsd/nfs4state.c:1016/nfsd4_free_slab() Sep 28 10:52:50 Sep 28 10:52:50 Call Trace: <ffffffff80310343>{nfs4_state_shutdown+451} Sep 28 10:52:50 <ffffffff802f6101>{nfsd+0} <ffffffff802f6412>{nfsd+785} Sep 28 10:52:50 <ffffffff8020a70e>{child_rip+8} <ffffffff802f6101>{nfsd+0} Sep 28 10:52:50 <ffffffff802f6101>{nfsd+0} <ffffffff8020a706>{child_rip+0} Sep 28 10:52:50 kmem_cache_create: duplicate cache nfsd4_files Sep 28 10:52:50 Sep 28 10:52:50 Call Trace: <ffffffff80275832>{kmem_cache_create+1107} Sep 28 10:52:50 <ffffffff80310050>{nfs4_state_start+82} <ffffffff802f5ef3>{ nfsd_svc+93} Sep 28 10:52:50 <ffffffff802f6abd>{write_threads+131} <ffffffff8025930d>{ge t_zeroed_page+31} Sep 28 10:52:50 <ffffffff8029754b>{simple_transaction_get+143} <ffffffff802 f663e>{nfsctl_transaction_write+78} Sep 28 10:52:50 <ffffffff80278a16>{vfs_write+175} <ffffffff80278b65>{sys_wr ite+69} Sep 28 10:52:50 <ffffffff802098c2>{system_call+126} Sep 28 10:52:50 nfsd[6598]: nfssvc: Cannot allocate memory Sep 28 10:52:50 rc-scripts: Error starting NFS daemon Sep 28 10:53:22 mountd[6604]: Caught signal 15, un-registering and exiting.
nothing you do in userspace should cause a trace in the kernel; this is a kernel bug ...
*** Bug 149493 has been marked as a duplicate of this bug. ***
Please reproduce on gentoo-sources-2.6.18
Actually, make that the latest development kernel (currently 2.6.19-rc1)
See comment #4. The usual process is to reproduce this on the latest development kernel and then file a bug at http://bugzilla.kernel.org
