Closed lfam closed 1 week ago
The problem is that all was going well (no "file or directory not found") until borg tried to read the repo config contents, which failed with an IOError.
IOError can be anything going wrong in the filesystem or on the storage media, so borg can't differentiate between the "repo not being mounted any more" and e.g. a disk read error.
That makes sense. I still think it would be nice to not crash here, from the user's perspective.
Well, there isn't much we can do there:
Understood, thanks
Have you checked borgbackup docs, FAQ, and open GitHub issues?
Yes
Is this a BUG / ISSUE report or a QUESTION?
Bug / feature request
System information. For client/server mode post info for both machines.
Your borg version (borg -V).
Client: 1.4.0rc1 from Guix Server: 1.4.0rc1 from Guix
Operating system (distribution) and version.
Client: Debian Bookworm with Linux 5.15.160 Server: Debian Bookwork with Debian kernel 6.1.0-20-amd64
Hardware / network configuration, and filesystems used.
Client: Thinkpad x260, btrfs Server: PCEngines APU2, btrfs
How much data is handled by borg?
A few hundred gigabytes
Full borg commandline that lead to the problem (leave away excludes and passwords)
Describe the problem you're observing.
I didn't realize that the disk that contains the repository had become unmounted, and
borg create
was crashing, so I tried clearing any locks after checking that Borg was not running. It would be great if the client could be told that the repository could not be found, rather than crashing.