From the libarchive man page, it looks like the 'restricted' PAX format would remove the 8 GB limit and avoid the extended keyword at the same time (if possible). Though looking at the source, files larger than 8 GB set the 'need_extension' flag and thus trigger the extended attributes even with the restricted PAX format. Those warnings are benign, but I guess they would cause a lot of confusion for users, and a lot of work on answering the related questions for us.
However, since XtraBackup uses bundled libarchive, I'm going to fix this by modifying libarchive source to suppress those SCHILY.* attributes that GNU tar is unhappy with. GNU tar is a requirement for tar streams generated by XtraBackup anyway, so we can safely assume those attributes are never used.
Andrew,
Thank you for tracking down the problem.
From the libarchive man page, it looks like the 'restricted' PAX format would remove the 8 GB limit and avoid the extended keyword at the same time (if possible). Though looking at the source, files larger than 8 GB set the 'need_extension' flag and thus trigger the extended attributes even with the restricted PAX format. Those warnings are benign, but I guess they would cause a lot of confusion for users, and a lot of work on answering the related questions for us.
However, since XtraBackup uses bundled libarchive, I'm going to fix this by modifying libarchive source to suppress those SCHILY.* attributes that GNU tar is unhappy with. GNU tar is a requirement for tar streams generated by XtraBackup anyway, so we can safely assume those attributes are never used.
Thanks again for your help in verifying this bug.