ACM Transactions on Computer Systems (TOCS)
Reimplementing the Cedar file system using logging and group commit
SOSP '87 Proceedings of the eleventh ACM Symposium on Operating systems principles
The design and implementation of a log-structured file system
ACM Transactions on Computer Systems (TOCS)
Hierarchical clustering: a structure for scalable multiprocessor operating system design
The Journal of Supercomputing - Special issue: trends in parallel operating systems
HFS: a performance-oriented flexible file system based on building-block compositions
ACM Transactions on Computer Systems (TOCS)
Physical integrity in a large segmented database
ACM Transactions on Database Systems (TODS)
A trace-driven analysis of the UNIX 4.2 BSD file system
Proceedings of the tenth ACM symposium on Operating systems principles
Soft updates: a solution to the metadata update problem in file systems
ACM Transactions on Computer Systems (TOCS)
The Recovery Manager of the System R Database Manager
ACM Computing Surveys (CSUR)
Samba: Integrating UNIX and Windows
Samba: Integrating UNIX and Windows
Inside the Windows NT File System
Inside the Windows NT File System
Filesystem Performance and Scalability in Linux 2.4.17
Proceedings of the FREENIX Track: 2002 USENIX Annual Technical Conference
HOTOS '97 Proceedings of the 6th Workshop on Hot Topics in Operating Systems (HotOS-VI)
Hfs: a flexible file system for shared-memory multiprocessors
Hfs: a flexible file system for shared-memory multiprocessors
Running "Fsck" in the background
BSDC'02 Proceedings of the BSD Conference 2002 on BSD Conference
File system logging versus clustering: a performance comparison
TCON'95 Proceedings of the USENIX 1995 Technical Conference Proceedings
Metadata logging in an NFS server
TCON'95 Proceedings of the USENIX 1995 Technical Conference Proceedings
Adding response time measurement of CIFS file server performance to NetBench
NT'97 Proceedings of the USENIX Windows NT Workshop on The USENIX Windows NT Workshop 1997
Journaling versus soft updates: asynchronous meta-data protection in file systems
ATEC '00 Proceedings of the annual conference on USENIX Annual Technical Conference
Soft updates: a technique for eliminating most synchronous writes in the fast filesystem
ATEC '99 Proceedings of the annual conference on USENIX Annual Technical Conference
K42: building a complete operating system
Proceedings of the 1st ACM SIGOPS/EuroSys European Conference on Computer Systems 2006
K42: lessons for the OS community
ACM SIGOPS Operating Systems Review
Fast memory snapshot for concurrent programmingwithout synchronization
Proceedings of the 23rd international conference on Supercomputing
Symmetric active/active metadata service for high availability parallel file systems
Journal of Parallel and Distributed Computing
Hi-index | 0.00 |
File system consistency frequently involves a choice between raw performance and integrity guarantees. A few software-based solutions for this problem have appeared and are currently being used on some commercial operating systems; these include log-structured file systems, journaling file systems, and soft updates. In this paper, we propose meta-data snapshotting as a low-cost, scalable, and simple mechanism that provides file system integrity. It allows the safe use of write-back caching by making successive snapshots of the meta-data using copy-on-write, and atomically committing the snapshot to stable storage without interrupting file system availability. In the presence of system failures, no file system checker or any other operation is necessary to mount the file system, therefore it greatly improves system availability. This paper describes meta-data snapshotting, and its incorporation into a file system available for the Linux and K42 operating systems. We show that meta-data snapshotting has low overhead: for a microbenchmark, and two macrobenchmarks, the measured overhead is of at most 4%, when compared to a completely asynchronous file system, with no consistency guarantees. Our experiments also show that it induces less overhead then a write-ahead journaling file system, and it scales much better when the number of clients and file system operations grows.Furthermore, this new technique can be easily extended to provide file system snapshotting (versioning) and transaction support for a collection of selected files or directories.