Dave Hitz, James Lau, and Michael Malcolm. File system design for a file server appliance. In Proceedings of the 1994 Winter USENIX Technical Conference, pages 235--245, San Francisco, CA, January 1994. Usenix. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Deciding when to forget in the Elephant file system - Santry, Feeley.. (1999) (49 citations) (Correct)
....file systems, off line backup storage is used to protect users from system failures, media failures, and their own mistakes. Checkpointing file systems such as Plan 9, AFS, and WAFL build this support into the file system using copy on write techniques to create periodic file system checkpoints [16, 5, 6]. These checkpoints are available online and they allow users to access out dated versions that were captured by a checkpoint. Changes that occur between checkpoints (or backups) however, are not recoverable. Furthermore, the fact that checkpointing occurs at the granularity of the entire file ....
....did not apply to directories. Operations such as renaming a file, creating or destroying a directory, or, in some cases, deleting a file, were thus not revocable. Several recent file systems have taken a different approach to versioning. In systems such as AFS [6] Plan 9 [16, 15] and WAFL [5] an efficient checkpoint of an entire file system can be created to facilitate backup or to provide users with some protection from accidental deletes and overwrites. A checkpoint is typically created and maintained in a copy on write fashion in parallel with the active file system. The old ....
Dave Hitz, James Lau, and Michael Malcolm. File system design for a file server appliance. In Proceedings of the 1994 Winter USENIX Technical Conference, pages 235--245, San Francisco, CA, January 1994. Usenix.
Elephant: The File System that Never Forgets - Douglas Santry (1999) (10 citations) (Correct)
....versioning did not apply to directories. Operations such as renaming a file, creating or destroyinga directory, or, in some cases, deleting a file, were thus not revocable. Several recent file systems have taken a different approach to versioning. In systems such as AFS [5] Plan9 [7] and WAFL [4] an efficient checkpoint of an entire file system can be created to facilitate backup or to provide users with some protection from accidental deletes and overwrites. A checkpoint is typically created and maintained in a copy on write fashion in parallel with the active file system. The old ....
....Elephant In Elephant, all user operations are reversible. Deleting a file does not release its storage and file writes are handled in a copy on write fashion, creating a new version of a file block each time it is written. Elephant s update handling is thus similar to the Log Structured File System[4, 9, 11], though meta data handling and log cleaning are fundamentally different as discussed below. File versions are indexed by the time they were created and versioning is extended to directories as well as files. When naming a file or directory, a user can optionally specify a date and time as part of ....
D. Hitz, J. Lau, and M. Malcolm. File system design for a file server appliance. In Proceedingsof the 1994Winter USENIX Technical Conference, pages 235--245, San Francisco, CA, January 1994. Usenix.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC