Mirrorfs is a lazy-mirroring stackable file system. It creates a thin view of a remote file system by displaying only file and directory names, with their correct sizes. However, none of the actual file data is retrieved locally until someone (possibly remote) tries to read it. In that manner, only files that are actually being used get mirrored from the origin site. When a remote user tries to read a file (say via FTP or HTTP), Mirrorfs will open a T-style channel to both the user and the origin site, retrieving the data from the remote site on the fly, streaming it to the end-user, and concurrently writing it to the local disk for persistent storage. (In a way, the local disk in Mirrorfs acts as a caching file system.) Since remote users are trying to retrieve data over a slow network channels anyway, the added overhead for retrieving the data from the origin site is negligible. Mirrorfs can also lazy-copy the meta-data of the origin file system (file/directory names, sizes, etc.). Finally, we include a set of policies that can clean up data files that either no longer exist on the remote site, or haven't been used locally for a period of time.
|#||Name (click for home page)||Program||Period||Current Location|
|1||Nikolai Joukov||PhD||Jan 2004 - Dec 2006||Research Staff Member, Storage and Data Services Research group, IBM T. J. Watson Research Center (Hawthorne, NY)|
|#||Sponsor||Amount||Period||Type||Title (click for award abstract)|
|1||NSF Trusted Computing (TC)||$400,000||2003-2006||Sole PI||A Layered Approach to Securing Network File Systems|