On 03/22/2016 11:26 AM, Nicholas Cheng wrote: > # Creating a new test backup The backup went well, there was no > output indicating an I/O error with the --verbose flag on. > > # Mounted the newly created test backup I simply created a folder in > my home directory named 'test' and mounted the backup. All the files > in the backup were readable and didn't seem to indicate any > problems.
Hi Nicholas, this is good news. Your backup isn't broken, it's just a matter of the extraction process. > # Attempted to extract the test backup I encountered the same errors > as before, please refer to the attached text file named 'extracting' > to look at the output and commands I used. The traceback suggests that the problem occurs during setxattr(). This would suggest that the files by themselves are complete, please check that to be sure. > After submitting the bug report, I did some additional testing by > installing Attic, I encountered the same issue with extracting > backups. This might indicate a problem with your file system creation and/or mount options. You should check if getfattr/setfattr support works when calling interactively: getfattr -d ~/test/somefile setfattr -n user.somecoolname -v somevalue ~/test/somefile You should normally be able to set anything in the "user.*" namespace. If the files in your ~/Downloads folder additionally have values outside of the namespace, that would explain why attic/borg cannot restore them. AFAIK writing anything outside the user namespace needs root permission. (In this case, please check why they have the attributes in the first place, and check if restoring with sudo gives the desired result.) On my ext4 /home file system, I can set user.* attributes and restore them with borg correctly. What file system are you using for /home? Cheers, - Danny
signature.asc
Description: OpenPGP digital signature
