1 Nov
2005
1 Nov
'05
18:45
G'd day everyone, Just found interesting bug from 10.0. Don't know yet why, but seems that on this system kernel nfsd deadlocks kernel right after system has been booted. Latest thing seen in syslog from nfsd: kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory kernel: NFSD: recovery directory /var/lib/nfs/v4recovery doesn't exist kernel: NFSD: starting 90-second grace period WTF? Was this defaulting to highly broken NFSv4? Well that most certainly would explain it. There was nothing on console about this and once the system locks up, it does not even respond to sysRq. So not even interrupts are running anymore. Deadlocking from atomic context? -- // Janne