1 / 17

Sun Network File System

Sun Network File System. Presentation 3 Group A4 Sean Hudson, Syeda Taib, Manasi Kapadia. Problem. How can physically distributed computers share a file system?. Sun’s Network File System (NFS). Solution. Background. Developed by Sun. The NFS specification is platform independent:

finley
Download Presentation

Sun Network File System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Sun Network File System Presentation 3 Group A4 Sean Hudson, Syeda Taib, Manasi Kapadia

  2. Problem How can physically distributed computers share a file system?

  3. Sun’s Network File System (NFS) Solution

  4. Background • Developed by Sun. • The NFS specification is platform independent: • Portable • Operates in a heterogeneous environment.

  5. Fundamentals • NFS was developed to allow a machine to mount a disk partition on a remote machine as if it were local. • This allows for fast, seamless sharing of file across network. • There is no global naming hierarchy. • NFS allows any machine to be client or server.

  6. NFS Protocols • Mount Protocol • File Access Protocol • Their functionality is defined as a set of Remote Procedure Calls (RPC).

  7. Client Server home usr Request Dir1 Dir2 Open Local Mount Mount Protocol

  8. Mount Protocol (cont.) • After mount request, server returns a file handle (a key for further access). • Mount operation changes only the user’s view.

  9. Client Server RPC Calls • Search • Read/Write • Manipulate links/directories NFS Protocol

  10. Implementation • Three major layers of NFS architecture: • System Call layer: • This handles calls like OPEN, READ, and CLOSE. • Virtual File System (VFS) layer: • distinguishes local files from remote ones. • NFS service layer: • implements the RPC calls.

  11. Client Server System call layer Virtual file system layer Virtual file system layer Local OS NFS client NFS server Local OS Local disk Message to server Message from client Local disk Schematic view of NFS

  12. Pathname Translation • This is done by breaking the path into component names and performing a separate NFS lookup for every pair of component name and directory v-node. • Lookups are performed remotely by the server.

  13. Performance • Clients cache file attributes (i-nodes) and file data. • Cached data blocks and directories are discarded periodically. • When a cached file is open, the time it was last modified is checked at the server. If necessary, a new copy is brought from the server.

  14. Performance (cont.) • Servers keep a cache to reduce disk I/O. • Read-ahead caching • Write-behind caching • Periodically, modified cache blocks are written back to servers.

  15. Issues • Synchronization of file accesses are not well-defined. • Widely criticized for not implementing the UNIX semantics.

  16. Conclusion NFS is a simple, popular and widely used file system!

  17. References • Casvant, Thomas and Singhal, Mukesh. Distributed Computing Systems. IEEE Press. • Mullender, Sape. Distributed Systems. ACM Press. • Pradeep, Sinha K. Distributed Operating Systems. IEEE Computer Society Press. • Stallings, William. Operating Systems. • Tanenbaum, Andrew. Distributed Operating Systems.

More Related