Synoloy NAS does not support fuse3

Dong_Hyun_Choi · March 20, 2023, 6:00am

What is the problem you are having with rclone?

Synoloy NAS does not support fuse3 and I cannot mount the remote due to fuse3.

[Rclone Log]
failed to mount FUSE fs: fusermount: exec: "fusermount3": executable file not found in $PATH

So I want to know how to mount the remote without fuse3.
Otherwise if it's necessary, I want to know how to install fuse3 on the Synoloy NAS.

Run the command 'rclone version' and share the full output of the command.

1.16.1 or before : Sucess
1.62.0 : Failed
1.62.1 : Failed
1.62.2 : Failed

Which cloud storage system are you using? (eg Google Drive)

Google Drive

The command you were trying to run (eg `rclone copy /tmp remote:tmp`)

Paste command here

The rclone config contents with secrets removed.

Paste config here

A log from the command with the `-vv` flag

Paste  log here

ncw · March 20, 2023, 11:01am

Unfortunately the library rclone uses switched to fuse3 so rclone has to follow suit.

Your choices are

use an older version of rclone
build rclone yourself from source and use rclone cmount which will use fuse2
install fuse3 on the synology

asdffdsa · March 20, 2023, 12:54pm

i have already posted about that the synology forum, so far no answer.
https://community.synology.com/enu/forum/1/post/159464

Dong_Hyun_Choi · March 21, 2023, 12:32am

OK, I see. I think old version is the best way to me...because I don't know how to install fuse3 to Synology.
Many thanks!

ncw · March 21, 2023, 12:57pm

One thing that might be worth trying is just symlinking the fusermount binary to fusermount3 or maybe copying it. I don't know whether that will work or not, but it is worth a try!

asdffdsa · March 21, 2023, 1:06pm

yes, it was worth a try

2023/03/21 09:05:35 DEBUG : rclone: Version "v1.62.2" starting with parameters ["rclone" "mount" "wasabi01:zork" "/var/services/homes/user99/rclone/mount/remote" "--allow-other" "--vfs-cache-mode=full" "--cache-dir=/var/services/homes/user99/rclone/cache" "--config=/var/services/homes/user99/.config/rclone/rclone.conf" "--log-level=DEBUG" "--debug-fuse"]
2023/03/21 09:05:35 DEBUG : Creating backend with remote "wasabi01:zork"
2023/03/21 09:05:35 DEBUG : Using config file from "/var/services/homes/user99/.config/rclone/rclone.conf"
2023/03/21 09:05:35 DEBUG : Resolving service "s3" region "us-east-1"
2023/03/21 09:05:35 INFO  : S3 bucket zork: poll-interval is not supported by this remote
2023/03/21 09:05:35 DEBUG : vfs cache: root is "/var/services/homes/user99/rclone/cache"
2023/03/21 09:05:35 DEBUG : vfs cache: data root is "/var/services/homes/user99/rclone/cache/vfs/wasabi01/zork"
2023/03/21 09:05:35 DEBUG : vfs cache: metadata root is "/var/services/homes/user99/rclone/cache/vfsMeta/wasabi01/zork"
2023/03/21 09:05:35 DEBUG : Creating backend with remote "/var/services/homes/user99/rclone/cache/vfs/wasabi01/zork"
2023/03/21 09:05:35 DEBUG : Creating backend with remote "/var/services/homes/user99/rclone/cache/vfsMeta/wasabi01/zork"
2023/03/21 09:05:35 INFO  : vfs cache: cleaned: objects 0 (was 0) in use 0, to upload 0, uploading 0, total size 0 (was 0)
2023/03/21 09:05:35 DEBUG : S3 bucket zork: Mounting on "/var/services/homes/user99/rclone/mount/remote"
2023/03/21 09:05:35 mount helper error: fusermount3: mount failed: Operation not permitted
2023/03/21 09:05:35 Fatal error: failed to mount FUSE fs: fusermount: exit status 1

ncw · March 21, 2023, 1:12pm

Try a symlink - the fusermount binary is setuid so is hard to copy correctly...

ncw · March 21, 2023, 1:13pm

Interesting, its a symlink on my system so there must be some level of forward/backward compatibility

$ ls -l `which fusermount`
lrwxrwxrwx 1 root root 11 Mar 23  2022 /usr/bin/fusermount -> fusermount3
$ ls -l /usr/bin/fusermount3
-rwsr-xr-x 1 root root 35200 Mar 23  2022 /usr/bin/fusermount3

asdffdsa · March 21, 2023, 1:17pm

looks like the symlink worked

ln -s /bin/fusermount /bin/fusermount3

