TW
When I tried whoosh, I noticed: - takes additional time at / after each backup - consumes space per backup (not just once, as in the case of `locate`) -...
some work (mostly adding comments) was done in #2691 (but was not merged).
Hah. It always happens in the last line of that block, no matter what it is. `__exit__` of context manager maybe? Yup, it is `out_f.close()` that produces this `OSError`.
I don't think I've seen that for borg 2.0.0a3 recently. So, is something broken in borg, on freebsd, in llfuse?
I also tested on 3 different Linux dists, netbsd, openbsd and macOS - that issue did **not** show up there.
freebsd still broken as of today.
still broken for 2.0.0b1 and freebsd 13.1-release-p1.
borg does not try to optimize for (very) large files. if it creates a relatively small segment file way below `max_segment_size` because there was not more data at the time...
@robaato thanks for the update. btw, you don't need to create the repo dir first, borg init does that, too.
My first (install via pip from pypi package) and second impression (install from git repo) is also that it works. Installation is like on (native) Ubuntu (Trusty, 14.04). Only thing...