TW
https://github.com/python/cpython/blob/3.13/Lib/tarfile.py#L87 It doesn't look like tarinfo type "E" being supported even by `tarfile` stdlib module. But a week ago (after b12) I added code to support extended attributes in PAX...
Maybe try if you can create PAX tar archives (POSIX.1-2001 (pax) format) - that seems to be standard, while I suspect that "E" header is a solaris specific thing?
So, would you think it is better if borg silently ignored the `E` type tarinfos?
I don't know much about that E type stuff, but currently it looks like a non-standard solaris tar specific thing, guess I rather would not implement that considering that there...
- DONE (docs improved): check if docs need to be more clear - TODO check if we can easily implement relative patterns
Yeah, the paths you give on the cmdline are the same as the recursion roots (R).
Docs fixed by #6242 and #6265.
At `create` time, borg outputs the paths starting with the recursion root. But if you look into the archive (`borg list`), you should see `app/...`. Guess the exclude behaviour needs...
I just check current master branch code and it also behaves like seen in https://github.com/borgbackup/borg/issues/6231#issuecomment-1649875219 . Also, 1.2-maint current code behaves the same.
If you mean "archives in one repository" when saying snapshots, you should reduce that count to get better speed. Some operations are O(archive count), thus 15000 will make it 100x...