2023/03/21 09:39:17 DEBUG : rclone: Version "v1.62.2" starting with parameters ["rclone" "mount" "wasabi01:zork" "/var/services/homes/user99/rclone/mount/remote" "--allow-other" "--vfs-cache-mode=full" "--cache-dir=/var/services/homes/user99/rclone/cache" "--config=/var/services/homes/user99/.config/rclone/rclone.conf" "--log-level=DEBUG" "--debug-fuse"]
2023/03/21 09:39:17 DEBUG : Creating backend with remote "wasabi01:zork"
2023/03/21 09:39:17 DEBUG : Using config file from "/var/services/homes/user99/.config/rclone/rclone.conf"
2023/03/21 09:39:17 DEBUG : Resolving service "s3" region "us-east-1"
2023/03/21 09:39:17 INFO  : S3 bucket zork: poll-interval is not supported by this remote
2023/03/21 09:39:17 DEBUG : vfs cache: root is "/var/services/homes/user99/rclone/cache"
2023/03/21 09:39:17 DEBUG : vfs cache: data root is "/var/services/homes/user99/rclone/cache/vfs/wasabi01/zork"
2023/03/21 09:39:17 DEBUG : vfs cache: metadata root is "/var/services/homes/user99/rclone/cache/vfsMeta/wasabi01/zork"
2023/03/21 09:39:17 DEBUG : Creating backend with remote "/var/services/homes/user99/rclone/cache/vfs/wasabi01/zork"
2023/03/21 09:39:17 DEBUG : Creating backend with remote "/var/services/homes/user99/rclone/cache/vfsMeta/wasabi01/zork"
2023/03/21 09:39:17 DEBUG : vfs cache RemoveNotInUse (maxAge=3600000000000, emptyOnly=false): item d.txt not removed, freed 0 bytes
2023/03/21 09:39:17 INFO  : vfs cache: cleaned: objects 1 (was 1) in use 0, to upload 0, uploading 0, total size 29 (was 29)
2023/03/21 09:39:17 DEBUG : S3 bucket zork: Mounting on "/var/services/homes/user99/rclone/mount/remote"
2023/03/21 09:39:17 DEBUG : : Root:
2023/03/21 09:39:17 DEBUG : : >Root: node=/, err=<nil>

ncw · March 21, 2023, 3:44pm

Nice one That looks to be a reasonable solution for the fuse3 problem.

asdffdsa · March 21, 2023, 3:48pm

@Dong_Hyun_Choi, can you create the symlink and test?

ln -s /bin/fusermount /bin/fusermount3

Dong_Hyun_Choi · March 22, 2023, 4:39am

It works great!!! Thanks!!!

Dong_Hyun_Choi · March 22, 2023, 4:41am

Many thanks. It works perfect!!!! Really thanks for your help!

asdffdsa · March 22, 2023, 12:41pm

i posted at the fuse mailing list, and was told the symlink is not a supported solution.

On Tue, 21 Mar 2023, at 16:20, asdffdsa6132 via fuse-devel wrote:
> hello, thanks, first time poster, hope my question is acceptable.
>
> on some systems, cannot install fusermount3, such as synology machines.
> for example, latest version of rclone has switched to fusermount3, so rclone mount would not work anymore
>
> i have found that if a create a symlink, then rclone mount works again
> """
> ln -s /bin/fusermount /bin/fusermount3
>
> ls -l /usr/bin/fusermount3
> lrwxrwxrwx 1 root root 15 Mar 21 09:36 /usr/bin/fusermount3 -> /bin/fusermount
> """
>
> so please, is this a supported workaround or is there any other such advice to how to get this done?

Even though this will often work, it is not a supported workaround.

If the filesystem is linked against libfuse3, then fuse3 binaries need to be installed.

Best,
-Nikolaus

ncw · March 22, 2023, 3:56pm

rclone mount isn't linked agaiinst libfuse3 - it reimplements it in the bazil/fuse library.

So the kernel needs to support the fuse3 interface. However this has been standard for > 10 years now I understand.

Here is the upstream commit which changed it to use fusermount3 - it has some interesting points there.

github.com/bazil/fuse

Switch to calling fusermount3

committed 08:01PM - 09 Dec 22 UTC

tv42

+4 -4

The C FUSE library maintainers released the new major version v3 in 2013, and as… part of that also renamed the system tool that has nothing to do with whether applications use the C library or not. (If anything, it's tied to the kernel version being run, and Linux is excellent about not breaking userspace ABI compatibility.) Apparently, some distros are starting to drop libfuse v2, and in the process only provide `fusermount3` instead of the slightly more sanely named `fusermount`. (Historically, users needed to run the `fusermount` tool instead of the regular `umount` to unmount FUSE filesystems, but apparently that obscure historical misdesign has been fixed, and `umount` works. Personally, I dislike the design where mounts are SUID userspace fiddly things that attempt to duplicate kernel data structures in `/etc/mtab`, prefer hosts where `/etc/mtab` is obsoleted by `/proc/mounts` etc, and think the `user_id` comparison should live in the kernel.) Apparently the two versions of `fusermount` are fully compatible, but instead of maintaining it as a separate system tool, belonging more to something like coreutils or the kernel, libfuse maintainers consider it a part of the C libfuse library, thus making all other FUSE server implementations second class citizens. Oh well. Suck it up, go with the flow, and call `fusermount3`. For now, we're choosing not to include a backwards compatible path, trying both names. `fusermount3` apparently has been a thing since 2013, so you've had plenty of time to get it installed. If this causes issues, please let us know, backwards compatibility can be added as needed. Closes #275

This bit in particular

Apparently the two versions of fusermount are fully compatible

So it seems symlinking is a good solution!

I made an upstream issue about this here: fusermount3 not found on all systems - fall back to fusermount? · Issue #298 · bazil/fuse · GitHub

system · March 25, 2023, 3:57pm

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.