up vote 1 down vote favorite
share [g+] share [fb]

Hi is there a way to restart the lockd kernel thread (NFS lock manager)? There were some file locking requests which went wrong and since then it consumes about 50% of CPU. The processes requiring those locks are killed.

Also enabling NLM debug shows me this in logs:

Jan 14 16:50:27 backend2 kernel: [677200.130257] lockd: unlock failed (err = 13)
Jan 14 16:50:27 backend2 kernel: [677200.130260] lockd: request from 127.0.0.1, port=789
Jan 14 16:50:27 backend2 kernel: [677200.130262] lockd: rebind host localhost
link|improve this question
Nevermind. I have mounted a gluster expoted volume without nolock option. – Calin Don Jan 14 at 17:33
feedback

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown
discard

Browse other questions tagged or ask your own question.