This is exactly how it does not work. If you upload the same file again and again every time it will result with different content and different hash as encryption keys are seeded with cryptographic salt. Effectively every file you upload is encrypted with different key even if it is the same file. It is important part of well designed encryption implementation (well done rclone) - making certain types of attacks on crypto impossible.
I stand corrected on the encryption part, that is actually great to know. I have not delved much into that area, but will be in the next few weeks, so thanks for pointing that out. It is actually awesome to know that tidbit!
lets say I have file1 - content "abcd" and file2 - content "efgh"
crypto keys are derived from password (and you need password to decrypt content) - I guess what you call master crypt remote you mean the same password everywhere.
Now what happens when you upload these two files to crypt:
file1 becomes XYYZABW with content "12345", file2 becomes KLMNVBN with content "67890" - note here that both file name length and content size increases (content by tiny almost ignorable %) - it is probably not so important on Google Drive when path length can be crazy long but is something to plan on other remotes. --crypt-filename-encoding best choice for Google Drive is base64
when you upload them again to some other folder:
file1 becomes XYYZABW with content "01924", file2 becomes KLMNVBN with content "73092"
files/names encryption produces always the same encrypted name. Content is always different and random.
You can not produce dupes - crypt abstraction layer behaves like any nice filesystem. You can not have two file1 in the same folder.
yes it would require rclone crypt v2 format with original hash included in metadata and also encrypted itself. Theory itself how to do it is not so complex but somebody has to implement it. Myself I use rclone chunker to achieve it - so I have original hashes available on all my crypt remotes - at the cost of extra metadata side car files - they are not visible though when accessing all remotes stack remote<-crypt<-chunker.
Just made a simple test.
I created two encrypted remote on a local 2 PB disk array with compression and data reduction (deduplication) acvite
Uploading the same file on the two remote has a payload of 2 times the single file size
The same test without encryption pays just 1 time the size.
I just jumped on the better Plan on google workspace and have endless resources to download and upload. If, anyone wants to subscribe to my drive then please write.
to go into it again. you said you also have an old account with only 1 user and no emails either. that would not speak for the fact that we should increase to 5 users as soon as possible to be save. my memory overview looks the same as yours.
Yes I agree 100% EVERYONE who has NOT gotten a notice and does NOT have 5 users should immediately upgrade their PAID user to 5.
I have many Workspace so this one I do not mind using as a test
But I feel many people do not realize that if they WAIT until Google sends the notice then it will probably be too LATE to adjust their account.
Once Google flags an account I doubt simply adding users will fix it. As in "my viewpoint" the account has NOT honored the Legacy upgrade by keeping 5 users, so Google could say Hey, you never had 5 users, so the UNLIMITED does not apply and you relinquished your right to keep it by not having the 5 users minimum requirement.
So if people even have a HOPE of keeping unlimited, my advice is UPGRADE to 5 paid users BEFORE Google warns you
Again my single user account I am simply using to see what happens, I have other Workspaces with more than 5 so it is easy for me to move the content if needed.
I have 5 users for about 3 years. I didn't get any emails from Google but i got a warning in the admin panel saying "To avoid service disruptions, free up space or get more storage within 33 days." now. So having 5 users won't protect anyone i suppose.
Can you send a screenshot of what the message looks like? Do not need to show any private info or even your total storage just the message itself area.
I am assuming the message is appearing at storage?
I do not think that this would be enough.
You suggest to add more users before getting the message from Google saying that you are running out of space since before the warning you are granted unlimited, right?
What about me?
I had UNLIMITED since Google Suite in 2018. When migrated to Workspace Enterprise I have been granted unlimited regardless rules saying that to get the unlimited at least 5 users were needed and without any notice since one week I have the red banner in the Admin page saying that I have 60 days to delete data or to add users before my account will be read only.
It is the same approach. Google simply does not care about in place agreements.
I had another conversation yesterday with Workspace support and no way... they suggest to me to get assistance from a lawyer.
Take care... I am not a users storing PetaByte of unwatched porno moviews... I store 12 TB of personal and family movies, pictures, etc....
