When databases are configured, don't auto-enable the "one_file_system" option #918
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What I'd like to do and why
Currently, when databases are configured in borgmatic, that auto-enables both the "read_special" option and the "one_file_system" option. The "read_special" option is to support database dump streaming, and the "one_file_system" option is reduce the chance of Borg finding a special file and hanging on it given that "read_special" is enabled.
However, since that arrangement was initially made, borgmatic gained a feature that detects individual special files and auto-excludes them from the set of source files handed to Borg, thereby hopefully sidestepping the hang issue. For that reason, auto-enabling "one_file_system" may no longer be necessary, and in fact can cause problems of its own when auto-enabled.
So as part of this ticket, look into making the database code path no longer auto-enable "one_file_system". Test this on real-world scenarios to ensure that the auto-excluding feature is sufficient.
Other notes / implementation ideas
No response
Implemented in main and will be part of the next release! Feedback welcome.
Released in borgmatic 1.9.0!