Borg Prune deletes the config?

[InnoDavi]

borg prune --list --prefix '{hostname}-' --keep-daily 10 is my simple statement to purging

Question: Why does this statement also delete the config file from the repo directory? Whats happend?

Backup works fine but 10 days over and the prune keep is on 10, config fle in Repo-Directory is deleted und Repo destroyed.

Cant understand why the config will be also deleted on pruning.
Can anyone help me where is my issue?

Adding following informations:

borg 1.1.18
NAME="CentOS Linux"
VERSION="7 (Core)"

we using a bash script to handle with cron.daily

#!/bin/sh

export BORG_REPO=/mnt/backupnas01/SERVER/

borg create                         \
    --verbose                       \
    --filter AME                    \
    --list                          \
    --stats                         \
    --show-rc                       \
    --compression lz4               \
    --exclude-caches                \
    --exclude-from ${HOME}'/.config/borg/exclude-list' \
    ::'{hostname}-{now}'            \
    /mnt/backup                     \
    /srv/FTP/                       \
    /srv/www/html/                  \


borg prune                          \
    --list                          \
    --prefix '{hostname}-'          \
    --keep-daily    10              \

thats all...
after keep-daily >= 10 it does delete the config...
but i doesnt understand why
...strange...

[ThomasWaldmann]

borg doesn't delete its config (AFAIK). to the contrary: it makes rather sure that even when updating it, it is always either the original old or the complete new version, but never something "in between".

so, either you have a fs (or other) issue there or you have found a severe, yet unknown bug in borg.

can you edit your top post and add more information or just file this as an issue and fill out all it asks for?

[ThomasWaldmann]

1.1.18 is rather old (as is your OS). can you run a more recent, still supported borg version on that, like 1.2.x maybe?

[ThomasWaldmann]

Closing this as outdated: it has seen no activity for a long time and predates the current borg releases.

If this still affects you on a current version - borg 1.4.x (stable) or the borg 2.0.0 beta - please open a new discussion with up-to-date details.