[Errno 18] Cross-device link #931

New Issue

Closed

opened 2024-11-08 02:00:39 +00:00 by modem7 · 13 comments

modem7 commented 2024-11-08 02:00:39 +00:00

Copy Link

What I'm trying to do and why

Backups started failing in 1.9.0. Probably me not RTFMing and understanding the release notes re "Move the default check state directory".

summary:
/etc/borgmatic.d/config.yml: An error occurred
Borgbase: Error running actions for repository
[Errno 18] Cross-device link: '/root/.borgmatic/checks' -> '/root/.local/state/borgmatic/checks'

Steps to reproduce

source_directories:
     - ${BORG_SOURCE_1}
     - ${BORG_SOURCE_2}
repositories:
     - path: ${BORG_REPO}
       label: Borgbase
one_file_system: true
exclude_caches: true

#storage:
#   Passphase is set in variable $BORG_PASSPHRASE
compression: lz4
archive_name_format: 'backup-{now}'

keep_hourly: 0
keep_daily: 7
keep_weekly: 4
keep_monthly: 12
keep_yearly: 1

checks:
#  - name: repository
#    frequency: 2 weeks
#  - name: archives
#    frequency: always
#  - name: extract
#    frequency: 2 weeks
#  - name: data
#    frequency: 1 month

before_everything:
#    - borgmatic break-lock
#    - echo "Starting a backup job."
    - echo "Stopping containers."
    - exec /borgscripts/docker-stop.sh
after_everything:
    - echo "Starting containers."
    - exec /borgscripts/docker-start.sh
    - echo "Backup created."
on_error:
    - echo "Error while creating a backup."
    - exec /borgscripts/docker-start.sh
    # https://torsion.org/borgmatic/docs/how-to/backup-your-databases/

healthchecks:
    ping_url: ${BORG_HEALTHCHECK_URL}

Actual behavior

No response

Expected behavior

No response

Other notes / implementation ideas

apprise 1.9.0
borg 1.4.0
borgmatic 1.9.0
dockercli 25.0.5
composecli 2.23.3
python 3.13.0

borgmatic version

No response

borgmatic installation method

No response

Borg version

No response

Python version

No response

Database version (if applicable)

No response

Operating system and version

No response

### What I'm trying to do and why Backups started failing in 1.9.0. Probably me not RTFMing and understanding the release notes re "Move the default check state directory". ``` summary: /etc/borgmatic.d/config.yml: An error occurred Borgbase: Error running actions for repository [Errno 18] Cross-device link: '/root/.borgmatic/checks' -> '/root/.local/state/borgmatic/checks' ``` ### Steps to reproduce ```yaml source_directories: - ${BORG_SOURCE_1} - ${BORG_SOURCE_2} repositories: - path: ${BORG_REPO} label: Borgbase one_file_system: true exclude_caches: true #storage: # Passphase is set in variable $BORG_PASSPHRASE compression: lz4 archive_name_format: 'backup-{now}' keep_hourly: 0 keep_daily: 7 keep_weekly: 4 keep_monthly: 12 keep_yearly: 1 checks: # - name: repository # frequency: 2 weeks # - name: archives # frequency: always # - name: extract # frequency: 2 weeks # - name: data # frequency: 1 month before_everything: # - borgmatic break-lock # - echo "Starting a backup job." - echo "Stopping containers." - exec /borgscripts/docker-stop.sh after_everything: - echo "Starting containers." - exec /borgscripts/docker-start.sh - echo "Backup created." on_error: - echo "Error while creating a backup." - exec /borgscripts/docker-start.sh # https://torsion.org/borgmatic/docs/how-to/backup-your-databases/ healthchecks: ping_url: ${BORG_HEALTHCHECK_URL} ``` ### Actual behavior _No response_ ### Expected behavior _No response_ ### Other notes / implementation ideas apprise 1.9.0 borg 1.4.0 borgmatic 1.9.0 dockercli 25.0.5 composecli 2.23.3 python 3.13.0 ### borgmatic version _No response_ ### borgmatic installation method _No response_ ### Borg version _No response_ ### Python version _No response_ ### Database version (if applicable) _No response_ ### Operating system and version _No response_

witten commented 2024-11-08 02:58:08 +00:00

Owner

Copy Link

Thanks for taking the time to file this! I think I have an idea of what might be going on.. Are /root/.borgmatic/checks and /root/.local/state/borgmatic/checks on different filesystems on your machine?

If that's the case, I have a way to fix the borgmatic code so that it can do cross-filesystem moves.

Thanks for taking the time to file this! I think I have an idea of what might be going on.. Are `/root/.borgmatic/checks` and `/root/.local/state/borgmatic/checks` on different filesystems on your machine? If that's the case, I have a way to fix the borgmatic code so that it can do cross-filesystem moves.

witten added the

bug

label 2024-11-08 02:58:14 +00:00

witten referenced this issue from a commit 2024-11-08 03:20:20 +00:00

Fix an error when implicitly upgrading the check state directory across filesystems (#931).

witten commented 2024-11-08 03:20:48 +00:00

Owner

Copy Link

Okay, I've pushed a fix to main, but it would still be good to confirm whether your two paths are on different filesystems. Thanks!

Okay, I've pushed a fix to main, but it would still be good to confirm whether your two paths are on different filesystems. Thanks!

witten closed this issue 2024-11-08 03:20:48 +00:00

xLogiiCx commented 2024-11-08 14:10:54 +00:00

Copy Link

Hi, i am having the same issue. Looking forward for the fix in main.

For me it is basically in two different file systems (running in docker /root/.borgmatic is mapped to a folder on my host and /root/.local/ is in a docker volume.

Hi, i am having the same issue. Looking forward for the fix in main. For me it is basically in two different file systems (running in docker `/root/.borgmatic` is mapped to a folder on my host and `/root/.local/` is in a docker volume.

witten commented 2024-11-08 15:17:43 +00:00

Owner

Copy Link

Thanks for weighing in. That makes sense as a use case where this issue would manifest.

Thanks for weighing in. That makes sense as a use case where this issue would manifest.

👍 1

modem7 commented 2024-11-09 03:46:54 +00:00

Author

Copy Link

This is my current compose file (which I realise I didn't post originally (derp))

  #############
  ##Borgmatic##
  #############

  borgmatic:
    image: modem7/borgmatic-docker
    # image: modem7/borgmatic-docker:1.8.13-1.4.0
    # image: borgmatic:test
    # image: ghcr.io/borgmatic-collective/borgmatic
    container_name: Borgmatic
    environment:
      TZ: $TZ
      BORG_PASSPHRASE: $BORG_PASSPHRASE
      BORG_SOURCE_1: $BORG_SOURCE_1
      BORG_SOURCE_2: $BORG_SOURCE_2
      BORG_REPO: $BORG_REPO
      BORG_HEALTHCHECK_URL: $BORG_HEALTHCHECK_URL
      # EXTRA_PKGS: postgresql16-client rclone coreutils jq
      DOCKERCLI: true
      CRON: $BORG_CRON
      CRON_COMMAND: $BORG_CRON_COMMAND
      # EXTRA_CRON: |-
      #   @daily borgmatic check -v 1 2>&1 > tee /mnt/log/check-$(date +\%Y-\%m-\%dT\%H:\%M:\%S).log
      #   0 7 1 * * command2
    logging:
      driver: "local"
      options:
        max-size: 10m
        max-file: "3"
    volumes:
      - $BORGHOMESOURCEDIR:/mnt/source/
      # - $CRONTAB:/mnt/source/Cron
      # - Pihole:/mnt/source/Pihole/Pihole
      # - Dnsmasq:/mnt/source/Pihole/Dnsmasq
      - $BORGSERVBACKUPDIR/Database:/mnt/borg-DBrepository
      - $BORGSERVBACKUPDIR/Docker:/mnt/borg-repository
      - $RAMDRIVEBACKUP/borg:/mnt/ramdrive
      - $USERDIR:/mnt/source/DockerApps/
      - $USERDIR/Borgmatic/borgmatic.d/:/etc/borgmatic.d/
      - $USERDIR/Borgmatic/.config/borg/:/root/.config/borg
      - $USERDIR/Borgmatic/.ssh/:/root/.ssh
      - $USERDIR/Borgmatic/.state/:/root/.borgmatic
      - $USERDIR/Borgmatic/.cache/borg/:/root/.cache/borg
      - $DOCKERDIR/HDA/.env:/mnt/docker/HDA/.env:ro
      - $DOCKERDIR/HDA/docker-compose.yml:/mnt/docker/HDA/docker-compose.yml:ro
      - $BORGSCRIPTS:/borgscripts:ro
      - /var/run/docker.sock:/var/run/docker.sock # So we can run scripts
      # - /mnt/downloads/script/:/custom-cont-init.d:ro
    networks:
      isonet:
      isolated:
    restart: always

So I'm not quite sure why it thinks it's going across filesystems in my particular case.

Hopefully the fix will resolve! Will test when it gets released!

This is my current compose file (which I realise I didn't post originally (derp)) ```yaml ############# ##Borgmatic## ############# borgmatic: image: modem7/borgmatic-docker # image: modem7/borgmatic-docker:1.8.13-1.4.0 # image: borgmatic:test # image: ghcr.io/borgmatic-collective/borgmatic container_name: Borgmatic environment: TZ: $TZ BORG_PASSPHRASE: $BORG_PASSPHRASE BORG_SOURCE_1: $BORG_SOURCE_1 BORG_SOURCE_2: $BORG_SOURCE_2 BORG_REPO: $BORG_REPO BORG_HEALTHCHECK_URL: $BORG_HEALTHCHECK_URL # EXTRA_PKGS: postgresql16-client rclone coreutils jq DOCKERCLI: true CRON: $BORG_CRON CRON_COMMAND: $BORG_CRON_COMMAND # EXTRA_CRON: |- # @daily borgmatic check -v 1 2>&1 > tee /mnt/log/check-$(date +\%Y-\%m-\%dT\%H:\%M:\%S).log # 0 7 1 * * command2 logging: driver: "local" options: max-size: 10m max-file: "3" volumes: - $BORGHOMESOURCEDIR:/mnt/source/ # - $CRONTAB:/mnt/source/Cron # - Pihole:/mnt/source/Pihole/Pihole # - Dnsmasq:/mnt/source/Pihole/Dnsmasq - $BORGSERVBACKUPDIR/Database:/mnt/borg-DBrepository - $BORGSERVBACKUPDIR/Docker:/mnt/borg-repository - $RAMDRIVEBACKUP/borg:/mnt/ramdrive - $USERDIR:/mnt/source/DockerApps/ - $USERDIR/Borgmatic/borgmatic.d/:/etc/borgmatic.d/ - $USERDIR/Borgmatic/.config/borg/:/root/.config/borg - $USERDIR/Borgmatic/.ssh/:/root/.ssh - $USERDIR/Borgmatic/.state/:/root/.borgmatic - $USERDIR/Borgmatic/.cache/borg/:/root/.cache/borg - $DOCKERDIR/HDA/.env:/mnt/docker/HDA/.env:ro - $DOCKERDIR/HDA/docker-compose.yml:/mnt/docker/HDA/docker-compose.yml:ro - $BORGSCRIPTS:/borgscripts:ro - /var/run/docker.sock:/var/run/docker.sock # So we can run scripts # - /mnt/downloads/script/:/custom-cont-init.d:ro networks: isonet: isolated: restart: always ``` So I'm not quite sure why it thinks it's going across filesystems in my particular case. Hopefully the fix will resolve! Will test when it gets released!

witten commented 2024-11-09 05:35:13 +00:00

Owner

Copy Link

Ah yeah. So it does appear that /root/.borgmatic would be on one filesystem (since it's a mounted volume) while /root/.local/state would be on another. Once you upgrade, it would be good to switch your volume mount from the former to the latter if you'd like check state to persist across container restarts.

Ah yeah. So it does appear that `/root/.borgmatic` would be on one filesystem (since it's a mounted volume) while `/root/.local/state` would be on another. Once you upgrade, it would be good to switch your volume mount from the former to the latter if you'd like check state to persist across container restarts.

witten commented 2024-11-10 16:28:04 +00:00

Owner

Copy Link

Fixed in borgmatic 1.9.1, just released!

Fixed in borgmatic 1.9.1, just released!

🚀 1

qymab commented 2024-11-11 10:50:07 +00:00

Copy Link

Fixed in borgmatic 1.9.1, just released!

Halo I'm experiencing this issue too.

this my docker compose

services:

  borgmatic:
    container_name: borgmatic
    image: ghcr.io/borgmatic-collective/borgmatic
    restart: always
    security_opt:
      - no-new-privileges:true
    networks:
      borg_proxy:
    volumes:
      - $VOLUME_SOURCE:/mnt/source:ro
      - $BORGDIR/data:/mnt/borg-repository
      - $BORGDIR/borgmatic.d:/etc/borgmatic.d/
      - $BORGDIR/.config/borg:/root/.config/borg
      - $BORGDIR/.ssh:/root/.ssh
      - $BORGDIR/.cache/borg:/root/.cache/borg
      - $BORGDIR/.borgmatic/:/root/.borgmatic
    environment:
      - TZ=$TZ

this my borgmatic config:

repositories:
    - path: ssh://
      label: rsync

one_file_system: true
read_special: true
encryption_passphrase: ""
compression: lz4
ssh_command: ssh
archive_name_format: '-rsync-{now}'

keep_daily: 5
keep_weekly: 4
keep_monthly: 3

checks:
    - name: repository
    - name: archives
      frequency: 2 weeks
check_last: 3

before_backup:
    - echo "Starting a backup rsync."
after_backup:
    - echo "Finished a backup rsync."
on_error:
    - echo "Error during create/prune/compact/check."

the error:

rsync: Error running actions for repository
[Errno 18] Cross-device link: '/root/.borgmatic/checks' -> '/root/.local/state/borgmatic/checks'

> Fixed in borgmatic 1.9.1, just released! Halo I'm experiencing this issue too. this my docker compose ``` services: borgmatic: container_name: borgmatic image: ghcr.io/borgmatic-collective/borgmatic restart: always security_opt: - no-new-privileges:true networks: borg_proxy: volumes: - $VOLUME_SOURCE:/mnt/source:ro - $BORGDIR/data:/mnt/borg-repository - $BORGDIR/borgmatic.d:/etc/borgmatic.d/ - $BORGDIR/.config/borg:/root/.config/borg - $BORGDIR/.ssh:/root/.ssh - $BORGDIR/.cache/borg:/root/.cache/borg - $BORGDIR/.borgmatic/:/root/.borgmatic environment: - TZ=$TZ ``` this my borgmatic config: ``` repositories: - path: ssh:// label: rsync one_file_system: true read_special: true encryption_passphrase: "" compression: lz4 ssh_command: ssh archive_name_format: '-rsync-{now}' keep_daily: 5 keep_weekly: 4 keep_monthly: 3 checks: - name: repository - name: archives frequency: 2 weeks check_last: 3 before_backup: - echo "Starting a backup rsync." after_backup: - echo "Finished a backup rsync." on_error: - echo "Error during create/prune/compact/check." ``` the error: ``` rsync: Error running actions for repository [Errno 18] Cross-device link: '/root/.borgmatic/checks' -> '/root/.local/state/borgmatic/checks' ```

xLogiiCx commented 2024-11-11 11:13:02 +00:00

Copy Link

Fixed in borgmatic 1.9.1, just released!

Halo I'm experiencing this issue too.

this my docker compose

services:

  borgmatic:
    container_name: borgmatic
    image: ghcr.io/borgmatic-collective/borgmatic
    restart: always
    security_opt:
      - no-new-privileges:true
    networks:
      borg_proxy:
    volumes:
      - $VOLUME_SOURCE:/mnt/source:ro
      - $BORGDIR/data:/mnt/borg-repository
      - $BORGDIR/borgmatic.d:/etc/borgmatic.d/
      - $BORGDIR/.config/borg:/root/.config/borg
      - $BORGDIR/.ssh:/root/.ssh
      - $BORGDIR/.cache/borg:/root/.cache/borg
      - $BORGDIR/.borgmatic/:/root/.borgmatic
    environment:
      - TZ=$TZ

this my borgmatic config:

repositories:
    - path: ssh://
      label: rsync

one_file_system: true
read_special: true
encryption_passphrase: ""
compression: lz4
ssh_command: ssh
archive_name_format: '-rsync-{now}'

keep_daily: 5
keep_weekly: 4
keep_monthly: 3

checks:
    - name: repository
    - name: archives
      frequency: 2 weeks
check_last: 3

before_backup:
    - echo "Starting a backup rsync."
after_backup:
    - echo "Finished a backup rsync."
on_error:
    - echo "Error during create/prune/compact/check."

the error:

rsync: Error running actions for repository
[Errno 18] Cross-device link: '/root/.borgmatic/checks' -> '/root/.local/state/borgmatic/checks'

Container „Latest“ is not version 1.9.1 yet.

> > Fixed in borgmatic 1.9.1, just released! > > Halo I'm experiencing this issue too. > > this my docker compose > > ``` > services: > > borgmatic: > container_name: borgmatic > image: ghcr.io/borgmatic-collective/borgmatic > restart: always > security_opt: > - no-new-privileges:true > networks: > borg_proxy: > volumes: > - $VOLUME_SOURCE:/mnt/source:ro > - $BORGDIR/data:/mnt/borg-repository > - $BORGDIR/borgmatic.d:/etc/borgmatic.d/ > - $BORGDIR/.config/borg:/root/.config/borg > - $BORGDIR/.ssh:/root/.ssh > - $BORGDIR/.cache/borg:/root/.cache/borg > - $BORGDIR/.borgmatic/:/root/.borgmatic > environment: > - TZ=$TZ > ``` > > this my borgmatic config: > > ``` > repositories: > - path: ssh:// > label: rsync > > one_file_system: true > read_special: true > encryption_passphrase: "" > compression: lz4 > ssh_command: ssh > archive_name_format: '-rsync-{now}' > > keep_daily: 5 > keep_weekly: 4 > keep_monthly: 3 > > checks: > - name: repository > - name: archives > frequency: 2 weeks > check_last: 3 > > before_backup: > - echo "Starting a backup rsync." > after_backup: > - echo "Finished a backup rsync." > on_error: > - echo "Error during create/prune/compact/check." > ``` > > the error: > > ``` > rsync: Error running actions for repository > [Errno 18] Cross-device link: '/root/.borgmatic/checks' -> '/root/.local/state/borgmatic/checks' > ``` Container „Latest“ is not version 1.9.1 yet.

👍 1

modem7 commented 2024-11-11 11:13:46 +00:00

Author

Copy Link

Fixed in borgmatic 1.9.1, just released!

Halo I'm experiencing this issue too.

this my docker compose

services:

  borgmatic:
    container_name: borgmatic
    image: ghcr.io/borgmatic-collective/borgmatic
    restart: always
    security_opt:
      - no-new-privileges:true
    networks:
      borg_proxy:
    volumes:
      - $VOLUME_SOURCE:/mnt/source:ro
      - $BORGDIR/data:/mnt/borg-repository
      - $BORGDIR/borgmatic.d:/etc/borgmatic.d/
      - $BORGDIR/.config/borg:/root/.config/borg
      - $BORGDIR/.ssh:/root/.ssh
      - $BORGDIR/.cache/borg:/root/.cache/borg
      - $BORGDIR/.borgmatic/:/root/.borgmatic
    environment:
      - TZ=$TZ

this my borgmatic config:

repositories:
    - path: ssh://
      label: rsync

one_file_system: true
read_special: true
encryption_passphrase: ""
compression: lz4
ssh_command: ssh
archive_name_format: '-rsync-{now}'

keep_daily: 5
keep_weekly: 4
keep_monthly: 3

checks:
    - name: repository
    - name: archives
      frequency: 2 weeks
check_last: 3

before_backup:
    - echo "Starting a backup rsync."
after_backup:
    - echo "Finished a backup rsync."
on_error:
    - echo "Error during create/prune/compact/check."

the error:

rsync: Error running actions for repository
[Errno 18] Cross-device link: '/root/.borgmatic/checks' -> '/root/.local/state/borgmatic/checks'

borgmatic-collective/borgmatic has not been updated to 1.9.1 just yet.

Please monitor borgmatic docker releases for an update.

Should hopefully be done in the next day or two.

Edit: @xLogiiCx - doi - just realised I replied to you. I think I need more coffee...

> > Fixed in borgmatic 1.9.1, just released! > > Halo I'm experiencing this issue too. > > this my docker compose > > ``` > services: > > borgmatic: > container_name: borgmatic > image: ghcr.io/borgmatic-collective/borgmatic > restart: always > security_opt: > - no-new-privileges:true > networks: > borg_proxy: > volumes: > - $VOLUME_SOURCE:/mnt/source:ro > - $BORGDIR/data:/mnt/borg-repository > - $BORGDIR/borgmatic.d:/etc/borgmatic.d/ > - $BORGDIR/.config/borg:/root/.config/borg > - $BORGDIR/.ssh:/root/.ssh > - $BORGDIR/.cache/borg:/root/.cache/borg > - $BORGDIR/.borgmatic/:/root/.borgmatic > environment: > - TZ=$TZ > ``` > > this my borgmatic config: > > ``` > repositories: > - path: ssh:// > label: rsync > > one_file_system: true > read_special: true > encryption_passphrase: "" > compression: lz4 > ssh_command: ssh > archive_name_format: '-rsync-{now}' > > keep_daily: 5 > keep_weekly: 4 > keep_monthly: 3 > > checks: > - name: repository > - name: archives > frequency: 2 weeks > check_last: 3 > > before_backup: > - echo "Starting a backup rsync." > after_backup: > - echo "Finished a backup rsync." > on_error: > - echo "Error during create/prune/compact/check." > ``` > > the error: > > ``` > rsync: Error running actions for repository > [Errno 18] Cross-device link: '/root/.borgmatic/checks' -> '/root/.local/state/borgmatic/checks' > ``` borgmatic-collective/borgmatic has not been updated to 1.9.1 just yet. Please monitor [borgmatic docker releases](https://github.com/borgmatic-collective/docker-borgmatic/releases) for an update. Should hopefully be done in the next day or two. Edit: @xLogiiCx - doi - just realised I replied to you. I think I need more coffee...

😆 1

modem7 commented 2024-11-11 11:23:36 +00:00

Author

Copy Link

@witten - For feedback, I can confirm the 1.9.1 works as intended, thank you!

@witten - For feedback, I can confirm the 1.9.1 works as intended, thank you!

👍 1

qymab commented 2024-11-11 14:19:00 +00:00

Copy Link

I can confirm that it works now as well. Thank you!

I can confirm that it works now as well. Thank you!

👍 1

witten commented 2024-11-11 15:41:38 +00:00

Owner

Copy Link

Awesome, glad to hear it!

Awesome, glad to hear it!

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

No results found.

1.9.8

1.9.7

1.9.6

1.9.5

1.9.4

1.9.3

1.9.2

1.9.1

1.9.0

1.8.14

1.8.13

1.8.12

1.8.11

1.8.10

1.8.9

1.8.8

1.8.7

1.8.6

1.8.5

1.8.4

1.8.3

1.8.2

1.8.1

1.8.0

1.7.15

1.7.14

1.7.13

1.7.12

1.7.11

1.7.10

1.7.9

1.7.8

1.7.7

1.7.6

1.7.5

1.7.4

1.7.3

1.7.2

1.7.1

1.7.0

1.6.6

1.6.5

1.6.4

1.6.3

1.6.2

1.6.1

1.6.0

1.5.24

1.5.23

1.5.22

1.5.21

1.5.20

1.5.19

1.5.18

1.5.17

1.5.16

1.5.15

1.5.14

1.5.13

1.5.12

1.5.11

1.5.10

1.5.9

1.5.8

1.5.7

1.5.7.dev0

1.5.6

1.5.5

1.5.4

1.5.3

1.5.2

1.5.1

1.5.0

1.4.22

1.4.21

1.4.20

1.4.19

1.4.18

1.4.17

1.4.16

1.4.15

1.4.14

1.4.13

1.4.12

1.4.11

1.4.10

1.4.9

1.4.8

1.4.7

1.4.6

1.4.5

1.4.4

1.4.3

1.4.2

1.4.1

1.4.0

1.3.26

1.3.25

1.3.24

1.3.23

1.3.22

1.3.21

1.3.20

1.3.19

1.3.18

1.3.17

1.3.16

1.3.15

1.3.14

1.3.13

1.3.12

1.3.11

1.3.10

1.3.9

1.3.8

1.3.7

1.3.6

1.3.5

1.3.4

1.3.3

1.3.2

1.3.1

1.3.0

1.2.18

1.2.17

1.2.16

1.2.15

1.2.14

1.2.13

1.2.12

1.2.11

1.2.10

1.2.9

1.2.8

1.2.7

1.2.6

1.2.5

1.2.4

1.2.3

1.2.2

1.2.1

1.2.0

1.1.15

1.1.14

1.1.13

1.1.12

1.1.11

1.1.10

1.1.9

1.1.7

1.1.6

1.1.5

1.1.4

1.1.3

1.1.2

1.1.1

1.1.0

1.0.3

1.0.2

1.0.1

1.0.0

0.1.8

0.1.7

0.1.6

0.1.5

0.1.4

0.1.3

0.1.2

0.1.1

0.1.0

0.0.7

0.0.6

0.0.5

0.0.4

0.0.3

0.0.2

Labels

Clear labels

blocked

bug

data loss

design finalized

good first issue

new feature area

question / support

security

waiting for response

No Label

bug

Milestone

No items

No Milestone

Assignees

Clear assignees

No Assignees

4 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#931

No description provided.