Metadata Efficiency in a Comprehensive Versioning File System

Metadata Efficiency in a Comprehensive Versioning File System (2002)

Cached

Download Links

by Craig A. N. Soules , Garth R. Goodson , John D. Strunk , Gregory R Ganger

Venue:	In Proceedings of USENIX Conference on File and Storage Technologies
Citations:	21 - 2 self

Versions

Version History

Metadata Version 3

User correction supplied by SystemCorrections

Datum	Value	Source
TITLE	Metadata Efficiency in a Comprehensive Versioning File System	INFERENCE
AUTHOR NAME	Craig A. N. Soules	user correction - Legacy Corrections
AUTHOR AFFIL	School of Computer Science; Carnegie Mellon University	user correction - Legacy Corrections
AUTHOR ADDR	Pittsburgh, PA 15213	user correction - Legacy Corrections
AUTHOR NAME	Garth R. Goodson	user correction - Legacy Corrections
AUTHOR AFFIL	School of Computer Science; Carnegie Mellon University	user correction - Legacy Corrections
AUTHOR ADDR	Pittsburgh, PA 15213	user correction - Legacy Corrections
AUTHOR NAME	John D. Strunk	user correction - Legacy Corrections
AUTHOR AFFIL	School of Computer Science; Carnegie Mellon University	user correction - Legacy Corrections
AUTHOR ADDR	Pittsburgh, PA 15213	user correction - Legacy Corrections
AUTHOR NAME	Gregory R Ganger	user correction - Legacy Corrections
AUTHOR AFFIL	School of Computer Science; Carnegie Mellon University	user correction - Legacy Corrections
AUTHOR ADDR	Pittsburgh, PA 15213	user correction - Legacy Corrections
ABSTRACT	A comprehensive versioning file system creates and retains a new file version for every WRITE or other modification request. The resulting history of file modifications provides a detailed view to tools and administrators seeking to investigate a suspect system state. Conventional versioning systems do not efficiently record the many prior versions that result. In particular, the versioned metadata they keep consumes almost as much space as the versioned data. This paper examines two space-efficient metadata structures for versioning file systems and describes their integration into the Comprehensive Versioning File System (CVFS). Journal-based metadata encodes each metadata version into a single journal entry; CVFS uses this structure for inodes and indirect blocks, reducing the associated space requirements by 80%. Multiversion b-trees extend the per-entry key with a timestamp and keep current and historical entries in a single tree; CVFS uses this structure for directories, reducing the associated space requirements by 99%. Experiments with CVFS verify that its current-version performance is similar to that of non-versioning file systems. Although access to historical versions is slower than conventional versioning systems, checkpointing is shown to mitigate this effect.	user correction - Legacy Corrections
YEAR	2002	INFERENCE
VENUE	In Proceedings of USENIX Conference on File and Storage Technologies	INFERENCE
VENUE TYPE	CONFERENCE	INFERENCE
CITATIONS	45 found	ParsCit 1.0