borgbackup
Borg continues even if cache partition fills up
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.
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
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?
@drws I don't think a server-side cleanup should be needed if you ran into an out-of-space issue client-side.