On Sat, Feb 02, 2013 at 03:29:19AM +1100, Dmitry Smirnov wrote: > Dear Andreas, > > Thank you for explanation. > > Translation of attributes make sense.
Don't know if it's at all possible, but could make sense if so... > > Warnings are only meaningful if it is theoretically possible to restore > metadata. Otherwise it's a noise. :) But it is practically possible to restore the metadata... just extract to a filesystem that supports the metadata. > > Perhaps it's make sense to print exactly one warning in the beginning of > extraction if attributes can't be restored. Flooding isn't nice, but with only one warning you wouldn't know which files lost metadata during extraction. > > Millions of warnings per file are hardly useful. > Besides GNU tar restore archive to btrfs without any warnings. You can use the gnu tar format in libarchive as well. (See the bug report I mentioned in previous mail). That way you'll not store any additional metadata, so you won't get any warnings about not being able to restore it on extraction. > > I think "Failed to set flags" warning is highly confusing. (what flags?). Could be more detailed, sure... > Without deep knowledge of file systems' internals it is hard to understand if > extraction is succeeded or if something goes wrong. > If there were any other warnings they are hard to notice due to amount of > "Failed to set flags" in the output. > > I don't expect folders in /home to have any unusual attributes (i.e. all of > them are alike) and "user_xattr" mount option is not used (and probably never > was). From what I can see ownership, time and access flags are successfully > restored so I wonder what exactly was dropped? Can we also notify user about > the nature of metadata that can't be restored (if any)? ownership, time and access are not filesystem specific information which all (sane) filesystems support. The problem are with "extended attributes" and other filesystem specific features. I don't really see how to handle this "bug" in debian. I agree that there are places where libarchive can be enhanced. I recommend you file enhancement requests in the upstream bug tracker, if you think that you have something which isn't already covered by the bug (mentioned in previous mail) that was forwarded upstream. -- Andreas Henriksson -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
