Showing papers on "Distributed File System published in 1980"

Issues in the design and use of a distributed file system

Abstract: This paper discusses an independent file facility, one that is not embedded in an operating system. The distributed file system (DFS) is so named because it is implemented on a cooperating set of server computers connected by a communications, network, which together create the illusion of a single, logical system for the creation, deletion, and random accessing of data. Access to the DFS can only be accomplished over the network; a computer (or, more precisely, a program running on one) that uses the DFS is called a client. This paper describes the division of responsibility between servers and clients. The basic tool for maintaining data consistency in these situations is the atomic property of transactions, which protects clients from system malfunctions and from the competing activities of other clients. Several cooperating clients may share a transaction. The DFS provides an unconventional locking mechanism between transactions that supports client caches and eliminates a novel form of deadly embrace. We have implemented and put into service a system based on these concepts.

A Universal File Server

Abstract: A file server is a utility provided in a computer connected via a local communications network to a number of other computer. File servers exist to preserve material for the benefit of client machines or systems. It is desirable for a file server to be able to support multiple file directory and access management systems, so that the designer of a client system retains the freedom to design the system that best suits him. For example, he may wish to use the rile server to support a predefimed directory structure or as a swapping disk. The paper explores the dedgn issues associated with such a file server and proposes some solutions.

File area managing system

Abstract: PURPOSE:To reduce the file capacity of distribution, by giving a space which can store the data amount of the entire system at a peak day to a distributed file. CONSTITUTION:When a transmission request is given from a terminal side, the address of a memory area on a distribution file DF of a distributed to terminals A-C is obtained by referring to a data managing table 20 classified by terminal, and the distributed file is read out and transmitted to the terminal. When the distributed data is transmitted, the said data area is vacant and erased from a table 20 and registered in a table 22 instead. In writing in the distributed data to the distribution file DF, the area managing table 22 is observed and vacant areas in which the said distribution data can sufficiently be written in, are obtained and the said distribution data are written in.