Using bzr + nfsv4 i reproduce systematically ("bzr status" command non-interruptible even with kill -9. Using "umount -f ...." once or twice terminates bzr command).
I add log statements (logs added with 'mutter' are stored in ~/.bzr.log) in "show_tree_status" from status.py. It appears that this is the last statement of show_tree_status which block: "wt.unblock()" (http://bazaar.launchpad.net/~bzr-pqm/bzr/2.1/view/head:/bzrlib/status.py#L165).
Using bzr + nfsv4 i reproduce systematically ("bzr status" command non-interruptible even with kill -9. Using "umount -f ...." once or twice terminates bzr command). bazaar. launchpad. net/~bzr- pqm/bzr/ 2.1/view/ head:/bzrlib/ status. py#L165).
I add log statements (logs added with 'mutter' are stored in ~/.bzr.log) in "show_tree_status" from status.py. It appears that this is the last statement of show_tree_status which block: "wt.unblock()" (http://
Backtrace attached (done after "umount -f ..."). See https:/ /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/665082/ +attachment/ 1708220/ +files/ nfsbug2. txt too.