Android error: failed to mount FUSE fs: fusermount: fork/exec fusermount: permission denied

What is the problem you are having with rclone?

Android Fatal error: failed to mount FUSE fs: fusermount: fork/exec /system/bin/fusermount: permission denied

Even running as root and even with what appear to be correct permissions. I checked the related posts but still could not solve the issue.

What is your rclone version (output from rclone version)

rclone: Version "v1.57.0-beta.5698.19fc1b2a9"
Android is version 7 on a rooted Samsung Galaxy S8 (stock firmware)

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


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

# rclone -vvv mount mypcloud: /mnt/cloud/mypcloud --gid 9997 --dir-perms 0771 --file-perms 0660 --umask=0 --allow-other
WARNING: linker: /data/data/com.termux/files/usr/bin/rclone: unsupported flags DT_FLAGS_1=0x8000001
2021/10/22 14:53:34 DEBUG : Setting --config "/data/data/com.termux/files/home/.config/rclone/rclone.conf" from environment variable RCLONE_CONFIG="/data/data/com.termux/files/home/.config/rclone/rclone.conf"
2021/10/22 14:53:34 DEBUG : rclone: Version "v1.57.0-beta.5698.19fc1b2a9" starting with parameters ["rclone" "-vvv" "mount" "mypcloud:" "/mnt/cloud/mypcloud" "--gid" "9997" "--dir-perms" "0771" "--file-perms" "0660" "--umask=0" "--allow-other"]
2021/10/22 14:53:34 DEBUG : Creating backend with remote "mypcloud:"
2021/10/22 14:53:34 DEBUG : Using config file from "/data/data/com.termux/files/home/.config/rclone/rclone.conf"
2021/10/22 14:53:34 INFO  : pcloud root '': poll-interval is not supported by this remote
2021/10/22 14:53:34 NOTICE: pcloud root '': --vfs-cache-mode writes or full is recommended for this remote as it can't stream
2021/10/22 14:53:34 DEBUG : pcloud root '': Mounting on "/mnt/cloud/mypcloud"
2021/10/22 14:53:34 Fatal error: failed to mount FUSE fs: fusermount: fork/exec /system/bin/fusermount: permission denied

The rclone config contents with secrets removed.

# cat /data/data/com.termux/files/home/.config/rclone/rclone.conf
type = pcloud
hostname =
token = {"access_token":"xxxxxxxxxxxxxxxx","token_type":"bearer","expiry":"0001-01-01T00:00:00Z"}

More info

# ls -la /system/bin/fusermount
-rwxrwxrwx 1 root root 95904 2021-10-22 01:56 /system/bin/fusermount

# echo $PATH

# ls -la /mnt/cloud/
total 0
drwx------  3 root root    60 2021-10-22 02:03 .
drwxr-xr-x 11 root system 240 2021-10-22 02:02 ..
drwxrwxrwx  2 root root    40 2021-10-22 02:03 mypcloud

Hi MtnX2,

I have limited experience with mounts and no experience with Android/termux, but let me give you a few trouble shooting tips:

  • Perhaps there is an issue with permissions on the folder(s) containing fusermount?
  • Are you able to execuce /system/bin/fusermount -V (to check permissions without rclone)
  • Do you know the reason for the linker Warning in the top of the log?

@asdffdsa I have seen you using rclone on termux, do you have any ideas?

rclone on termux can only mount if the device is rooted.

but here comes @ivandeex, so let's see what he/she/it has to say.

Android permissions is a special beast. Termux specifically delivers root-dedicated packages, including fuse. I think you should cross-post there for better chance to find authoritative advise.

We also have an android talent, one of termux contributors, who can help with your case - @x0b

Hi. I appreciate all the replies.

Yes, my device is rooted and I made sure to state that in the OP.

I am thinking about removing Termux. This is one reason why:

My device is rooted with SuperSU v2.82. I can run scripts as root without Termux, if needed.

I am grateful for any help and I will even happily pay for an expert's time to help me sort this issue out. I don't even ask for a guaranteed solution. I want to learn about the issue so I will be satisfied even if we fail, as long as I learn exactly what the problem is.

Latest status:
How to automate rclone-mount without Termux or Magisk? - Android Enthusiasts Stack Exchange

It seems to be working now. I need to do more testing, however.


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