Rclone with autofs doesnt work any more

Help and Support
1

Hello,

using rclone together with autofs doesnt work any more.
There is a message saying too many sections with symbolic links.

Device: RaspberryPI4
OS: Raspian bullseye
Rclone: 1.52.3 (just updated with deb-File from rclone.org)
Mounter-Helper-Script from
https://github.com/rclone/rclone/wiki/rclone-mount-helper-script
is in
/usr/local/bin

Entry in autofs config file auto.master:
/mnt/googleDrives /etc/auto.gdrive -_netdev,--timeout=0

Entry in /etc/auto.gdrive:
Gdrive1 -fstype=fuse.rclonefs,config=/home/pi/.config/rclone/rclone.conf,allow-non-empty,uid=1000,gid=1003,dir-perms=0770,file-perms=0770,allow-other,fast-list,umask=002 :Gdrive1:

Mounting with rclone-Gui works
Mounting webdav via mount-command works
Mounting webdav via autofs works

I tried this:
Gdrive1 -fstype=fuse.rclonefs,config=/home/pi/.config/rclone/rclone.conf,allow-non-empty :Gdrive1:
But this also does not work.

Where is the error?

Thanks.

2

Can you post the error?

Did this work with a previous rclone - if so which version?

3

yes, when I configured rclone and autofs at the beginning of 2020, it worked very well.
But I cannot say which version of rclone I used there. I always take the Version from Raspi-repo "testing".

Fehler
Fehler906×305 37.4 KB

In journald, there are no error-messages for automount
Does rclone also write a log? If yes, where?

4

Can you try some different versions of rclone to see if we can pin down what changed in rclone?

Also are there symlinks involved?

Is the mount point empty?

I think you may have to add the option

--allow-non-empty

with autofs otherwise you get a lock up.

5

there are no symlinks.
if autofs is not running, the mount-point is empty, but the mount-point-folder exists.
As you can see my config, there is already the "allow-non-empty" Option mentioned

6

i made some tests.

  1. i tried all older versions of rcone from here:
    https://archive.raspbian.org/raspbian/pool/main/r/rclone/
    --> still have the problem

  2. i tried it with mount together with fstab as it is described here:
    https://github.com/rclone/rclone/wiki/rclone-mount-helper-script
    --> it worked

  3. i tried it with mount together with fstab and used the options I am using for autofs:
    Gdrive1:/ /mnt/googleDrivesGdrive1 fuse.rclonefs config=/home/pi/.config/rclone/rclone.conf,allow-non-empty,uid=1000,gid=1003,dir-perms=0770,file-perms=0770,allow-other,fast-list,umask=002 0 0
    --> it doesnt work

  4. i tried it with mount together with fstab and used the options I am using for autofs WITHOUT allow-non-empty:
    Gdrive1:/ /mnt/googleDrivesGdrive1 fuse.rclonefs config=/home/pi/.config/rclone/rclone.conf,allow-non-empty,uid=1000,gid=1003,dir-perms=0770,file-perms=0770,allow-other,fast-list,umask=002 0 0
    --> it works

Any idea why allow-non-empty is now wrong?

7

I think this issue describes the problem

And the root is that fuse3 has removed the nonempty mount option.

Does that make sense?

There is probably some docs which need fixing!

8

you are right.
I think the most important document is this one

9

Do you want to edit it?

10

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