I just found your stuff last night by accident, haha. I was having an issue with rClone and I found a post you made about go1.10 or something like that having an error with drive labels. Soon as I get back to my hotel, I’ll look into reconfiguring plex. I might hold off until I get my new dedicated server.
@Animosity022 here I am again… Everything was working good and fast. And since two days I’m getting bannned on the download quota. Ever had that before? I start a movie in the morning and later in the day I hit it. Uploading still works, but downloading doesn’t cause I’m banned.
My mount: rclone mount --rc --allow-other --buffer-size 1G --dir-cache-time 72h --drive-chunk-size 256M --fast-list --log-level INFO --vfs-read-chunk-size 128M --vfs-read-chunk-size-limit off gdrive_crypt: /mnt/user/mount_rclone/Gdrive &
2018/12/08 07:37:39 ERROR : Films/Troy (2004)/Troy (2004).mkv: ReadFileHandle.Read error: low level retry 1/10: read tcp 10.0.0.60:57068->172.217.17.74:443: i/o timeout
2018/12/08 09:10:19 ERROR : Films/Troy (2004)/Troy (2004).mkv: ReadFileHandle.Read error: low level retry 1/10: read tcp 10.0.0.60:47412->172.217.168.202:443: i/o timeout
2018/12/08 10:58:32 ERROR : Films/Murder on the Orient Express (2017)/Murder on the Orient Express (2017).mkv: ReadFileHandle.Read error: low level retry 1/10: couldn't reopen file with offset and limit: open file failed: googleapi: Error 403: The download quota for this file has been exceeded., downloadQuotaExceeded
Are you linking files for others to download? If you are, that could be your problem. There’s no download cap when using rClone, at least not one I’ve encountered. I just pulled 35TB of data off Google G Suite.
I only use the Gdrive for streaming and backing up. I don’t get 10TB of traffic, so I think it has to do with files being opened over and over again or something.
Version is the latest beta.
I’m currently trying to create a new API and have that working but I keep getting locked out because of the bans.
Just switched to the stable version 1.45 (was on beta 1.45.031). Also created a new API and rebuild my whole rclone config. Currently it is working again. Got my DEBUG log on, so hopefully I can catch it if it goes wrong again.
A few questions about your choices of flags again:
buffer-size -> why only 256M? It seems the common choice is 1G.
drive-chunk-size -> why only 32M? I’ve read NCW say that the bigger the better.
you only have the -rc flag. @BinsonBuzz uses this command aswell: rclone rc --timeout=1h vfs/refresh recursive=true. Now -rc is a bit of a black box for me. So I think the --timeout flag waits the directory caching for 1hr. But I don’t exactly know what the other flags do and why you don’t use those.
buffer-size is more hardware dependent on your workload and how much extra memory you have available. It is used per file so if you have 100 files open with a buffer-size of 1G, you consume 100G of memory. For most things, you can leave it at the default as it really depends on your use case. I recently tested with 16M and noticed no issues/challenges. I bumped it up to 256M to try as I have a lot of spare memory on my system so for me, it’s resources not being used that can help. The big thing to think about is waste though. If you have players that constantly open and close, having a large buffer would cause a lot of waste as on a file close, the buffer is dumped.
rc just runs another server that listens for commands to execute. You can do quite a lot with the rc commands, but not secured or exposed, they can give too much access. I run with rc and use the refresh as well on boot as that’s a little faster to ‘prime’ up the cache. This isn’t needed and I only use it as I’m impatient and want the first scan to be quick. Normally, the scan would build the cache anyway .
So my gdrive mount was cached and in the last 3 hours the new mount and API is live I’ve hit about 40.000 API hits. Is this normal for a first time API usage or after mounting?
Thanks for the reference. I’m at about 30TB and had only 2-3 streams. Will see what tomorrow brings after it settles down and if things are still working.
The bans started after I updated my rclone to the latest beta. So maybe something has changed which impacts this.
I had created a rclone cache mount. May I know how it is actually taking effect when the same local cached file is reopen to access, or any keyword I can locate from the log file?
I’m running Emby only at the moment and it should have already scanned my whole library, so I don’t understand why all these API hits are happening.
Any clue? I can share with you my whole log, but I would like to do that private, since it contains all my files.