Pawlowski, B., Juszczak, C., Staubach, P., Smith, C., Lebel, D. and D. Hitz, "NFS Version 3 Design and Implementation", Proceedings of the USENIX Summer 1994 Technical Conference.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....paper describes a novel architecture and middleware techniques that allow the creation of Virtual Private Grid File System (VP GFS) sessions. VP GFS sessions support on demand data transfers on private, encrypted channels, and support the API of a widely used distributed network file system (NFS [17]) across nodes of a computational grid. The mechanisms are based on extensions to proxy based grid virtual file systems [2] that support i) private, per user encrypted data channels for NFS traffic without requiring modifications to existing NFS clients and servers, and ii) file system disk ....

B. Pawlowski, C Juszczak, P. Staubach, C. Smith, D. Lebel and D. Hitz, "NFS Version 3 Design and Implementation", Proc. USENIX Summer Technical Conference, 1994.

....2.1. Client performance issues NFS is based on a client makes right design: the client is responsible for ordering bytes, managing network and server congestion, and otherwise handling the complex issues of implementing a distributed file system. This leaves the server simple and scalable [15]. In fact, NFS servers maintain very little state. Satyanarayanan, et al. 16] justify this architecture by pointing out that in typical client server distributed systems, workstations have cycles to burn. Consequently, an NFS client tends to be complex, which can interfere with efficiency and ....

Pawlowski, B., Juszczak, C., Staubach, P., Smith, C., Lebel, D., Hitz, D. "NFS Version 3 - Design and Implementation. " USENIX Technical Conference Proceedings, June 1994.

....Our explicit marking of data does not change the behavior of cleaning, it merely simplifies our implementation. We simulate two write algorithms The first, called NFS async, does not provide synchronous NFS semantics. It assumes that either the file systems are mounted with the unsafe NFS option [6] or that the system is equipped with at least two segments worth of non volatile RAM into which segments are written before they are transferred to disk. In either case, the system caches data until a full segment accumulates before writing it to disk. The second model, NFSsynch, supports the ....

Pawlowski, B., Juszczak, C., Staubach, P., Smith, C., Lebel, D., Hitz., D., "NFS Version 3: Design and Implementation," Proceedings of the 1994 Summer Usenix Conference, Boston, MA, June 1994, 137-152.

....a file system runs on the server. The clients mount the file system on their hosts, and use the server functionalities seamlessly. Typically, multimedia servers can be of three types: centralized, distributed, and serverless. In a system with a centralized server (e.g. Network File System (NFS) [13], Symphony [15] Continuous Media File System (CMFS) 3] a single dedicated node controls the admission process as well as all other file operations and security issues. All the read write operations are approved and handled by the centralized server. Thus the implementation is simple and the ....

B. Pawlowski,, C. Juszczak, P. Staubach, C. Smith, D. Lebel, D. Hitz, "NFS Version 3 Design and Implementation", Winter USENIX Conf. Proc., USENIX Association, Berkeley, CA, January 1994.

....all nodes and all users, except those protected by the usual access rights, and vice versa. This should not be confused with the fact that multiple file systems can exist in a workstation as subdirectories of the root directory. The NFS Approach The NFS (Network File System) is an open standard [9] developed by Sun Microsys Table 2:Comparison of SSI Services in Four Distributed File Systems File System NFS AFS xFS Proxy FS Location Transparency Ye s Yes Ye s Ye s Remote Access Remote Procedure Call (RPC) RPC RPC (Active Message) Object handler (zero copy I O) Availability ....

B. Pawlowski, C. Juszczak, P. Staubach, C. Smith, D. Lebel, and D. Hitz, "NFS Version 3 Design and Implementation," Proc. of the 1994 Summer USENIX Conference, USENIX Association, Berkeley, CA, June 1994.

....to a server followed by a COMMIT request. The server is required to verify that client data is on stable storage only when it receives the COMMIT operation. A mechanism is provided that allows the client to detect server loss of uncommitted data and recover. Measurements of NFS V3 implementations [Pawlowski94] show that writes are now much faster and limited now only by the speed of the network. 2.3 Firewalls 2.3.1 TCP vs UDP The firewalls that protect corporate Intranets from Internet attackers have also been an effective barrier to the use of NFS on the Internet. Packet filtering firewalls are ....

....to disk rotational delay and seek time. The NFS version 3 protocol side steps the synchronous write requirement of version 2 by allowing the server to cache client writes in memory until the client requests the data be flushed to stable storage with a COMMIT request. Digital Equipment Corporation [Pawlowski94] have demonstrated that an implementation of NFS V3 running on a two Model 3000 600 workstations delivered peak write performance of 2,323 KB s vs 320 KB s for version 2 more than 7 times faster. With support from Prestoserve NVRAM and write gathering, V3 was still ahead with 6,425 KB s vs ....

Brian Pawlowski, Chet Juszczak, Peter Staubach, Carl Smith, Diane Lebel, David Hitz, "NFS Version 3 Design and Implementation," Summer USENIX Conference Proceedings, USENIX Association, Berkeley, CA, June 1994.

....either his NFS Version 4 capable desktop at home has synchronized its dirty cache with the server, or the server will revoke the delegation to gain access to the latest data. The user at the office will be blocked from accessing his data until the server has a consistent copy. 16. Future Work [Pawlowski] described several follow on tasks for NFS Version 3. Of those tasks, NFS Version 4 addresses strong security, while it does not provide support for concurrent write sharing (though we introduce delegations for improved caching performance) nor does it support disconnected operation. Changes to ....

Pawlowski, B. Juszczak, C., Staubach, P., Smith, C., Lebel, D., Hitz, D., "NFS Version 3 Design and Implementation." Proceedings of the USENIX Summer 1994 Technical Conference. http://www.netapp.com/ftp/NFSv3_Rev_3.pdf

No context found.

Pawlowski, B., Juszczak, C., Staubach, P., Smith, C., Lebel, D. and D. Hitz, "NFS Version 3 Design and Implementation", Proceedings of the USENIX Summer 1994 Technical Conference.

No context found.

Pawlowski, B., Juszczak, C., Staubach, P., Smith, C., Lebel, D. and D. Hitz, "NFS Version 3 Design and Implementation", Proceedings of the USENIX Summer 1994 Technical Conference.

No context found.

Pawlowski, B., Juszczak, C., Staubach, P., Smith, C., Lebel, D. and D. Hitz, "NFS Version 3 Design and Implementation", Proceedings of the USENIX Summer 1994 Technical Conference.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC