New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add --force-cleanup option to cleanup command #3964
Comments
Agree. cleanup doesn't seem to clean up everything, or doesn't work as intended. What's interesting is that I can run empty trash from the GDrive web site and it shows as empty. This command finds and deletes files that are 3+ months old: |
The cleanup call, calls Googles API to empty the trash which seems a bit nebulous. It sometimes takes days to work.
Well, we implemented clean up for Google Team drives with effectively that I'm pretty sure that running this code for both team drives and non team drives would do the right thing Lines 2476 to 2482 in d252816
Fancy giving that a go @biship or @kennyparsons ? |
Original forum discussion: https://forum.rclone.org/t/empty-google-drive-trash/14331/5
What is your current rclone version (output from
rclone version
)?What problem are you are trying to solve?
The
cleanup
command has some nebulous results, as seen in several of the forum posts. An alternative, more manual command I had great success with was:rclone delete gdrive: --drive-trashed-only --drive-use-trash=false --verbose=2 --fast-list
This command enumerated and manually deleted several terabytes of junk data sitting the trash, whereas the
cleanup
option was slow and results have varied for many.How do you think rclone should be changed to solve that?
I would like to see an additional flag, such as
--force-cleanup
, available to thecleanup
command. This flag would essentially be a shortcut to flip thecleanup
command to adelete
command with--drive-trashed-only
and--drive-use-trash=false
as default attached commands. The--forced-cleanup
flag ideally would also accept additional, existing flags, such as--fast-list
,--verbose=x
, etc.The text was updated successfully, but these errors were encountered: