Distributed NAStore as the next step

The authors describe the goals and requirements that have shaped the emerging NAStore 3 design. They describe the current form of the design, which employs the Bitfile Server interface and the Bitfile Server's Migration Manager to create a transparent distributed file system. They describe how the UNIX system can be modified to work jointly with other UNIX systems to create a distributed file system while continuing to work independently as it does now. They also describe how the NAStore 3 design builds upon NAStore 2 and upon the U.C. Berkeley Redundant Array of Inexpensive Disks (RAID) research. Finally, they outline the prototype construction and system implementation steps to be taken leading to a production NAStore 3 system.<<ETX>>

[1]  John S. Heidemann,et al.  Implementation of the Ficus Replicated File System , 1990, USENIX Summer.

[2]  David Tweten Hiding mass storage under Unix: NASA's MSS-II architecture , 1990, [1990] Digest of papers. Tenth IEEE Symposium on Mass Storage Systems@m_Crisis in Mass Storage.

[3]  Kevin J. Dunlap,et al.  Experiences Implementing BIND, a Distributed Name Server for the DARPA Internet , 1986, USENIX Summer.

[4]  Sailesh Chutani,et al.  DEcorum File System Architectural Overview , 1990, USENIX Summer.

[5]  Mahadev Satyanarayanan,et al.  A SURVEY OF DISTRIBUTED FILE SYSTEMS , 1990 .

[6]  Kenneth P. Birman,et al.  Deceit: a flexible distributed file system , 1990, [1990] Proceedings. Workshop on the Management of Replicated Data.

[7]  Mahadev Satyanarayanan,et al.  Coda: A Highly Available File System for a Distributed Workstation Environment , 1990, IEEE Trans. Computers.

[8]  Stephen W. Miller,et al.  A Reference Model for Mass Storage Systems , 1988, Adv. Comput..

[9]  Andrew R. Cherenson,et al.  The Sprite network operating system , 1988, Computer.