NFS Illustrated

NFS Illustrated

3.5 2
by Brent Callaghan
     
 

View All Available Formats & Editions

The Network File System (NFS) protocol that enables remote access to files is now a key element of any LAN. It is also currently and increasingly used as a key technology with the Web and wide area networks.

 

Written for programmers creating NFS-based applications, network engineers creating new implementations of NFS, and network managers,

See more details below

Overview

The Network File System (NFS) protocol that enables remote access to files is now a key element of any LAN. It is also currently and increasingly used as a key technology with the Web and wide area networks.

 

Written for programmers creating NFS-based applications, network engineers creating new implementations of NFS, and network managers, NFS Illustrated promotes a thorough understanding of that protocol through extensive diagrams and real protocol traces that show NFS in action. Covering NFS versions 2 and 3, the book also looks into WebNFS and the new NFS version 4, with Internet support. Detailed and authoritative, the book not only examines NFS in depth, but also describes the protocols that underlie and support it, including External Data Representation (XDR), Remote Procedure Call (RPC), the NFS MOUNT protocol, and the NFS Lock Manager protocol. It discusses several NFS variants and compares NFS to a number of alternative file systems.

 

You will find a detailed discussion on the NFS filesystem model and a procedure-by-procedure description of NFS versions 2 and 3, illustrated through the use of snoop traces that capture and display protocol packets from the network. In addition, the book addresses real-world implementation issues faced by those building an NFS client or server, factors that affect NFS performance, and critical performance benchmarks.

 

Specific topics of interest include:

  • NFS version 4, highlighting performance improvements, security features, and cross-platform interoperability for Internet operation
  • RPC authentication and security
  • Differences between NFS versions 2 and 3
  • Implementation issues for clients and servers
  • Read-ahead and write-behind
  • Caching policies
  • The Lock Manager protocol
  • Automounting
  • NFS variants, including Spritely NFS, NQNFS, Trusted NFS, and NASD NFS
  • NFS competitors: RFS, AFS, DCE/DFS, and CIFS
  • The PCNFS protocol for implementing NFS on PC operating systems
  • SPEC SFS benchmarks, WebNFS, and firewalls

Comprehensive and current, NFS Illustrated is an essential resource for network professionals who want to use this widespread and evolving technology to its fullest.

Read More

Editorial Reviews

Booknews
For programmers creating applications based on it, network engineers creating new implementations of it, and network managers, Callaghan, a software engineer at Sun Microsystems, explains the Network File System protocol, which enables remote access to files. He discusses the filesystem model, describes versions two and three procedure-by-procedure, looks at the new version four, and identifies factors that affect performance. Annotation c. Book News, Inc., Portland, OR (booknews.com)

Product Details

ISBN-13:
9780321618931
Publisher:
Pearson Education
Publication date:
01/07/2000
Sold by:
Barnes & Noble
Format:
NOOK Book
Pages:
544
File size:
19 MB
Note:
This product may take a few minutes to download.

Read an Excerpt

I have been working with the NFS protocol since I joined Sun Microsystems in 1986. At that time the NFS market was expanding rapidly and I was excited to be working with the group, led by Bob Lyon, that developed the protocol and its first implementation in SunOS. In the NFS group, the protocol was a powerful but raw technology that needed to be exploited. We wanted it to run on as many platforms as possible, so an NFS porting group was assigned the task of helping other companies implement NFS on their computers.

Our NFS evangelism was a little ahead of its time. Before the phrase "open systems" had yet become hackneyed, we'd made the source code for Sun RPC available for free download via FTP server1 and organized the first Connectathon event. At Connectathon our enthusiasm for NFS was shared with engineers from other companies who brought along their machines, source code, and junk food and spent a few days connected to a network, testing their NFS client and server implementations against each other.

Implementations of the NFS protocol have been successful in bringing remote file access to programs through existing interfaces. There is no need to change the software for remote file access or to name files differently. NFS has been almost too successful at making remote files indistinguishable from local files. For instance, a program that backs up files on a local disk to tape needs to avoid stumbling into NFS filesystems. For everyone but system administrators, NFS is invisible—if you ignore the rare "NFS server not responding" message.

