Hide Forgot
Description of problem: Upgrading from tar-1.23-7.el6.x86_64 to tar-1.23-11.el6.x86_64 introduced a problem with the -W verify switch. Problem seems to have started with tar-1.23-9.el6.x86_64 Version-Release number of selected component (if applicable): tar-1.23-7.el6.x86_64 How reproducible: every time Steps to Reproduce: 1. tar -cvWf mytarfile.tar * Actual results: file.txt: Mode differs file.txt: Gid differs file.txt: Mod time differs Expected results: Verify */file.txt Additional info: This is my first bug report. Hopefully I am providing enough information.
Created attachment 712790 [details] Example case of error
We tried to downgrade to tar-1.23-9.el6.x86_64 but the problem did not go away. When we downgraded to tar-1.23-7.el6.x86_64 it went back to normal behavior. Inspecting the tar file, the contents look correct.
Tested on two separate systems both running RHEL 6.4. Also tested on mounted and local file systems with the same results.
Hi Will, thanks for the report. This is really caused by the RH-tar commit a309347d41ac4 (longnames patch). Upstream fixed this later by: http://git.savannah.gnu.org/cgit/tar.git/commit/?id=24214ca5d506f56 There are some other patches fixing/enhancing -W option which should be observed in upstream but this should fix the major issue. Note that this bug tracking system is not a mechanism for requesting support, and we are not able to guarantee the timeliness or suitability of a resolution. If this issue is critical or in any way time sensitive, please raise a ticket through your regular Red Hat support channels to make certain it receives the proper attention and prioritization to assure a timely resolution. For information on how to contact the Red Hat production support team, please visit: https://www.redhat.com/support/process/production/#howto Pavel
*** Bug 963237 has been marked as a duplicate of this bug. ***
*** Bug 976553 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-1285.html