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

Borg continues even if cache partition fills up #8666

Open
drws opened this issue Feb 11, 2025 · 3 comments
Open

Borg continues even if cache partition fills up #8666

drws opened this issue Feb 11, 2025 · 3 comments
Milestone

Comments

@drws
Copy link

drws commented Feb 11, 2025

If the partition ~/.cache/borg resides on fills up (during create), Borg still continues, producing 'file not found' errors. Happened with the latest stable v1.4.0. A solution would be to detect the situation before zero free space is left, gracefully stop and produce .checkpoint (if necessary) while also clearly informing the user of the situation.

@ThomasWaldmann ThomasWaldmann added this to the 1.4.1 milestone Feb 16, 2025
@ThomasWaldmann
Copy link
Member

Can you please:

  • reproduce this
  • add the log output to the top post
  • describe whether that causes any permanent problem besides the fs being full

@drws
Copy link
Author

drws commented Mar 6, 2025

I encountered the issue in a production environment so I'd rather not try to reproduce the exact scenario (I could try something in a VM if it helps), but I do remember some specifics which might help. First of all, the listed not-found files were cache files, not the actual files processed. After seeing errors I stopped the operation with SIGINT, deleted the allegedly corrupted cache and enlarged its storage. Listing repository contents, a consistency check and successful later backups indicate repository is fine.

Thinking about it now I'm unsure whether I also did any server-side cleanup (besides the consistency check), could that be a problem?

@ThomasWaldmann
Copy link
Member

@drws I don't think a server-side cleanup should be needed if you ran into an out-of-space issue client-side.

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

No branches or pull requests

2 participants