# Fuse-T support?

**URL:** <https://kopia.discourse.group/t/fuse-t-support/3769>\
**Category:** General Topics\
**Created:** [February 25, 2025, 4:45am UTC](https://kopia.discourse.group/t/fuse-t-support/3769 "2025-02-25T04:45:43Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![sorgel](https://avatars.discourse-cdn.com/v4/letter/s/b3f665/32.png) [@sorgel](https://kopia.discourse.group/u/sorgel)\
**Post date:** [February 25, 2025, 4:45am UTC](https://kopia.discourse.group/t/fuse-t-support/3769/1 "2025-02-25T04:45:43Z")

</div>

Currently, for macOS, Kopia requires macFUSE to mount a snapshot as a file system.

macFUSE has some issues, one of which is the use of a kernel extension — a practice discouraged by Apple. This fact led Cryptomator to support and recommend the more modern FUSE-T instead of macFUSE. Here is a discussion with details:

> <https://github.com/cryptomator/cryptomator/issues/2482>
>
> \### Please agree to the following
> 
> \- \[X\] I have searched \[existing issues\](https…://github.com/cryptomator/cryptomator/issues?q=) for duplicates
> \- \[X\] I agree to follow this project's \[Code of Conduct\](https://github.com/cryptomator/cryptomator/blob/develop/.github/CODE\_OF\_CONDUCT.md)
> 
> \### Summary
> 
> Support for FUSE-T (macOS FUSE implementation without kext)
> 
> \### Motivation
> 
> macFUSE relies on a kext and is very often flaky (at least for me). Kexts are also set to be deprecated on macOS soon.
> 
> FUSE-T is a new FUSE implementation that doesn't rely on a kext: https://www.fuse-t.org/
> 
> Cryptomator doesn't seem to work with it however - with FUSE-T installed on my system, the only option available in Preferences -\> Virtual Drive is WebDAV.
> 
> Any chance you could support FUSE-T on macOS?
> 
> \### Considered Alternatives
> 
> \_No response\_
> 
> \### Anything else?
> 
> \_No response\_

I’m curious if Kopia developers are considering supporting FUSE-T?

---

<div class="post-metadata">

**Author:** ![sorgel](https://avatars.discourse-cdn.com/v4/letter/s/b3f665/32.png) [@sorgel](https://kopia.discourse.group/u/sorgel)\
**Post date:** [February 25, 2025, 8:01am UTC](https://kopia.discourse.group/t/fuse-t-support/3769/2 "2025-02-25T08:01:42Z")

</div>

It seems we might not need it after all — at least not for users with an rclone repository.

Kopia was the last application on my machine that relied on macFUSE. So, I was interested to see if I could get it working with fuse-t and remove macFUSE entirely.

As it turns out, rclone works quite well with fuse-t. Instead of mounting a repository with Kopia and macFUSE, users can mount it using rclone and then connect to it with Kopia as if it were a new repository.

This approach should improve performance. Not only because fuse-t performs better but also because it aligns with the recommended method for rclone repos:

> [@Faster restore from rclone repository](https://kopia.discourse.group/t/faster-restore-from-rclone-repository/3716):
>
> hi, I’m using a rclone google drive repository for backup my AppData von windows. restoring this is very slow because of many small files. Is there a fast way for restore ? Like to download as zip from the cloud instead of downloading all single files ?

If fuse-t support is ever implemented in Kopia, it would benefit more users with non-rclone backend. And users with rclone repositories should use the method described above without waiting for a fuse-t implementation.

Please let me know if I’ve misunderstood anything or gotten something wrong.

---

<div class="post-metadata">

**Author:** ![kapitainsky](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/kapitainsky/32/535_2.png) [@kapitainsky](https://kopia.discourse.group/u/kapitainsky)\
**Post date:** [February 25, 2025, 8:18am UTC](https://kopia.discourse.group/t/fuse-t-support/3769/3 "2025-02-25T08:18:25Z")

</div>

Using rclone you can mount raw repository but not its content… I think you misunderstood what `kopia mount` is for.

For the latter no `FUSE` is needed. You can use `webdav` alternative:

`kopia mount snapshot_ID /path/to/mountpoint --webdav`

> **[mount](https://kopia.io/docs/reference/command-line/common/mount/)**
>
> $ kopia mount \[path\] \[mountPoint\] Mount repository object as a local filesystem.
> Flag Short Default Help --\[no-\]browse false Open file browser --\[no-\]fuse-allow-non-empty-mount false Allows the mounting over a non-empty directory. The files in it...

---

<div class="post-metadata">

**Author:** ![sorgel](https://avatars.discourse-cdn.com/v4/letter/s/b3f665/32.png) [@sorgel](https://kopia.discourse.group/u/sorgel)\
**Post date:** [February 25, 2025, 8:33am UTC](https://kopia.discourse.group/t/fuse-t-support/3769/5 "2025-02-25T08:33:42Z")

</div>

Thank you!

I noticed this option earlier but somehow assumed WebDAV would be outperformed by almost any alternative. Perhaps that’s not true, and I should test it.

And you were right — I misunderstood how mounting works when it comes to mounting a snapshot instead of a repository. Thanks for pointing that out to me!
