Hello, should I be worried by these messages? Both nfs & nfsd seems to work, but on other side messages about nfsd4 being hung in D state for more than 480 seconds look suspicious. ============================================= [ INFO: possible recursive locking detected ] 2.6.28-64-06887-g85390a8-dirty #4 --------------------------------------------- nfsd4/4336 is trying to acquire lock: (&type->i_mutex_dir_key#2){--..}, at: [] vfs_fsync+0x84/0x100 but task is already holding lock: (&type->i_mutex_dir_key#2){--..}, at: [] nfsd4_sync_rec_dir+0x1d/0x50 [nfsd] other info that might help us debug this: 4 locks held by nfsd4/4336: #0: (nfsd4){--..}, at: [] run_workqueue+0xb3/0x250 #1: ((laundromat_work).work){--..}, at: [] run_workqueue+0xb3/0x250 #2: (client_mutex){--..}, at: [] laundromat_main+0x2e/0x300 [nfsd] #3: (&type->i_mutex_dir_key#2){--..}, at: [] nfsd4_sync_rec_dir+0x1d/0x50 [nfsd] ... INFO: lockdep is turned off. INFO: task nfsd4:4336 blocked for more than 480 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Thanks, Petr