#fuse #filesystem-path

fuse_mt

A higher-level FUSE filesystem library with multi-threading and inode->path translation

16 releases

0.6.3 Nov 30, 2025
0.6.1 Sep 19, 2023
0.6.0 Jul 12, 2022
0.5.1 Aug 17, 2020
0.3.0 Feb 1, 2017

#178 in Filesystem

Download history 275/week @ 2025-10-01 1299/week @ 2025-10-08 1100/week @ 2025-10-15 2403/week @ 2025-10-22 769/week @ 2025-10-29 2205/week @ 2025-11-05 2168/week @ 2025-11-12 796/week @ 2025-11-19 4304/week @ 2025-11-26 5455/week @ 2025-12-03 1768/week @ 2025-12-10 470/week @ 2025-12-17 287/week @ 2025-12-24 672/week @ 2025-12-31 351/week @ 2026-01-07 334/week @ 2026-01-14

1,781 downloads per month
Used in 7 crates (6 directly)

MIT/Apache

66KB
1.5K SLoC

FUSE-MT

Build Status Crates.io

Documentation

This code is a wrapper on top of the Rust FUSE crate with the following additions:

  • Dispatch system calls on multiple threads, so that e.g. I/O doesn't block directory listing.
  • Translate inodes into paths, to simplify filesystem implementation.

The fuser crate provides a minimal, low-level access to the FUSE kernel API, whereas this crate is more high-level, like the FUSE C API.

It includes a sample filesystem that uses the crate to pass all system calls through to another filesystem at any arbitrary path.

This is a work-in-progress. Bug reports, pull requests, and other feedback are welcome!

Some random notes on the implementation:

  • The trait that filesystems will implement is called FilesystemMT, and instead of the FUSE crate's convention of having methods return void and including a "reply" parameter, the methods return their values. This feels more idiomatic to me. They also take &Path arguments instead of inode numbers.
  • Currently, only the following calls are dispatched to other threads:
    • read
    • write
    • flush
    • fsync
  • Other calls run synchronously on the main thread because either it is expected that they will complete quickly and/or they require mutating internal state of the InodeTranslator and I want to avoid needing locking in there.
  • The inode/path translation is always done on the main thread.
  • It might be a good idea to limit the number of concurrent read and write operations in flight. I'm not sure yet how many outstanding read/write requests FUSE will issue though, so it might be a non-issue.

Dependencies

~3–4MB
~75K SLoC