RClone @ QNAP: mount helper error: fusermount3: if you are sure this is safe, use the 'nonempty' mount option

[nickiman]

Hi,

I´m having problems to make "rclone mount" with Google Drive running it in my QNAP NAS:

RClone - MyQNAP

The version is:

rclone v1.66.0
- os/version: qts 5.1.5 (20240219) (64 bit)
- os/kernel: 5.10.60-qnap (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.22.1
- go/linking: static
- go/tags: none

The script used is this:

rclone mount \
--config=/share/CACHEDEV3_DATA/.qpkg/RClone/.config/rclone/rclone.conf \
--allow-other \
--allow-non-empty \
--dir-cache-time=100h \
--log-level INFO \
--log-file /share/CACHEDEV3_DATA/.qpkg/RClone/LOGs/GD_nickidisk01_Peliculas_Clasicas_MicroHD.log \
--poll-interval 15s \
--user-agent RClone_Peliculas_Clasicas_MicroHD \
--rc \
--rc-addr :5573 \
--rc-no-auth \
--cache-dir /share/CACHEDEV3_DATA/Media/Cloud/Peliculas_Clasicas_MicroHD/ \
--vfs-cache-mode=full \
--vfs-cache-max-size 500G \
--vfs-cache-max-age 24h \
GD_nickidisk01:Peliculas_Clasicas_MicroHD/ /share/CACHEDEV3_DATA/Media/Cloud/Peliculas_Clasicas_MicroHD/ &

In the log file I get these messages:

2024/04/05 12:28:19 NOTICE: Serving remote control on http://[::]:5573/
2024/04/05 12:28:19 INFO  : vfs cache: cleaned: objects 0 (was 0) in use 0, to upload 0, uploading 0, total size 0 (was 0)
2024/04/05 12:28:19 mount helper error: fusermount3: mountpoint is not empty
2024/04/05 12:28:19 mount helper error: fusermount3: if you are sure this is safe, use the 'nonempty' mount option
2024/04/05 12:28:19 Fatal error: failed to mount FUSE fs: fusermount: exit status 1

And in the folder I can see this:

The fusermount3 message in the log say to use the variable 'nonempty' and that is the most weird because I´m using the --allow-non-empty option in the rclone mount script. I´ve tried to use the 'nonempty' including it in the script but "as expected" is not recognized by Rclone.

This rclone mount script was used one year ago without problems with a different "older" version of QNAP NAS firmware and an older version of Rclone running in it.

Regards

[asdffdsa (jojothehumanmonkey)]

@nickiman

mountpoint is not empty

is the mountpoint empty?

why did you choose to add --allow-non-empty?

99.99% of the time, --allow-non-empty is not required
should remove it, unless you are 1000% sure it is required.
it allows for over-mounting.

[nickiman]

Yes, it´s empty:

I´ve tried out the script without the --allow-non-empty variable.

rclone mount \
--config=/share/CACHEDEV3_DATA/.qpkg/RClone/.config/rclone/rclone.conf \
--allow-other \
--dir-cache-time=100h \
--log-level INFO \
--log-file /share/CACHEDEV3_DATA/.qpkg/RClone/LOGs/GD_nickidisk01_Peliculas_Clasicas_MicroHD.log \
--poll-interval 15s \
--user-agent RClone_Peliculas_Clasicas_MicroHD \
--rc \
--rc-addr :5573 \
--rc-no-auth \
--cache-dir /share/CACHEDEV3_DATA/Media/Cloud/Peliculas_Clasicas_MicroHD/ \
--vfs-cache-mode=full \
--vfs-cache-max-size 500G \
--vfs-cache-max-age 24h \
GD_nickidisk01:Peliculas_Clasicas_MicroHD/ /share/CACHEDEV3_DATA/Media/Cloud/Peliculas_Clasicas_MicroHD/ &

But the result is the same:

2024/04/05 14:39:25 NOTICE: Serving remote control on http://[::]:5573/
2024/04/05 14:39:26 INFO  : vfs cache: cleaned: objects 0 (was 0) in use 0, to upload 0, uploading 0, total size 0 (was 0)
2024/04/05 14:39:26 Fatal error: failed to mount FUSE fs: "/share/CACHEDEV3_DATA/Media/Cloud/Peliculas_Clasicas_MicroHD/" is not empty, use --allow-non-empty to mount anyway
2024/04/05 14:43:38 NOTICE: Serving remote control on http://[::]:5573/
2024/04/05 14:43:39 INFO  : vfs cache: cleaned: objects 0 (was 0) in use 0, to upload 0, uploading 0, total size 0 (was 0)
2024/04/05 14:43:39 Fatal error: failed to mount FUSE fs: "/share/CACHEDEV3_DATA/Media/Cloud/Peliculas_Clasicas_MicroHD/" is not empty, use --allow-non-empty to mount anyway

After try it I can see these folders again:

[asdffdsa (jojothehumanmonkey)]

ok, i think i found the issue.

you set the cache dir to the same dir as the mountpoint?
and that is why fusermount is complaining about a non-empty mountpoint.

please, instead of hard to read, tiny screen snippets, just copy and paste from the command line, ok?

[nickiman]

@asdffdsa

ok, i think i found the issue.

you set the cache dir to the same dir as the mountpoint?
and that is why fusermount is complaining about a non-empty mountpoint.

Yeah, mate you´re right! Sorry, I haven´t seen it

Thank you, now I can see the content.