lockd using up 60% CPU and won't let go
Subsystems (2)
Hi,
Quoted 1 line
It's basically just a userspace NFS server, right?
Correct.
Quoted 1 line
Could you work around the problem by mounting with -onolock?
That doesn't seem to help.
Quoted 1 line
You might try running wireshark on the "lo" interface and seeing whether there's any NLM traffic from lockd.
You guessed right. There's a 12 megabytes per second of NLM traffic on lo.
unlock call requests and unlock replies saying permission denied, looks like it just repeats forever in a tight loop.
Marc
Quoted 10 lines · Just Marc
Hi,
Quoted 1 line
It's basically just a userspace NFS server, right?
Correct.
Quoted 1 line
Could you work around the problem by mounting with -onolock?
That doesn't seem to help.
Quoted 7 lines
Quoted 1 line
You might try running wireshark on the "lo" interface and seeing
whether there's any NLM traffic from lockd.
You guessed right. There's a 12 megabytes per second of NLM traffic on lo.
unlock call requests and unlock replies saying permission denied, looks like it just repeats forever in a tight loop.
As Bruce said, you need to mount with -onolock. Please unmount _all_ your cfs partitions, then mount them again with -onolock.
Note that -oremount,nolock will not work and for some kernels, mounting while you have the same cfs partition mounted somewhere else will cause the kernel to use the 'old' mount options.
See /proc/mounts to find out which mount options the kernel is actually using.
Cheers
Trond
Quoted 10 lines · Just Marc
Hi,
Quoted 1 line
It's basically just a userspace NFS server, right?
Correct.
Quoted 1 line
Could you work around the problem by mounting with -onolock?
That doesn't seem to help.
Quoted 7 lines
Quoted 1 line
You might try running wireshark on the "lo" interface and seeing
whether there's any NLM traffic from lockd.
You guessed right. There's a 12 megabytes per second of NLM traffic on lo.
unlock call requests and unlock replies saying permission denied, looks like it just repeats forever in a tight loop.
Permission denied on an unlock sounds pretty weird--probably a bug on the server (CFS) side. The client might be able to handle it gracefully, but that's probably not a high priority.
So -onlock is the way to go; see Trond's suggestions. Locking will still work, CFS just won't be told about it. That would only be a problem if you had multiple NFS clients doing locking on the same CFS filesystem, but you're only loopback-mounting, so only one client is involved.
--b.