MarFS provides a scalable near-POSIX file system by using one or more POSIX file systems as a scalable metadata component and one or more data stores (object, file, etc) as a scalable data component.
Clone or download
jti-lanl compile-time fix for non-sockets builds.
For non-sockets builds, we had the wrong sense of a compile-time test.
This would've caused pftool to spew warnings about reading the
~/.awsAuth file, but was hidden by the same thing that required
erasureUtils 54bea71ba066.  Unhidden by that, and now fixed by this.
Latest commit d707b2f Nov 1, 2018

README.md

MarFS provides a scalable near-POSIX file system by using one or more POSIX file systems as a scalable metadata component and one or more data stores (object, file, etc) as a scalable data component.

Our default implementation uses GPFS file systems as the metadata component and Scality object stores as the data component.

The MetaData Abstraction Layer and Data Abstraction Layer (MDAL/DAL) provide a modular way to introduce alternative implementations (metadata and data implementations, respectively). We are developing a Multi-Component data implementation, which we are currently in the process of validating. This adds the ability to use our own erasure implementation over underlying RAID-Z3 ZFS pools as the data component.

There is extensive documentation in the Documents directory, including theory and an install guide.