|
From: | Arjun Krishnan |
Subject: | Re: [Duplicity-talk] Following up on an extended attributes question |
Date: | Mon, 29 May 2017 12:07:58 -0600 |
Currently we use the GNU_FORMAT, which is the default format, so there is no pax_header in that format. For sake of backwards compatibility, we'd need to be able to read GNU_FORMAT, and the PAX_FORMAT would need to be readable by GNU tar for manual recovery of a corrupted backup. Perhaps it's time to change formats? I don't know all the tradeoffs we'll need to make and what the complexity would be.
Since pax_headers are key/value pairs, we need to track their size and be prepared for a value that may exceed our max block size. I've read of cases where key/value pairs exceed the size of the file itself, performing the functional equivalent of a dictionary file. We would have to allow for cases where a large value crosses a volume boundary.
[Prev in Thread] | Current Thread | [Next in Thread] |