Replication in the harp file system

Liskov, Barbara; Ghemawat, Sanjay; Gruber, R.; Johnson, Paul R.; Shrira, Liuba; Williams, M.

doi:10.1145/121132.121169

Cited by 158 publications

(23 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Main database vendors, such as IBM and Oracle, have business solutions for highperformant dependable storage systems. Innovative approaches to such dependable storage systems are based on state machine replication, either in KV-stores [75,201,305], filesystems [96,230], or transactional storages [143,173]. These systems are frequently used to build business-critical (and sometimes even life-critical) systems and must be constantly monitored to assess the correct behavior of the storage system.…”

Section: Dependable Storage Systemsmentioning

confidence: 99%

A survey of challenges for runtime verification from advanced application domains (beyond software)

Sánchez

Schneider

Ahrendt

et al. 2019

Form Methods Syst Des

View full text Add to dashboard Cite

Runtime verification is an area of formal methods that studies the dynamic analysis of execution traces against formal specifications. Typically, the two main activities in runtime verification efforts are the process of creating monitors from specifications, and the algorithms for the evaluation of traces against the generated monitors. Other activities involve the instrumentation of the system to generate the trace and the communication between the system under analysis and the monitor.Most of the applications in runtime verification have been focused on the dynamic analysis of software, even though there are many more potential applications to other computational devices and target systems. In this paper we present a collection of challenges for runtime verification extracted from concrete application domains, focusing on the difficulties that must be overcome to tackle these specific challenges. The computational models that characterize these domains require to devise new techniques beyond the current state of the art in runtime verification.

show abstract

Section: Dependable Storage Systemsmentioning

confidence: 99%

A survey of challenges for runtime verification from advanced application domains (beyond software)

Sánchez

Schneider

Ahrendt

et al. 2019

Form Methods Syst Des

View full text Add to dashboard Cite

show abstract

“…VCFS adopts a low-level kernel approach similar to that taken in the Harp file system. 8 A kernel-level file system eliminates the overhead due to context switches, and thus results in better performance. VCFS also enables versioning to be used by all Unix applications without modification, since it falls under the Virtual File System (VFS) interface, and to allow extensions to implement immutable files and transaction support in distributed file systems.…”

Section: Vcfs Featuresmentioning

confidence: 99%

An Installable Version Control File System for Unix

Chee¹,

Erdogan²

1997

Softw: Pract. Exper.

View full text Add to dashboard Cite

SUMMARYWe present a file system named VCFS, a Version Control File System that provides transparent version control of files. VCFS is implemented as an installable file system in the Unix operating system. The facility is transparent to users in the sense that VCFS automatically stores changes between incremental versions of a file without user intervention. Access to the latest version of the file retains traditional Unix semantics, enabling all existing Unix applications to be run modified under VCFS if so desired. VCFS provides system call enhancements and supports application level utilities for version number retrieval, displaying changes between two versions of a file, upgrading to a new release number, and related version control functions. Performance measurements show that VCFS provides a significant increase in version control operations compared to application level change management systems such as SCCS, and that the space utilization is significantly better than of the existing version control systems. The primitives and facilities provided by VCFS can be exploited for use in a wide range of applications, ranging from immutable files, transaction processing and file replication support in a distributed file system, to the development of enhanced change management control systems for software project management. ©1997 by John Wiley & Sons, Ltd.key words: version control; software engineering; installable file system; immutable files THE NEED FOR VERSION CONTROL FILE SYSTEMS Efficient version control mechanisms are increasingly required by a wide range of Unix applications. In distributed systems which support file replication across distinct hosts, versioning support is necessary to identify copies of the same file stored on different hosts and determine the hosts that have the latest version of a file.

show abstract

“…Harp is a primary-copy server protocol [10]. The protocol uses witnesses [15], uninterruptible power supplies, and stable RAM to lower the cost of replication.…”

Section: Harpmentioning

confidence: 99%

Achieving strong consistency in a distributed file system

Triantafillou

Neilson

1997

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

Distributed file systems nowadays need to provide for fault tolerance. This is typically achieved with the replication of files. Existing approaches to the construction of replicated file systems sacrifice strong semantics (i.e., the guarantees the systems make to running computations when failures occur and/or files are accessed concurrently). This is done mainly for efficiency reasons. This paper puts forward a replicated file system protocol that enforces strong consistency semantics. Enforcing strong semantics allows for distributed systems to behave more like their centralized counterparts-an essential feature in order to provide the transparency that is so strived for in distributed computing systems. One fundamental characteristic of our protocol is its distributed nature. Because of it, the extra cost needed to ensure the stronger consistency is kept low since the bottleneck problem noticed in primary-copy systems is avoided, load balancing is facilitated, clients can choose physically close servers, and the work required during failure handling and recovery is reduced. Another characteristic is that instead of optimizing each operation type on its own, file system activity was viewed at the level of a file session and the costs of individual operations were able to be spread over the life of a file session. We have developed a prototype and compared the performance of the prototype to both NFS and a nonreplicated version of the prototype that also achieves strong consistency semantics. Through these comparisons the cost of replication and the cost of enforcing the strong consistency semantics are shown.

show abstract

Replication in the harp file system

Cited by 158 publications

References 17 publications

A survey of challenges for runtime verification from advanced application domains (beyond software)

A survey of challenges for runtime verification from advanced application domains (beyond software)

An Installable Version Control File System for Unix

Achieving strong consistency in a distributed file system

Contact Info

Product

Resources

About