mirror of
https://github.com/kevinveenbirkenbach/docker-volume-backup.git
synced 2026-10-20 09:45:37 +00:00
Kevin Veen-Birkenbach
07d819cb41
rsync -a expands to -rlptgoD, so the backup stored neither extended attributes nor ACLs nor hardlinks while the restore side asks for -aHAX. A generation therefore never held what a restore wants back, and rsync faithfully mirrored a snapshot that has none. Reproduced end to end against a source carrying user.oc.* attributes and a hardlink: with the old argv, getfattr -d -R over the generation returns nothing and the hardlink splits into two inodes; with -aHAX both sides come back identical to the source. That is the shape in which an OpenCloud volume survived a disaster-recovery drill with its files intact and its storage metadata gone, so its posix driver skipped every space it could no longer read. restore/files.py had the same gap on this repository's own restore path. Two consequences worth knowing. The first backup after this re-copies every attribute-carrying volume once, because rsync declines to hardlink against a generation whose xattrs do not match. And a backup destination on a filesystem without xattr support now fails the run instead of producing a generation that cannot be restored. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>