[Errno 20] Not a directory #1007

New issue

Closed

opened 2025-02-24 22:08:55 +00:00 by mrclschstr · 3 comments

mrclschstr commented 2025-02-24 22:08:55 +00:00

Copy link

What I'm trying to do and why

As I already mentioned in #1006, I am currently testing the update from borgmatic 1.8.X to 1.9.X. During the restore of files I noticed the following warnings:

hetzner: Extracting archive latest
borgmatic/bootstrap: open: [Errno 20] Not a directory: '/borgmatic/bootstrap'
borgmatic/bootstrap/manifest.json: makedirs: [Errno 20] Not a directory: '/borgmatic/bootstrap'
borgmatic/bootstrap: makedirs: [Errno 20] Not a directory: '/borgmatic/bootstrap'
borgmatic/mariadb_databases: makedirs: [Errno 20] Not a directory: '/borgmatic/mariadb_databases'
borgmatic/mariadb_databases/mariadb: makedirs: [Errno 20] Not a directory: '/borgmatic/mariadb_databases'
borgmatic/mariadb_databases/mariadb/nextcloud: makedirs: [Errno 20] Not a directory: '/borgmatic/mariadb_databases'
borgmatic/mariadb_databases/mariadb: makedirs: [Errno 20] Not a directory: '/borgmatic/mariadb_databases'
borgmatic/mariadb_databases: makedirs: [Errno 20] Not a directory: '/borgmatic/mariadb_databases'
Exception ignored in: <function RemoteRepository.__del__ at 0x7f83551bd260>
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/site-packages/borg/remote.py", line 637, in __del__
AttributeError: 'NoneType' object has no attribute 'debug'

summary:
Successfully ran configuration file

Restoring files still works without any recognizable problems.

Steps to reproduce

Just restore (extract) files from a backup:

docker compose exec -T borgmatic borgmatic extract --archive latest --verbosity 1

Actual behavior

The files are restored without any recognizable problems, but the error messages mentioned above appear in the log.

Expected behavior

The extract function is not affected.

Other notes / implementation ideas

No response

borgmatic version

1.9.12

borgmatic installation method

Container

Borg version

1.4.0

Python version

3.13.2

Database version (if applicable)

n/a

Operating system and version

Ubuntu 22.04.5 LTS

### What I'm trying to do and why As I already mentioned in #1006, I am currently testing the update from borgmatic 1.8.X to 1.9.X. During the restore of files I noticed the following warnings: ``` hetzner: Extracting archive latest borgmatic/bootstrap: open: [Errno 20] Not a directory: '/borgmatic/bootstrap' borgmatic/bootstrap/manifest.json: makedirs: [Errno 20] Not a directory: '/borgmatic/bootstrap' borgmatic/bootstrap: makedirs: [Errno 20] Not a directory: '/borgmatic/bootstrap' borgmatic/mariadb_databases: makedirs: [Errno 20] Not a directory: '/borgmatic/mariadb_databases' borgmatic/mariadb_databases/mariadb: makedirs: [Errno 20] Not a directory: '/borgmatic/mariadb_databases' borgmatic/mariadb_databases/mariadb/nextcloud: makedirs: [Errno 20] Not a directory: '/borgmatic/mariadb_databases' borgmatic/mariadb_databases/mariadb: makedirs: [Errno 20] Not a directory: '/borgmatic/mariadb_databases' borgmatic/mariadb_databases: makedirs: [Errno 20] Not a directory: '/borgmatic/mariadb_databases' Exception ignored in: <function RemoteRepository.__del__ at 0x7f83551bd260> Traceback (most recent call last): File "/usr/local/lib/python3.13/site-packages/borg/remote.py", line 637, in __del__ AttributeError: 'NoneType' object has no attribute 'debug' summary: Successfully ran configuration file ``` Restoring files still works without any recognizable problems. ### Steps to reproduce Just restore (extract) files from a backup: ``` docker compose exec -T borgmatic borgmatic extract --archive latest --verbosity 1 ``` ### Actual behavior The files are restored without any recognizable problems, but the error messages mentioned above appear in the log. ### Expected behavior The extract function is not affected. ### Other notes / implementation ideas _No response_ ### borgmatic version 1.9.12 ### borgmatic installation method Container ### Borg version 1.4.0 ### Python version 3.13.2 ### Database version (if applicable) n/a ### Operating system and version Ubuntu 22.04.5 LTS

witten commented 2025-02-25 05:29:10 +00:00

Owner

Copy link

