@yuuza/btrdbfs v1.0.4

btrdbfs - btrdb FileSystem

Run a filesystem on btrdb!

btrdbfs implements FUSE filesystem using Node.js with the binding fuse-native.

Implemented operations

• create, open, mkdir, release
• readdir, getattr
• read, write
• chmod, chown, utimens, truncate
• unlink, rmdir, rename
• statfs
• link, symlink

Tested workloads

• copy/make some large files
• clone btrdb: git clone btrdb
• build btrdb: pnpm i && pnpm run build
• git clone and build MusicCloud, build and run its server
• run btrdbfs on btrdbfs and do things above

Performance

About 50 MB/s sequential read/write on i5-3320M with big_writes option.

$ dd if=/dev/zero of=mnt/zeros bs=1M status=progress
893386752 bytes (893 MB, 852 MiB) copied, 15 s, 59.6 MB/s^C
853+0 records in
853+0 records out
894435328 bytes (894 MB, 853 MiB) copied, 15.0697 s, 59.4 MB/s

$ dd if=mnt/bigfile of=/dev/null bs=1M status=progress
1083179008 bytes (1.1 GB, 1.0 GiB) copied, 22 s, 49.2 MB/s
1078+0 records in
1078+0 records out
1130364928 bytes (1.1 GB, 1.1 GiB) copied, 22.9497 s, 49.3 MB/s

The bottleneck is the CPU. Since both btrdb and btrdbfs are running on JS engine, the performance is better than my expectation.

The btrdb never do random write on the database file. For this reason, btrdbfs will have great random write performance on HDD.

Try it now

Install btrdbfs on your Linux OS:

npm install -g @yuuza/btrdbfs

Mount the btrdbfs:

mkdir mnt
btrdbfs myfs.db mnt

Design

Using three document sets for inodes, links and extents.

Inodes

/**
 * @typedef {Object} Inode
 * @property {number} id
 * @property {number} kind - KIND_*
 * @property {number} size
 * @property {number} ct - ctime
 * @property {number} at - atime
 * @property {number} mt - mtime
 * @property {number} mode
 * @property {number} uid
 * @property {number} gid
 * @property {string} ln - symlink
 */

const inodes = await db.createSet("inodes", "doc");

Links

For links, use "paid" index to get all links under the directory on readdir(), and use "paid_name" index to find a link with specific name under the specific directory when finding an link from path string.

/**
 * @typedef {Object} Link
 * @property {number} id
 * @property {number} ino
 * @property {number} paid - parent dir inode
 * @property {string} name
 */
const links = await db.createSet("links", "doc");
await links.useIndexes({
  "paid": (x) => x.paid,
  "paid_name": (x) => x.paid + "_" + x.name,
});

Extents

Each "Extent" document saving a Uint8array as the extent data. The "ino_pos" index is used to find an extent of an inode.

/**
 * @typedef {Object} Extent
 * @property {number} id
 * @property {number} ino - inode id
 * @property {number} pos
 * @property {Uint8Array} data
 */

const EXTENT_SIZE = 4 * 4096;

const extents = await db.createSet("extents", "doc");
extents.useIndexes({
  "ino_pos": (x) => x.ino + "_" + x.pos,
});