TW
Hmm, can you try if that works for you?: ``` borg list REPO::ARCHIVE 'sh:*/*/*' # pattern corresponding to depth wanted ```
Guess creating a full list with borg and then filtering it through `grep` and having grep filter out anything with more than N slashes could work.
I closed #1820 (without merging it) for now as it was not making progress. I guess next try should be more incremental, step-by-step, so it can get merged more quickly.
Maybe NTFS with kernel 5.15 (e.g. on Ubuntu Jammy) would be a good start: - it is local, kernel driver - not network / server side setup - still somewhat...
Considering that we test on quite some different platforms (github CI and/or vagrant) which use different filesystems, this is already solved.
I suspect your patterns don't match like you think they do. See the patterns help page and use these commands to see what's excluded and what not: - borg list...
Just wanted to note that using `!` instead of `-` is: - advisable for dirs like /proc and /sys on Linux where no includes below the excluded dir are expected...
Just to keep a vague idea: If the different layers in borg would communicate a bit more (like the compression method being flexibly given by upper layers and the decompression...
Advanced sparse file support would also save some time for archive creation as it does not have to read all these zeros in the sparse wholes (simple sparse file support...
@milkey-mouse bs just told me you have started on this. maybe first evaluate how much changes this needs - if it is a bigger change, it might be not applicable...