Share via

2.5.5.6 Open a File in an NFS File Share

  • Article

This use case supports the Two Applications Communicate via a Shared File use case (section 2.5.3). The application accesses a file using the NFS version 2 protocol [RFC1094], or the NFS version 3 protocol [RFC1813].

Context of Use: To open or create a file when the User has located a shared directory and wants to open or create a file in that directory using an NFS network access protocol.

Goal: To open or create a file in an NFS network share directory.

Actors

  • Application

  • File Client

  • NFS File Service

  • Authentication Service

  • Active Directory Service

Stakeholders

  • User

Preconditions

  • The client and server computers are configured in a domain.

  • An NFS file share has been created on the file server.

  • The User has located the path to the file on the NFS file share and has determined the desired open type (for example, "create a new file" or "open existing file").

Main Success Scenario

Trigger: Based on the User interaction, the Application determines whether to open or create a file in a target directory.

  1. The Application resolves the target directory using a set of LOOKUP requests as described in [RFC1094] section 2.2.5 or [RFC1813] section 2.5.3 to resolve each component of the path.

  2. The Application directs the file client to send a request to NFS File Service in order to accomplish one of the following options, depending upon the requested operation type. Each operation returns a file handle to the Application.

    •  (Create) Creation of the new file using the CREATE request as described in [RFC1094] section 2.2.10 or [RFC1813] section 3.3.8.

    •  (Open) Resolution of the file name (final path component) using the LOOKUP request as described in [RFC1094] section 2.2.5 or [RFC1813] section 3.3.

  3. The NFS File Service performs the create operation and returns a file handle to the Application.

Post Condition

A file is created or opened in an NFS network share directory.

 Extensions

  1. If an RPC time-out occurs, the application displays an error message, and the use case ends in failure.

  2. If an RPC authentication fails, the application displays an error message, and the use case ends in failure.

  3. If a protocol error code is returned from the NFS File Service, the Application displays an error message corresponding to the RPC error code returned, and the use case aborts.