Skip to content
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

VFS downloads until 0B is free on disk, then fails without any relevant error notice. #3505

Closed
jtagcat opened this issue Jul 3, 2021 · 10 comments

Comments

@jtagcat
Copy link

jtagcat commented Jul 3, 2021

How to use GitHub

  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Expected behaviour

Sync stops with a relevant error

Actual behaviour

User didn't have image previews, so they proceeded to mark 'always keep on this device' for every directory. Them having more files than space available on the disk, the disk filled up. I got a call for 'gmail is not opening', disk had 0B free.

On the server side, I figured out some large directories, that would likely be not needed. Unchecking the 'Always keep on this device' on the 2, and afterwards, again after a reboot 'Free up space' on the folders. The directories were not deflated, no error is reported.

I'm left with:
a) delete the files via client, files are deleted on the server, then restore files on server (not reasonable here)
b) Remove the sync connection, and re-add it. Takes about 6h+ per 100G, most files are ~4-8MiB. Massive downtime.

Client configuration

Client version: 3.2.3

Logs

Refusing to provide logs due to sensitive filenames. #3189

@github-actions
Copy link

github-actions bot commented Aug 3, 2021

This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

@github-actions github-actions bot added the stale label Aug 3, 2021
@jtagcat
Copy link
Author

jtagcat commented Aug 4, 2021

unstale

@github-actions github-actions bot removed the stale label Aug 5, 2021
@github-actions
Copy link

github-actions bot commented Sep 2, 2021

This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

@github-actions github-actions bot added the stale label Sep 2, 2021
@jtagcat
Copy link
Author

jtagcat commented Sep 2, 2021

unstale

@github-actions github-actions bot removed the stale label Sep 2, 2021
@github-actions
Copy link

github-actions bot commented Oct 1, 2021

This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

@github-actions github-actions bot added the stale label Oct 1, 2021
@jtagcat
Copy link
Author

jtagcat commented Oct 1, 2021

un
stale

@github-actions github-actions bot removed the stale label Oct 1, 2021
@github-actions
Copy link

This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

@github-actions github-actions bot added the stale label Oct 30, 2021
@jtagcat
Copy link
Author

jtagcat commented Oct 30, 2021

@claell is there free space monitoring? iirc there was? can the limit be bypassed with multiple transfers?

on explorer, you can't copy a 2G file, if the destination doesn't have the space (1.5G available), but you can start the copy of 2 1G files at the same time; the same could be happening with VFS adding thousands of files one-by-one

otherwise, gonna let it go stale

@github-actions github-actions bot removed the stale label Oct 31, 2021
@github-actions
Copy link

This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

@github-actions github-actions bot added the stale label Nov 28, 2021
@github-actions
Copy link

This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants