Rclone mount (for Plex) error - no space left on device

I'm having some issues getting rclone mount to work on a QNAP NAS.

I go gdrive > cache > crypt which seems to work fine on Windows 10 but when I mount on my QNAP box I get tons of no space left on device errors. Now, after an hour or so, it closes the mount and won't let me re-mount any more.

(I thought this would be easier to set up that a union between the local storage on the NAS and the storage I want to mount for Plex which contains a subset of the local media as well as some additional files not present in the local storage.)

[~] # rclone mount -v --allow-other remote-plexcache-crypt: /mnt/remote-plex
2019/06/17 18:15:52 Failed to save config after 10 tries: Failed to write temp config file: write /root/.config/rclone/rclone.conf865363640: no space left on device

Anyone got some experience with sorting this error?

I'm not much of help on a QNAP NAS other than the message is telling you that you ran of out space on your root volume.

How much is there?

You can probably reduce your cache and delete all the chunks and make it something that fits so it can mount.

What path are you using under QNAP? Are you sure that is correct (going to the correct storage partition) and not somewhere with only a small amount of space.

What does rclone about qnap: say? (or whatever you called your qnap remote).

I'm not sure if I'm using the cache correctly here. I'm working as root but I'm not sure if it's got write access to /root/.cache/rclone/cache-backend/.

There's about 1TB free space on the NAS so that shouldn't be an issue.

I cribbed from various sources and tried with the following flags but it still didn't seem massively stable:

--allow-other
--buffer-size 1G
--dir-cache-time 96h
--drive-chunk-size 32M
--timeout 1h
--umask 002
--cache-dir /share/plexcache
--cache-db-path /share/plexcache
--cache-db-purge

What do you mean by "path" here?

[~] # rclone -v about plexcache-crypt:
2019/06/18 15:31:27 INFO  : plexcache: Cache DB path: /root/.cache/rclone/cache-backend/plexcache.db
2019/06/18 15:31:27 INFO  : plexcache: Cache chunk path: /root/.cache/rclone/cache-backend/plexcache
2019/06/18 15:31:27 INFO  : plexcache: Chunk Memory: true
2019/06/18 15:31:27 INFO  : plexcache: Chunk Size: 16M
2019/06/18 15:31:27 INFO  : plexcache: Chunk Total Size: 20G
2019/06/18 15:31:27 INFO  : plexcache: Chunk Clean Interval: 1m0s
2019/06/18 15:31:27 INFO  : plexcache: Workers: 4
2019/06/18 15:31:27 INFO  : plexcache: File Age: 2d
2019/06/18 15:31:27 INFO  : plexcache: Cache DB path: /root/.cache/rclone/cache-backend/plexcache.db
2019/06/18 15:31:27 INFO  : plexcache: Cache chunk path: /root/.cache/rclone/cache-backend/plexcache
2019/06/18 15:31:27 INFO  : plexcache: Chunk Memory: true
2019/06/18 15:31:27 INFO  : plexcache: Chunk Size: 16M
2019/06/18 15:31:27 INFO  : plexcache: Chunk Total Size: 20G
2019/06/18 15:31:27 INFO  : plexcache: Chunk Clean Interval: 1m0s
2019/06/18 15:31:27 INFO  : plexcache: Workers: 4
2019/06/18 15:31:27 INFO  : plexcache: File Age: 2d
Used:    6.399T
Trashed: 12.832G
Other:   0
2019/06/18 15:31:27 INFO  : plex: stopped Plex watcher
2019/06/18 15:31:27 INFO  : plex: stopped Plex watcher

You don't on your / partition I guess as your out of space based on the error you are getting.

Which partition are you referring to? I've only used cache > crypt on Windows before so I'm not sure where it needs the space.

There's only one partition/volume on the QNAP.

Whatever that is.

I'm not sure if /root is it's own or what.

Right. So using --cache-db-path with a 100% writeable directory should fix it then?

Without knowing what your file systems are, it's really a guess.

If you can share some output of what the file systems look like, that would help.

Having something 100% full is generally bad.

Nothing is close to being full.

I said I pointed it to a 100% writeable folder with >1TB free using that switch. Should it fix that error?

I'm guessing I'm also asking what other options I need to use on a NAS.

The place you are running the mount command, can you run a "df -h" or something along those lines to show the mount points and what they are?

Ahhhhhhh! I had no idea the place you ran the command made a difference...

edit: actually it seems it doesn't on testing...

In the box were you typed the rclone mount command, run df -h

and check the disk space.

[share/plexcache] # df -h
Filesystem Size Used Available Use% Mounted on
none 250.0M 233.4M 16.6M 93% /
devtmpfs 3.8G 8.0K 3.8G 0% /dev
tmpfs 64.0M 480.0K 63.5M 1% /tmp
tmpfs 3.8G 8.0K 3.8G 0% /dev/shm
tmpfs 16.0M 0 16.0M 0% /share
tmpfs 16.0M 0 16.0M 0% /mnt/snapshot/export
/dev/md9 499.5M 138.7M 360.8M 28% /mnt/HDA_ROOT
cgroup_root 3.8G 0 3.8G 0% /sys/fs/cgroup
/dev/mapper/cachedev1
27.9T 24.3T 3.6T 87% /share/CACHEDEV1_DATA
/dev/mapper/vg1-snap10001
27.9T 24.2T 3.7T 87% /mnt/snapshot/1/10001
/dev/md13 355.0M 337.1M 17.9M 95% /mnt/ext
tmpfs 16.0M 40.0K 16.0M 0% /share/CACHEDEV1_DATA/.samba/lock/msg.lock
tmpfs 16.0M 0 16.0M 0% /mnt/ext/opt/samba/private/msg.sock
tmpfs 1.0M 0 1.0M 0% /mnt/rf/nd
/dev/mapper/cachedev1
27.9T 24.3T 3.6T 87% /lib/modules/4.2.8/container-station
/dev/mapper/cachedev1
27.9T 24.3T 3.6T 87% /share/CACHEDEV1_DATA/.qpkg/container-station/system-docker/plugins
/dev/mapper/cachedev1
27.9T 24.3T 3.6T 87% /share/CACHEDEV1_DATA/.qpkg/container-station/system-docker/overlay

3.6TB free in the /dev/mapper/cachedev1 which is where /share/ lives.

The problem is that there is no space in the root file system where rclone is trying to store its config file.

Rclone is using /root to store its config file which appears to only have 16M free space. Is it a RAM disk?

You can use --config to point the config file elsewhere.

1 Like

Thanks.

So...

Should be okay?

I'm already using --config for a config file elsewhere.

I suggests you set --cache-dir to somewhere other than the /root this should move all the cache stuff elsewhere.

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