We don't use networkmanager but configure the interfaces through /etc/network/interfaces all the time.. But we still have this problem.
I figured out, that autofs-mounts have the correct clientaddr set while fstab mounts don't. Our fstab-mounts also have clientaddr=0.0.0.0. But when I manually unmount them and remount them, they get the right clientaddr but still the problem exists, at least we still have the error-messages in dmesg shown. I also found this redhat bugreport https://bugzilla.redhat.com/show_bug.cgi?id=732748 which claims that the problem is fixed with these patches: http://article.gmane.org/gmane.linux.nfs/48705 . I used kernel 3.3.6-030306-generic now but we still have the "nfs4_reclaim_open_state: Lock reclaim failed!" messages in dmesg but no hang so far.. Does your workaround still work for you? Do you had any hangs or the error-messages in dmesg anymore? Does anyone know what the clientaddr-field is used for? ** Bug watch added: Red Hat Bugzilla #732748 https://bugzilla.redhat.com/show_bug.cgi?id=732748 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/932687 Title: nfs4_reclaim_locks: unhandled error crashes applications and creates high load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/932687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
