TW

You can use `borg info repo::archive` and it will show you in the "deduplicated" column how much space is used exclusively by this single archive. It's practically not as helpful...

If you have "weird" space usage although you delete stuff: check if your repo is in append-only mode (by repo/config or by authorized_keys ssh forced command). As long as it...

There are 2 borg "fat binary" builds: - the one without extension is just a single, compressed file - the `*.tgz` one is a directory full of files, but otherwise...

Looks like the pCloud drive filesystem you use is misbehaved (like not POSIX compliant or having other consistency or behavioural issues) and triggers that assertion.

Maybe check if pCloud drive has some (debug) log and whether there are some warning or error messages logged in there.

I was curious and just signed up for pCloud trial. Let's see what i find... BTW, they are using macFUSE, that is the same FUSE implementation as `borg mount` uses...

Could be a race condition: - I directly used borg (no vorta), using 1.2-maint latest code - my first two test backups to pCloud **worked** - my 3rd test backup...

Did some more test backups, then this happened, different exception with `IOError`: ``` Exception ignored in: Traceback (most recent call last): File "/Users/tw/w/borg/src/borg/repository.py", line 192, in __del__ self.close() File "/Users/tw/w/borg/src/borg/repository.py",...

Guess pCloud is doing strange things internally. IIRC, borg does not create `lock.exclusive` directories suffixed by `(1)` or ` (2)` (notable is also the inconsistency of the latter having an...

`borg check` noted: ``` Failed to securely erase old repository config file (hardlinks not supported). Old repokey data, if any, might persist on physical storage. ``` Hardlinks unsupported: no big...