%28distributed%29filesystems administration article bookmarksmenu computer_science computing development dfs distributed faculdade file file_system filesystem job_file_systems linux netapp network networkfilesystem networking nfs nixon remote sistemas_distribuidos system_de_arquivos ubuntu

My tags:

From Wikipedia, the free encyclopedia

It has been suggested that this article or section be merged into Distributed file system. (Discuss)

A network file system is any computer file system that supports sharing of files, printers and other resources as persistent storage over a computer network. The first file servers were developed in the 1970s. In 1976 Digital Equipment Corporation created the File Access Listener (FAL) an implementation of the Data Access Protocol as part of DECnet Phase II which became the first widely used network file system. In 1985 Sun Microsystems created the file system called "Network File System" (NFS) which became the first widely used Internet Protocol based network file system. Other notable network file systems are Andrew File System (AFS), NetWare Core Protocol (NCP), and Server Message Block (SMB) which is also known as Common Internet File System (CIFS).

Contents 1 Transparency 2 Performance 3 Concurrent file updates 4 List of network file systems 4.1 Client-server file systems 5 See also 6 External links

[edit] Transparency

Ideally, a network file system should appear to its users to be a conventional, centralized file system. The multiplicity and dispersion of its servers and storage devices should be made invisible. That is, the client interface used by programs should not distinguish between local and remote files. It is up to the network file system to locate the files and to arrange for the transport of the data.

[edit] Performance

The most important performance measurement of a network file system is the amount of time needed to satisfy service requests. In conventional systems, this time consists of a disk-access time and a small amount of CPU-processing time. But in a network file system, a remote access has additional overhead due to the distributed structure. This includes the time to deliver the request to a server, the time to deliver the response to the client, and for each direction, a CPU overhead of running the communication protocol software. The performance of a network file system can be viewed as one dimension of its transparency: ideally, it would be comparable to that of a conventional file system.

[edit] Concurrent file updates

Concurrency control is a big and important issue nowadays as more than two persons accessing the same files and want to update it. A network file system should allow multiple client processes on multiple machines to access and update the same files. Hence updates to the file from one client should not interfere with access and updates from other clients. Concurrency control or locking may be either built into the file system or be provided by an add-on protocol.

[edit] List of network file systems

[edit] Client-server file systems

• 9P
• Amazon S3
• Andrew File System (AFS), OpenAFS
• Apple Filing Protocol (AFP)
• Coda
• DCE Distributed File System
• File Access Listener (FAL)
• NetWare Core Protocol (NCP)
• Network File System (protocol) (NFS)
• Secure File System (SFS) [1]
• Self-certifying File System (SFS)
• Server Message Block (SMB)

[edit] See also

• List of file systems, distributed file systems section
• Disk sharing
• Distributed data store
• Gopher

[edit] External links

• A distributed file system for distributed conferencing system ("A DFS for the DCS") by Philip S Yeager, Thesis, University of Florida, 2003. (pdf)
• Distributed File Systems Past, Present and Future: A Distributed File System for 2006 by Fabio Kon, Technical Report, University of Illinois at Urbana-Champaign, 1996.