Comment # 6 on bug 934202 from Neil Brown

Yes, it does help - thanks.

In frame 15164 the client opens a file called "agent-medusa" for read.
The server signal success and returns a "read delegation" as well (15165).
The client then reads from the file and closes it, still holding the
delegation.
The client then checks if "agent-medusa-ssh" exists, which it doesn't.
So the client wants to hard-link the agent-medusa file to the agent-medusa-ssh
name.
It knows that doing that will recall the delegation so it pro-actively starts
returning the delegation.
This involves looking through it's list of open files to see if one was opened,
without telling the server, on the strength of the delegation.
It seems that it finds one, because (frame 15172) it opens the file again
using the delegation, but opens it write-only!!  It shouldn't have a write-only
file from a read-only delegation.
This causes the error, as it should.

The LINK then happens, the server recalls the delegation as expected, and the
LINK completes.

So now I have to find out why the client thinks it has a write-only open on
that file....