DZMM

No. A team drive created by a google app user (who has unlimited storage) can be shared with any google account user(s). So, you could create team drives for friends to give them unlimited storage. Each user has a 750GB/day upload quota, so as long as each upload to the shared teamdrive is coming from a diff user (diff rclone token for the remote, and client_ID to try and avoid API bans) then you can utilise the extra quotas. I've added 3 accounts to my plex teamdrive and it's all working fine so far for 4 uploads (3 shared users and my google apps account) I imagine google has a FUP to clamp down on real abuse e.g. creating 100 teamdrives.

rclone move automatically retries failed transfers so you'll be ok - it's why it's best to upload via move rather than writing direct to the mount, because if the write fails there it's permanent.

My Mariadb mysql log folder keeps growing and has now hit 10GB - I only have 17GB or so of files in nextcloud! Is there something I'm supposed to do to keep the log size down? Thanks

Just create another encrypted remote for Bazarr with a different client_ID pointing to same gdrive/tdrive e.g. [gdrive_bazarr] type = drive client_id = Diff ID client_secret = Diff secret scope = drive root_folder_id = service_account_file = token = {should be able to use same token, or create new one if pointed to teamdrive"} [gdrive_bazarr_vfs] type = crypt remote = gdrive_bazarr:crypt filename_encryption = standard directory_name_encryption = true password = same password password2 = same password One problem I'm encountering is the multiple upload scripts are using a fair bit of memory, so I'm investigating how to reduce the memory usage by removing things like --fast-list from the upload script. Not a biggie as I can fix

This is working very well. I just moved files within google drive between My Drive and the Team Drive and once the dir cache updated, they appeared in the tdrive mount and played perfectly 🙂 I'm going to do a few more trial moves, which if go well I'm going to move all my files to the teamdrive and only upload to it going forwards. I wonder if google realise one user can create multiple teamdrives to share with friends to give them unlimited storage?

I have just one rclone_upload folder and then I created 3 upload scripts - one uploads /mnt/cache/rclone_upload, another /mnt/user0/rclone_upload and the third is a booster and currently is uploading from /mnt/disk4/rclone_upload. Yes, one tdrive with multiple accounts - one for each upload instance. Then there's only one tdrive to mount. Check my GitHub scripts for how I added in tdrive support. The mount I did for the 3rd user was just temporary to double-check it all worked as expected. To add each user just create new tdrive remotes with the same tdrive Id, rclone passwords, same remote location but different user tokens for each (and client IDs to spread the API hits)

I have 8.6G of logs - can I delete all of them and how can I stop this happening in the future? Thanks root@Highlander:/mnt/cache/appdata/dockers/mariadb# du -h --max-depth=1 | sort - hr 11G . 8.6G ./log 1.7G ./databases

Ok checked the 3rd user is working properly by creating a new remote using this user's token and then mounting it - it decrypted the existing folders and files correctly, so the password/encrypt sync worked 🙂 🙂

hmm not sure what was going on. I created a new teamdrive 'crypt' and the obscured file and folder names match up, regardless of what level I place the crypt. I'm going to ditch the first teamdrive I created and use this one and just doublecheck names manually the first time I decide to transfer files, if I do. I've added two users to this teamdrive so I'm up to 3x750GB per day - I'll only use the 3rd upload manually as I won't need that very often.

That could be it. My gdrive path is Gdrive/crypt/then_encrypted_media_folders and my team drive is Gdrive/highlander(name of tdrive)/crypt/then_encrypted_media_folders - Maybe if I named the tdrive 'crypt' and put the media folders in the root the names would match up. You're not really supposed to encrypt the root of a remote (will check why as not sure) I'm going to test now by creating a teamdrive called crypt and adding folders to its root.

yep - that's what I thought as well. Options I choose are: - 2 / Encrypt the filenames - 1 / Encrypt directory names - 1 Password or pass phrase for encryption. y) Yes type in my own password - Password or pass phrase for salt. y) Yes type in my own password

I use the same passwords for both mounts, different IDs (tried same didn't fix the problem) but different tokens because using two different google accounts. I'm not sure what rclone uses to encrypt but I'm guessing the tokens are the reason or the actual remote name. I'm hoping there is a fix. But, it's not a big problem as everything 'works' - it'd just be nice to have the option of being able to move files between remotes. It's made such a big difference today having another another 750GB or 70Mbps upload, as the single 750GB limit has been a pain in the ass for the last couple of months as I've had to manually manage how fast my rclone_upload backlog grew whereas now it's finally shrinking. I think I'm going to create a 3rd team drive tomorrow.

unfortunately I can't move files as the encryption is different - I think because I'm using different tokens. I've asked on the rclone forums if there's a way around this because I'd like to periodically move all files to one location

I just made a very useful change to my scripts that has solved my problem with the limit of only being able to upload 750GB/day, which was creating bottlenecks on my local server as I couldn't upload fast enough to keep up with new pending content. I've added a Teamdrive remote to my setup, that allows me to upload another 750GB/day in addition to the 750GB/day to my existing remote. This is because the 750GB/day limit is per account - by sharing the teamdrive created by my google apps account with another google account I can upload more. Theoretically I could repeat for n extra accounts (each one would need a separate token team drive), but 1 is enough for me. Steps: create new team drive with main google apps account share with 2nd google account create new team drive remotes (see first post) - remember to get token from account in #2 not account in #1 otherwise you won't get 2nd upload quota amend mount script (see first post) to mount new tdrive and change unionfs mount from 2-way union to 3-way including tdrive new upload script to upload to tdrive - my first upload script moves files from the array, and the 2nd from the cache. Another way to 'load-balance' the uploads could be to run one script against disks 1-3 and the other against 4-x add tdrive line to cleanup script add tdrive line to unmount script Optional repeat if need more upload capacity e.g. change 3-way union to 4-way

if you set your appdata, mount_rclone and mount_unionfs to cache only that should do the trick. I thought touch created the necessary directory tree? If not, glad you figured out how to fix.

That's a lot - check out https://www.hetzner.com/sb or https://github.com/Admin9705/PlexGuide.com-The-Awesome-Plex-Server/wiki/Recommend-Hosting-Servers @nuhll that's a bad way to do it IMO. How much are you spending? You could probably spend the same on a dedicated server from the links above and get gigabit speeds and processing power to run your plex server without using any of your home bandwidth

What's your VPS spec and how did you set it up? I might have to do this next year as I might be moving from 300/300 to an area where the upload is only about 30. Going to read up on 2.4.4_1 now

I wouldn't rely on resume working with gdrive as it doesn't work yet https://github.com/ncw/rclone/issues/87

Safest way is to create a new remote gdrive_new: and add this to your scripts IMO the script sounds like a bad idea. Upload doesn't resume so if you've spent 2 hours to reach 99% of a file uploaded and then stop, you'll have to start all over again. I'd recommend using bwlimit to schedule peak and off-peak upload speeds, or just do overnight. If you have to police your upload i.e. you can't comfortably upload 500-750GB/day then the service becomes less useful. Edit: or find a way to traffic shape the rclone upload e.g. pfsense

@nuhll is everything else working ok now?

Anyone else having problems with radarr & sonarr connecting to Jackett? Edit: ignore - somehow my API key changed

yes, the mountcheck file is created outside of rclone by running these two commands which creates the file and then moves it to the root of the rclone mount: touch mountcheck rclone copy mountcheck gdrive_media_vfs: -vv --no-traverse once done you should have something looking like this when looking locally at mount_rclone and mount_unionfs: and on drive the mountcheck file is encrypted so it will have a funny name. I went back through this thread and your rclone remote names are the same as mine, so running the two commands above in terminal will definitely do the job.

It's earmarked for the next release, so fingers crossed https://github.com/ncw/rclone/milestone/33

If you are renaming files you've already uploaded, unfortunately this is what unionfs does. Hopefully rclone union in a future release will allow unraid users to ditch unionfs