It's easy to forget NFS is there. NFS has no programming interface of its own. Even software engineers have no need to deal with NFS directly. There are no conference tutorials called "Programming with NFS," there are no magazine screen shots of NFS-enabled applications, and there are no demonstrations of NFS at trade shows. Except for server admin-istrators, NFS seems not to exist.

There are many server implementations of the NFS protocol, each with its own features. Each of these server implementations has its own documentation, each slightly different. Perhaps this explains why there are so few NFS books available. NFS is never more than a chapter in a book about the operating system in which it is embedded.

Although NFS implementations vary, there is an underlying invariant: the protocol itself. NFS is not a single protocol. Not only are there two versions of the protocol in use now, but there is a third version in development as well. The NFS protocol is layered on XDR and RPC protocols, and no implementation is complete without the MOUNT and Lock Manager protocols. I wanted to bring all the NFS protocols together into a single volume along with other topics unique to NFS, such as Connectathon and the SPEC SFS benchmarks.

I wanted this book to describe the protocol in detail in a more interesting way than a dry, text-only specification. I was inspired by Richard Stevens's book TCP/IP Illustrated, Volume 1. This book is an excellent example of network protocols animated through the use of diagrams and real protocol traces that show the protocol in action. I have used that book as a model for my own description of the NFS protocols. I hope you will appreciate it as a useful reference.

1. It is still available today via the Connectathon Web site, www.connectathon.org

Acknowledgments

Many people have helped me write this book. I attribute the idea for the book to Carol Long, my first editor at Addison Wesley Longman. Thanks to Richard Stevens and John Ousterhout for the advice and encouragement I needed to begin this venture. I'm grateful to my editor, Mary O'Brien, for her generous support and encouragement over the two years it took to write the book and to Elizabeth Spainhour for prompt handling of my drafts and reviews.

I'm very grateful to fellow NFS engineer Mike Eisler, who gave me prompt and insightful feedback on several drafts. Agnes Jacob did me a great favor in filling a draft with lots of yellow sticky notes with suggestions that helped improve the readability of some of my more obscure text. I'm thankful that Mike Kupfer and Salit Gazit were able to guide me through the mysteries of the Network Lock Manager—their experience with this protocol was invaluable. David Robinson and Spencer Shepler, who both spent several years developing the SPEC SFS benchmarks, corrected my description of SFS benchmarking and offered useful background material.

Thanks to Alex Chiu for the corrections he provided to my account of the WebNFS security negotiation protocol. Carl Beame and Fred Whiteside were invaluable in their review of the PC-NFS chapter. In particular, they provided me with useful material on their BWNFSD daemon implementation. Thanks to Jeff Mogul for his thorough review of my short description of his work on Spritely NFS and to Rick Macklem for checking my description of his NQNFS variant of NFS version 2. I'm grateful to Gary Winiger for the corrections and additional material he offered for the section on Trusted NFS (TNFS).

Special thanks to my technical reviewers for tolerating my lengthy (and sometimes incomplete) manuscripts. To be a useful reference, a technical book depends heavily on the accumulated experience of its reviewers. Thanks to Ran Atkinson, Richard Basch, Bob Gilligan, Clemens Huebner, Ron Hutchins, Kirk McKusick, Tom McNeal, Vernon Schryver, Hal Stern, Dana Treadwell, and Andy Watson.

I'm grateful to my employer, Sun Microsystems, Inc., for giving me the time and resources to write this book. A special thanks to my managers for their unwavering support: Cindy Vinores, David Brittle, and Bev Crair. Thanks to Professional Computing Series editors Brian Kernighan and Craig Partridge for their detailed and helpful reviews.

Finally, I'm grateful for the patience and understanding of my family: my wife, Barbara, and sons, Luke and Eli. Not only did they cheerfully put up with my frequent absences to work on "The Book," they also provided needed encouragement.

Read More

Customer Reviews

Average Review:

Write a Review

and post it to your social network

     

Most Helpful Customer Reviews

See all customer reviews >