The traceback itself is coming from Borg, and I'm not sure exactly what's causing it. If you can reproduce it without borgmatic, e.g. by manually running the extract command that borgmatic itself is running, then you might be able to file a ticket with the Borg project. You can see the extract command that borgmatic is running in the borgmatic output when run with --verbosity 2.

But I think I know what's causing the "Not a directory" messages, which I believe are also from Borg. The /borgmatic directory within an archive is where borgmatic stores database backups. You normally shouldn't need to extract them as long as borgmatic restore works for restoring your databases. But even if you do extract /borgmatic paths from an archive, /borgmatic should get created on your filesystem as a normal directory like any other from the archive (in the current directory by default).

The problem stems from the fact that you already have a file in the current directory named borgmatic, and therefore Borg can't create a directory there! That's why it's complaining that borgmatic is "Not a directory".

You have a few different options for working around this:

• Delete the borgmatic file before extracting.
• Or extract the archive to a different location (see --destination or just cd first).
• Or omit the borgmatic path when extracting (see --path).

The traceback itself is coming from Borg, and I'm not sure exactly what's causing it. If you can reproduce it without borgmatic, e.g. by manually running the `extract` command that borgmatic itself is running, then you might be able to file a ticket with the Borg project. You can see the `extract` command that borgmatic is running in the borgmatic output when run with `--verbosity 2`. But I think I know what's causing the "Not a directory" messages, which I believe are also from Borg. The `/borgmatic` directory within an archive is where borgmatic stores database backups. You normally shouldn't need to extract them as long as `borgmatic restore` works for restoring your databases. But even if you do extract `/borgmatic` paths from an archive, `/borgmatic` *should* get created on your filesystem as a normal directory like any other from the archive (in the current directory by default). The problem stems from the fact that you already have a file in the current directory named `borgmatic`, and therefore Borg can't create a directory there! That's why it's complaining that `borgmatic` is "Not a directory". You have a few different options for working around this: * Delete the `borgmatic` file before extracting. * Or extract the archive to a different location (see `--destination` or just `cd` first). * Or omit the `borgmatic` path when extracting (see `--path`).

witten added the

question / support

label 2025-02-25 05:29:22 +00:00

mrclschstr commented 2025-02-25 07:58:19 +00:00

Author

Copy link

Thank you for pointing me in the right direction. You are right that a file called /borgmatic exists in the container, which would also explain the error messages. I did some digging and I have a hunch that the bash completion setup is not working properly and is leaving a file named borgmatic in the root directory, see: github.com/borgmatic-collective/docker-borgmatic@17543f35ee/Dockerfile (L74)

I will leave an issue in the appropriate github repos. Thanks for the great help!

EDIT: For reference https://github.com/modem7/docker-borgmatic/issues/173

Thank you for pointing me in the right direction. You are right that a file called `/borgmatic` exists in the container, which would also explain the error messages. I did some digging and I have a hunch that the bash completion setup is not working properly and is leaving a file named `borgmatic` in the root directory, see: https://github.com/borgmatic-collective/docker-borgmatic/blob/17543f35eef6d59e77a15b079dba2add96c0066a/Dockerfile#L74 I will leave an issue in the appropriate github repos. Thanks for the great help! **EDIT:** For reference https://github.com/modem7/docker-borgmatic/issues/173

witten commented 2025-02-25 17:13:51 +00:00

Owner

Copy link

Ah, nice sleuthing! I'll close this ticket for now and follow along with the one you just filed.

Ah, nice sleuthing! I'll close this ticket for now and follow along with the one you just filed.

👍 1

witten closed this issue 2025-02-25 17:13:52 +00:00

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

parallel-borgmatic

command-hook-steps

2.1.7

2.1.6

2.1.5

2.1.4

2.1.3

2.1.2

2.1.1

2.1.0

2.0.13

2.0.12

2.0.11

2.0.10

2.0.9

2.0.8

2.0.7

2.0.6

2.0.5

2.0.4

2.0.3

2.0.2

2.0.1

2.0.0

1.9.14

1.9.13

1.9.12

1.9.11

1.9.10

1.9.9

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

  

breaking

  

bug

  

data loss

  

design finalized

  

good first issue

  

new feature area

  

question / support

  

security

  

waiting for response

No labels

blocked

breaking

bug

data loss

design finalized

good first issue

new feature area

question / support

security

waiting for response

Milestone

Clear milestone

No items

No milestone

Assignees

Clear assignees

No assignees

2 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

borgmatic-collective/borgmatic#1007

No description provided.