You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
a few weeks back i submitted an issue that should have probably been placed here from the beginning as a general question.
for reference its this #485
I noticed this first when using rclone and I thought it was an rclone issue, but as a sanity check I have also tested this with just uploading files in the tgdrive web ui and i see the issue there as well.
here is whats happening
i have the tgdrive setting "Split File Size" set to 1GB and i also have the "Upload Concurrency" setting set to 8 and have multiple bots added to tgdrive. I also have encryption enabled but the issue persists even with encryption disabled.
now if i run "df -h" on my host system before starting the upload i get this
Filesystem Size Used Avail Use% Mounted on
...
/dev/mapper/almalinux-root 99G 67G 33G 68% /
...
if i start an upload that is larger than 1GB (i tested with a 20GB ish file), then i can run df -h while the upload is taking place and i can see that my space available gradually reduces from 33G to 25G. After the upload finishes my available space goes back to 33G
since this is a decrease of 8gb i made the assumption that the tgdrive container is temporarily using 1GB per concurrent upload. since i set that to 8 and i set split file size to 1GB.
at one point i ran du -f on the docker overlay directory during an upload and could confirm that this is increasing the size of some container so im guessing its the tgdrive container and not the postgres container.
i thought tgdrive must have some sort of tmp directory or something and i submitted my issue to ask that question but now after seeing that reply im not sure whats going on.
im thinking my next steps would be to use a busybox executable as iwconfig mentioned in his reply, to run similar tests from inside the tgdrive container and see if i can verify that the container is using more drive space and what/where those files are being created ..... or would anyone recommend any other trouble shooting steps?
i dont know that this is needed but ill paste my docker compose here just in case anyone is curious
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
a few weeks back i submitted an issue that should have probably been placed here from the beginning as a general question.
for reference its this #485
I noticed this first when using rclone and I thought it was an rclone issue, but as a sanity check I have also tested this with just uploading files in the tgdrive web ui and i see the issue there as well.
here is whats happening
i have the tgdrive setting "Split File Size" set to 1GB and i also have the "Upload Concurrency" setting set to 8 and have multiple bots added to tgdrive. I also have encryption enabled but the issue persists even with encryption disabled.
now if i run "df -h" on my host system before starting the upload i get this
if i start an upload that is larger than 1GB (i tested with a 20GB ish file), then i can run df -h while the upload is taking place and i can see that my space available gradually reduces from 33G to 25G. After the upload finishes my available space goes back to 33G
since this is a decrease of 8gb i made the assumption that the tgdrive container is temporarily using 1GB per concurrent upload. since i set that to 8 and i set split file size to 1GB.
at one point i ran du -f on the docker overlay directory during an upload and could confirm that this is increasing the size of some container so im guessing its the tgdrive container and not the postgres container.
i thought tgdrive must have some sort of tmp directory or something and i submitted my issue to ask that question but now after seeing that reply im not sure whats going on.
im thinking my next steps would be to use a busybox executable as iwconfig mentioned in his reply, to run similar tests from inside the tgdrive container and see if i can verify that the container is using more drive space and what/where those files are being created ..... or would anyone recommend any other trouble shooting steps?
i dont know that this is needed but ill paste my docker compose here just in case anyone is curious
also my config.toml file with some stuff redacted
Beta Was this translation helpful? Give feedback.
All reactions