NFSv4 ID Status Spencer Shepler shepler@eng.sun.com ID Updates - - PowerPoint PPT Presentation
NFSv4 ID Status Spencer Shepler shepler@eng.sun.com ID Updates - - PowerPoint PPT Presentation
NFSv4 ID Status Spencer Shepler shepler@eng.sun.com ID Updates (0406) / Definition clarifications for data structures / nfs_lockowner state handling (release of) / Set access/modify time attributes / Recovery from lock request
I−D Updates (04−06)
/ Definition clarifications for data structures / nfs_lockowner state handling (release of) / Set access/modify time ’attributes’ / Recovery from lock request timeout/abort / UTF8 Normalization
I−D Updates cont’
/ OPEN_CONFIRM / SETCLIENTID_CONFIRM / OPEN_DOWNGRADE / Clarification for VERIFY/NVERIFY / Migration clarifications (LEASE_MOVED
error)
/ Volatile filehandle clarifications for
migration/rename
/ Misc: add stable storage definition
Draft 06 Updates
/ IETF last call ended on March 6th / LIPKEY RFC Reference and OID assignments / Error number additions for LINK, OPEN / VERIFY/NVERIFY redundant bitmasks
NFSv4 Implementation I−D
Spencer Shepler shepler@eng.sun.com
Filehandle construction
/ Persistent filehandle content / Volatile filehandle content / Tradeoffs between persistent/volatile /
I18N
/ Further Normalization discussion / Dealing with underlying filesystems that only
support single byte encodings
/
stateid/clientid
/ Content examples / Client choices for clientid / Server choices for stateid /
State management
/ State needed by server and client for correct
behavior
/ State the server can keep in non−volatile
memory to enable faster recovery
/ State the client can keep for faster recovery /
User id mappings
/ Mapping techniques for user/group strings / Integration with various naming services / Potential interoperability problems with mapping
techniques
/
Filesystem interfaces
/ Local OS FS interfaces and effect on NFSv4
client and server
/ Potential issues for correct NFSv4 behavior / Local access to filesystem at server /
NFSv2/NFSv3 interaction
/ Choices for NFSv4 and how will the various
servers interact
/ Interaction with other file server types /
Missing Attributes
/ Client behavior in the face of missing
recommended attributes
/ Choices for fabricating attributes /
Migration/Replication
/ Server responsibilities for mig/repl / Client choices for replica choices / Client responsibilities for migration /
ACL translation
/ Mapping suggestions or issues /
Locking/Leases
/ Handling servers that don’t support