Codecov Report

Merging #119 into develop will increase coverage by 0.08%.
The diff coverage is 92.3%.

@@             Coverage Diff             @@
##           develop     #119      +/-   ##
===========================================
+ Coverage    78.24%   78.33%   +0.08%     
===========================================
  Files          127      128       +1     
  Lines         9774     9786      +12     
===========================================
+ Hits          7648     7666      +18     
+ Misses        1522     1518       -4     
+ Partials       604      602       -2

Codecov Report

Merging #119 into develop will decrease coverage by 2.39%.
The diff coverage is 92.3%.

@@            Coverage Diff             @@
##           develop     #119     +/-   ##
==========================================
- Coverage    78.24%   75.85%   -2.4%     
==========================================
  Files          127      149     +22     
  Lines         9774    11994   +2220     
==========================================
+ Hits          7648     9098   +1450     
- Misses        1522     1890    +368     
- Partials       604     1006    +402

1. FUSE on CovenantSQL works now!

AS the original author commented in src code:

Inode relationships are stored in the namespace table, and inodes
themselves in the inode table.

Data blocks are stored in the block table, indexed by inode ID
and block number.

Basic functionality is implemented, including:

• mk/rm directory
• create/rm files
• read/write files
• rename
• symlinks

WARNING: concurrent access on a single mount is fine. However,
behavior is undefined (read broken) when mounted more than once at the
same time. Specifically, read/writes will not be seen right away and
may work on out of date information.

One caveat of the implemented features is that handles are not
reference counted so if an inode is deleted, all open file descriptors
pointing to it become invalid.

Some TODOs (definitely not a comprehensive list):

• support basic attributes (mode, timestamps)
• support other types: hard links
• add ref counting (and handle open/release)
• sparse files: don't store empty blocks
• sparse files 2: keep track of holes