Comment 9 for bug 50558

I can confirm it still occurs on feisty.
I've looked at what goes on with wireshark on 'lo'; something somewhere is doing a
portmap

  [Program Version: 2]
  [V2 Procedure: SET (1)]
  Program: NLM (100021)
  Version: 1
  Proto: TCP (6)
  Port: 38824

Which gave me an idea - it is locking related; adding -onolock makes the mount succeed in a few seconds.

I don't think I could argue for starting portmap by default - that would be insecure; but I think mount's behaviour without a local portmap should be more reasonable.

Dave