How Crazy Would it Be to Mount with Default Options

Help and Support
#1

How crazy would it be to mount my rclone drive using default options pretty much?
What is absolutely essential that I modify in options/flags if my main use is plex/mergerfs?

[Unit]
Description=cloud
After=network-online.target
Wants=network-online.target

[Service]
Type=notify
KillMode=none
Environment=RCLONE_CONFIG=/opt/rclone/rclone.conf
RestartSec=5
ExecStart=/usr/bin/rclone mount cloud: /mnt/cloud \
        --allow-other \
        --uid 1000 \
        --gid 1000 \
        --umask 002 \
        --log-file /opt/rclone/logs/rclone.log \
        --log-level INFO \
        --rc \
        --rc-addr 127.0.0.1:5572 \
        --cache-dir=/data/.cache/cloud
ExecStop=/bin/fusermount -uz /mnt/cloud
ExecStartPost=/usr/bin/rclone rc vfs/refresh recursive=true --rc-addr 127.0.0.1:5572 _async=true
Restart=on-failure
User=user
Group=user
#2

tl;dr, just try the command.

not at all crazy but really depends on your use-case,
which service provider is cloud?:, internet performance, your host machine hardware, etc..

for me, when using rclone mount to stream media from my local emby server,
i use a minimal set of flags, no vfs file cache, similar to your example.

#3

google drive
yeah i tried it and don't notice much of a difference but i dont really know what to look for. video place about the same

#4

hey @VBB,
i know that gdrive supports polling but not sure how that plays out with rclone + plex and what rclone command to use?

#5

i've since changed it slightly to

[Unit]
Description=cloud
After=network-online.target
Wants=network-online.target

[Service]
Type=notify
KillMode=none
Environment=RCLONE_CONFIG=/opt/rclone/rclone.conf
RestartSec=5
ExecStart=/usr/bin/rclone mount cloud: /mnt/cloud \
        --allow-other \
        --uid 1000 \
        --gid 1000 \
        --umask 002 \
        --log-file /opt/rclone/logs/rclone.log \
        --log-level INFO \
        --user-agent rclone \
        --poll-interval 15s \
        --vfs-cache-mode full \
        --vfs-cache-max-size 350G \
        --vfs-cache-poll-interval 5m \
        --rc \
        --rc-addr 127.0.0.1:5572 \
        --cache-dir=/data/.cache/cloud
ExecStop=/bin/fusermount -uz /mnt/cloud
ExecStartPost=/usr/bin/rclone rc vfs/refresh recursive=true --rc-addr 127.0.0.1:5572 _async=true
Restart=on-failure
User=user
Group=user
#6

I disabled polling, because my mount is read only and entirely static. It's always best to start out with defaults and go from there. Here's my current mount:

rclone mount --attr-timeout 5000h --dir-cache-time 5000h --drive-pacer-burst 200 --drive-pacer-min-sleep 10ms --no-checksum --poll-interval 0 --rc --read-only --user-agent *******

#7

why did you decide read-only?

#8

I don't upload through the mount or make any changes to it. Seemed like the safest option to mount it read-only :stuck_out_tongue:

#9

makes sense.
does read-only kinda speed things up?

#10

Don't think it makes any difference.

#11

without vfs cache mode full doesn't it not support seeking because things are not being run from local disk?

#12

I've never used any cache and seeking works just fine. I just don't have the space for it or the need, really, because the connection is fast enough.

#13

what does yours look like?

#14

my command is basically the same as @VBB.
tho the overall hardware/vm and use-cases are quite different, the song remains the same.

#15

would you say there is a speed benefit to your mount being like that over a vfs cache?
my main thing is im wondering if i need vfs cache to alleviate rate limits because i have multiple apps scanning constantly

#16

most rcloners use --vfs-cache-mode-full

with gdrive api limits and multiple apps, if your hardware can handle it, i would use the vfs file cache.

#17

my hardware and internet is kinda really great. guess i'll use it

#18

guess ill go back to this

[Unit]
Description=cloud
After=network-online.target
Wants=network-online.target

[Service]
Type=notify
KillMode=none
Environment=RCLONE_CONFIG=/opt/rclone/rclone.conf
RestartSec=5
ExecStart=/usr/bin/rclone mount cloud: /mnt/cloud \
        --allow-other \
        --default-permissions \
        --uid 1000 \
        --gid 1000 \
        --dir-perms 777 \
        --file-perms 666 \
        --umask 002 \
        --log-file /opt/rclone/logs/rclone.log \
        --log-level INFO \
        --dir-cache-time 5000h \
        --drive-pacer-min-sleep 10ms \
        --drive-pacer-burst 200 \
        --poll-interval 30s \
        --rc \
        --user-agent rclone \
        --rc-addr 127.0.0.1:5572 \
        --cache-dir=/data/.cache/cloud \
        --drive-chunk-size 32M \
        --vfs-cache-mode full \
        --vfs-cache-max-size 350G \
        --vfs-cache-max-age 15m \
        --vfs-cache-poll-interval 5m \
        --vfs-read-ahead 2G \
        --vfs-read-chunk-size 32M \
        --vfs-read-chunk-size-limit off \
        --bwlimit 8650k:off \
        --transfers 3 \
        --bwlimit-file 20M
ExecStop=/bin/fusermount -uz /mnt/cloud
ExecStartPost=/usr/bin/rclone rc vfs/refresh recursive=true --rc-addr 127.0.0.1:5572 _async=true
Restart=on-failure
User=user
Group=user
#19

as i do not use gdrive+plex, cannot comment much on that.

but i noticed that for --vfs-read-ahead,
in the past, @Animosity022 used that, but currently does not.

i have always been confused about that flag, when to use it???
i wonder why, why i wonder about @Animosity022 removing that flag?

#20

If you are sequentially reading a file, it helps if you have an internet blip and you use using cache mode full. It's a very narrow use case for helping as in Plex/Emby, you'd have to be direct playing and get some latency with your cloud remote.

I found there was no need for it in my case so for simplicity, I removed it as I did test with it for a bit.