Mesh-based content routing using XML
SOSP '01 Proceedings of the eighteenth ACM symposium on Operating systems principles
Advanced non-distributed operating systems course
ACM SIGCSE Bulletin
Alcatraz: An Isolated Environment for Experimenting with Untrusted Software
ACM Transactions on Information and System Security (TISSEC)
When cryptography meets storage
Proceedings of the 4th ACM international workshop on Storage security and survivability
Selective versioning in a secure disk system
SS'08 Proceedings of the 17th conference on Security symposium
Snapshot-Based Data Backup Scheme: Open ROW Snapshot
ICCS 2009 Proceedings of the 9th International Conference on Computational Science
Versioning for workflow evolution
Proceedings of the 19th ACM International Symposium on High Performance Distributed Computing
Snapshot-based data recovery approach
Proceedings of the 15th WSEAS international conference on Systems
Issues in automatic provenance collection
IPAW'06 Proceedings of the 2006 international conference on Provenance and Annotation of Data
Beyond disk imaging for preserving user state in network testbeds
CSET'12 Proceedings of the 5th USENIX conference on Cyber Security Experimentation and Test
A new one-way isolation file-access method at the granularity of a disk-block
ATC'07 Proceedings of the 4th international conference on Autonomic and Trusted Computing
Proceedings of the Twenty-Fourth ACM Symposium on Operating Systems Principles
ACM SIGOPS 24th Symposium on Operating Systems Principles
Replication, history, and grafting in the Ori file system
Proceedings of the Twenty-Fourth ACM Symposium on Operating Systems Principles
Hi-index | 0.00 |
Modern file systems associate the deletion of a file with the release of the storage associated with that file, and file writes with the irrevocable change of file contents. We propose that this model of file system behavior is a relic of the past, when disk storage was a scarce resource. We believe that the correct model should ensure that all user actions are revocable. Deleting a file should change only the name space and file writes should overwrite no old data. The file system, not the user, should control storage allocation using a combination of user specified policies and information gleaned from file-edit histories to determine which old versions of a file to retain and for how long.This paper presents the Elephant file system, which provides users with a new contract: Elephant will automatically retain all important versions of the users files. Users name previous file versions by combining a traditional pathname with a time when the desired version of a file or directory existed. Elephant manages storage at the granularity of a file or groups of files using user-specified retention policies. This approach contrasts with checkpointing file systems such as Plan-9, AFS, and WAFL, that periodically generate efficient checkpoints of entire file systems and thus restrict retention to be guided by a single policy for all files within that file system. We also report on the Elephant prototype, which is implemented as a new Virtual File System in the FreeBSD kernel.