[pnfs] October Bakeathon and Vestigial Locking Infrastructure From V4.0
William A. (Andy) Adamson
andros at citi.umich.edu
Thu Sep 13 16:08:30 EDT 2007
Just a note that draft-ietf-nfsv4-minorversion1-13.txt has not changed the
draft-ietf-nfsv4-minorversion10.txt language concerning the requriement to
zero sequence id's and client id's in existing operations related to locking
(OPEN, LOCK, LOCKU, etc).
Since the October Bakeathon uses draft-ietf-nfsv4-minorversion1-13.txt, we
expect this behaviour. Maybe I missed something - but I thought that at the
Austin bakeathon it was decided that the server could ignore vestigial
locking sequence id and client ids....
-->Andy
More information about the pNFS
mailing list