[nfsv4] Out of sync stateid scenario that looks difficult to resolve

cburnett@us.ibm.com

Message-ID: <OF1D4D5531.5A1D9100-ON87256D9E.007A62A9@us.ibm.com>
From: Carl Burnett <cburnett@us.ibm.com>
Subject: [nfsv4] Out of sync stateid scenario that looks difficult to resolve
Date: Thu, 11 Sep 2003 17:30:54 -0500

Consider the following:

1. Client opens file for read.

2. Another process opens the (same) file for write (using same open owner 
as #1).

3. Server gets and processes the request (#2), but client never gets reply 
(RPC timeout, N/W condition, impatient user hits ^c with an interruptible 
mount).

4. Process from step 1 issues a read to the server. This will be done with 
the stateid from step 1, while the server thinks the correct stateid comes 
from step 2. The server will return an error (STALE_STATEID).

There seems to be no graceful way to recover from this condition where the 
server and client stateids are hopelessly out of sync. How does a client 
recover without producing errors to the application?

Carl Burnett
AIX Kernel Architecture - Network File System
(512) 838-8498, TL 678-8498
(please reply to cburnett@us.ibm.com)

_______________________________________________
nfsv4 mailing list
nfsv4@ietf.org
https://www1.ietf.org/mailman/listinfo/nfsv4