On Mon, 2017-10-16 at 10:49 +0200, Stanislav Kinsburskiy wrote:
> Hi,
>
> We discovered an issue with NFSv4.0 mount.
> Server has crashed (or killed by OOM; it was Ganesha) on exclusive
> open-create operation after file was actually created, but no
> response was send to the client.
> Server was restarted (with grace period), and next clients attempt to
> create a file after server is ready fails with EEXIST.
> This is, probably, because for each open request client creates
> opendata and puts new jiffies value as the verifier (in
> nfs4_opendata_alloc) in the request.
> Does it sound like a client issue?
>
Hi Stanislav,
If it didn't receive a reply, the client should be reusing the same
opendata for the resend of the operation after state recover is
complete. Doesn't it?
--
Trond Myklebust
Linux NFS client maintainer, PrimaryData
trond.myklebust@xxxxxxxxxxxxxxx
��.n��������+%������w��{.n�����{��w��� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
