I'm helping debug a problem where a Linux client (2.6.18 kernel) is talking to an AIX server. We see an issue where Linux is happily using the stateid issued by the server (other part only, does not include the sequence number): 47B2DD610000014100128042 and then occasionally uses a different stateid: 47B2DD610000014100148042 This stateid is the correct stateid + 20000, however, AIX accepted it (very odd). Interestingly, this alternate stateid is used in a close, which the AIX server also accepts, returning the following stateid: 47B2DD610000014100140042 which is the original stateid +20000 - 8000 It appears that somewhere the code is overlaying some flag bits onto the stateid. The weird part is that way before this, AIX suddenly complains about the original stateid with NFS4ERR_BAD_STATEID. The sequence number has not changed at all during this period. Apparently another trace does show the Linux client making this same corruption of the stateid, but in that case, the AIX server DOES complain. Any thoughts what might be going on here from a Linux perspective? Thanks Frank ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ NFS maillist - NFS@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that nfs@xxxxxxxxxxxxxxxxxxxxx is being discontinued. Please subscribe to linux-nfs@xxxxxxxxxxxxxxx instead. http://vger.kernel.org/vger-lists.html#linux-nfs -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
