cannot access mount: connection refused

[MuhtasimTanmoy]

To regenerate

sudo ./target/debug/branchfs mount --base ~/test /mnt/a
Mounted at "/mnt/a"

sudo ./target/debug/branchfs create t /mnt/a
Error: Failed to open control file (is /mnt/a mounted?): Connection refused (os error 111)

ls /mnt/a
ls: cannot access '/mnt/a': Connection refused

mount | grep /mnt/
branchfs on /mnt/a type fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions)

Previously, didn't have this issue at commit 846338f253cd451eced27d6de46979f15f700f91

[congwang-mk]

Hi @MuhtasimTanmoy

I can't reproduce it here. Is it possible you had a stale mount from a previous run? Also, could you check if the FUSE daemon was running after mounting and before creating a branch?

Thanks.

[MuhtasimTanmoy]

• FUSE daemon was running, branchfs list worked. ls /mnt/a didn't.
• Did unmount the previous run

I will get back with a more consistent regeneration then.

[MuhtasimTanmoy]

If it requires no root privileges, then why

RUST_LOG=debug ./target/debug/branchfs mount --base ~/test /mnt/a

[2026-02-17T06:51:45Z ERROR branchfs::daemon] Failed to create daemon: io error: Permission denied (os error 13)
Error: Daemon failed to start

Need to use sudo.

[congwang-mk]

Probably because by default it uses /var/ for storage, you can avoid this by specifying your own storage via --storage option, for example, ./target/release/branchfs mount --base /tmp/basedir --storage /tmp/storage /tmp/branchfs