Skip to content

Latest commit

 

History

History
50 lines (36 loc) · 1.4 KB

README.md

File metadata and controls

50 lines (36 loc) · 1.4 KB
Raw

xv6fs

Reimplementation of the file system used by xv6 in Rust and FUSE.

xv6's file system follows the early design of Linux's journaling file system (namely, extfs2), which supports recovery in presence of crash. For details, please refer to the xv6 book.

Normally, a file system should be abstracted into these layers.

  • disk
  • block cache
  • logging (journaling, transaction)
  • inode
  • directory
  • path resolution
  • file object / descriptor

We use FUSE's low level API, which manages these last two layers conforming with Unix. The remaining work is to implement the top five layers and cooperate them with FUSE interface.

Notice: for convenience, we mock the disk with an array of contiguous 512 bytes in memory, with an interface providing synchronized atomic block read / write. This disk acts as a service running in a separated thread, and communicate with the file system in a Go routine fashion (which should be similar to IDE interruption implemented in xv6).

Quick Start

Preparations.

  • a nightly Rust compiler (known to compile with rustc 1.27.0-nightly).
  • libfuse-dev (ubuntu, find substitution for yourself if using other Linux distros).
$ make run

Then we have a mounted file system at ./mnt/.

$ cd mnt
$ touch foobar

License

Conforming with xv6 (see LICENSE).