Skip to content
UnifyFS: A file system for burst buffers
C Perl Shell M4 Makefile Python
Branch: dev
Clone or download
CamStan and adammoody Revert previous unit test fix due to hang
Running the tests with an mpi launcher works fine in most cases, but
breaks in a certain LSF bsub implementation. The case that the tests
are run from a launch node to be executed on a compute node. The test
suite is set up to launch unifyfs on the current node (launch node)
so when the suites run, the server cannot be found on the computer
node. This is the case that is used by GitLab. This cannot be
resolved by simply running the server on the compute node from a
launch node as this causes automakes tap-driver.sh to hang, waiting
for the background process running the server to finish.

Since the unit tests all only use a single process, there is no need
to run them with an mpi launcher. The only thing mpi is needed for in
the unit test suites is the arguments for unifyfs_mount().

This reverts back to having the server used for unit testing and the
unit tests to all be run on the same node as the make check is
executed on. This makes it so an allocation is not required for
running the unit tests and will allow the unit tests to be run by
GitLab.
Latest commit c6f23b9 Aug 15, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Update build, start, and config docs Aug 9, 2019
client Fix size bugs, add lamination with chmod/fchmod, misc fixes Aug 14, 2019
common Fix size bugs, add lamination with chmod/fchmod, misc fixes Aug 14, 2019
docs Update build, start, and config docs Aug 9, 2019
examples Fix size bugs, add lamination with chmod/fchmod, misc fixes Aug 14, 2019
extras Rename UnifyCR to UnifyFS Aug 6, 2019
m4 Rename UnifyCR to UnifyFS Aug 6, 2019
meta Rename UnifyCR to UnifyFS Aug 6, 2019
scripts Allow style checker to pass on do-while loop Aug 9, 2019
server Fix size bugs, add lamination with chmod/fchmod, misc fixes Aug 14, 2019
t Revert previous unit test fix due to hang Aug 19, 2019
util Rename UnifyCR to UnifyFS Aug 6, 2019
.gitignore Fix size bugs, add lamination with chmod/fchmod, misc fixes Aug 14, 2019
.travis.yml initialize and publish margo remote RPC address May 28, 2019
LICENSE Rename UnifyCR to UnifyFS Aug 6, 2019
LICENSE.ANL fix burstfs and cruise license (#15) Dec 8, 2017
LICENSE.BURSTFS fix burstfs and cruise license (#15) Dec 8, 2017
LICENSE.CRUISE fix burstfs and cruise license (#15) Dec 8, 2017
Makefile.am Rename UnifyCR to UnifyFS Aug 6, 2019
README.md Rename UnifyCR to UnifyFS Aug 6, 2019
autogen.sh Rename UnifyCR to UnifyFS Aug 6, 2019
bootstrap.sh Update BMI git URL in bootstap.sh Aug 7, 2019
configure.ac Fix size bugs, add lamination with chmod/fchmod, misc fixes Aug 14, 2019

README.md

UnifyFS: A Distributed Burst Buffer File System - 0.1.0

Node-local burst buffers are becoming an indispensable hardware resource on large-scale supercomputers to buffer the bursty I/O from scientific applications. However, there is a lack of software support for burst buffers to be efficiently shared by applications within a batch-submitted job and recycled across different batch jobs. In addition, burst buffers need to cope with a variety of challenging I/O patterns from data-intensive scientific applications.

UnifyFS is a user-level burst buffer file system under active development. UnifyFS supports scalable and efficient aggregation of I/O bandwidth from burst buffers while having the same life cycle as a batch-submitted job. While UnifyFS is designed for N-N write/read, UnifyFS compliments its functionality with the support for N-1 write/read. It efficiently accelerates scientific I/O based on scalable metadata indexing, co-located I/O delegation, and server-side read clustering and pipelining.

Documentation

Full UnifyFS documentation is contained here.

Use Build & I/O Interception for instructions on how to build and install UnifyFS.

Build Status

The current status of the UnifyFS dev branch is:

Build Status Read the Docs

Contribute and Develop

Contributing guidelines can be found in our documentation.

You can’t perform that action at this time.