rclone FUSE mount does not reliably unmount when operations are in flight, leaving broken mount behind

[nh2]

rclone FUSE mount does not reliably unmount when operations are in flight, leaving broken mount behind

[Animosity022]

The best way around that is to make sure all IO is stopped as if you have a network mount, it's going to be gritty to make anything stop 'nicely'.

I use systemd and ensure all processes connected are stopped before trying to stop the mount.

Even 5 times or 50 times, I don't think most people would figure out they need to stop processes connected to it.

Most folks already do a lazy unmount as well.

[ncw]

@nh2 which mount command are you using?

rclone mount uses bazil.org/fuse whereas rclone mount2 uses github.com/hanwen/go-fuse/v2?

If you are using rclone mount but investigating github.com/hanwen/go-fuse/v2 then you are investigating the wrong library :-(

There is also rclone cmount which you get if you build with -tags cmount on linux but it the default mount on macOS and Windows. This uses github.com/winfsp/cgofuse. This understands libfuse options - maybe there is a mount option for lazy unmount?

Can you try all 3 mounts and see if they have the same behaviour?

If we want to make lazy unmount an option then we need to add it to all 3 mounts ideally.

If you want to try the retry 5 times then try rclone mount2 and it should call the hanwen fuse code you linked above.