+++ This bug was initially created as a clone of Bug #652939 +++
Description of problem:
When creating an archive using the --listed-incremental option to tar, tar will segfault (return code 139). This only happens when archiving the root partition (/) and only on the second and subsequent invocations. (The first invocation creates the list file, the second should read the list file and archive only the delta changes).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. tar --create --one-file-system --listed-incremental=root.list --file=root.full.tar /
2. tar --create --one-file-system --listed-incremental=root.list --file=root.delta.tar /
3. echo $?
segfault errcode 139
delta archive into root.delta.tar
There is a patch for this floating around upstream. See:
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
identical problem on fedora 14 running this command line
# rm -f /tmp/backup-inc.tgz /tmp/snapshot.snar ; find /bin -not -type s -print | tar cvTf - /tmp/backup-inc.tgz --no-recursion -z --listed-incremental=/tmp/snapshot.snar
no probleme on fedora 11 and centos 5
Identical problem on debian
Looks to be solved on tar-1.25
Tried on tar-1.26. It works.
Yep, I know the problem exists on Fedora 14, it was not serious enough for me to do an update for tar there. I'll check if there are more such "smaller" things and maybe do an update, f15 should be ok anyway, as there is already upstream version with fix.
Ignore my previous comment, I realized that I fixed the problem in F14 already - see https://admin.fedoraproject.org/updates/tar-1.23-7.fc14 . So just make sure you have fully updated f14 and everything should be ok ... If not, feel free to report f14 bugzilla, this one is tracking RHEL-6 status.
(In reply to comment #5)
> Ignore my previous comment, I realized that I fixed the problem in F14 already
> - see https://admin.fedoraproject.org/updates/tar-1.23-7.fc14 . So just make
> sure you have fully updated f14 and everything should be ok ... If not, feel
> free to report f14 bugzilla, this one is tracking RHEL-6 status.
My test case (see below) is not fixed on my up2date F14 :-(.
I have no RHEL-6 for testing. could you make a try ?
I will open a bug for F14.
thanks for your time.
[root@box172 tmp]# rpm -qi
rpm: no arguments given for query
[root@box172 tmp]# rpm -qi tar
Name : tar Relocations: (not relocatable)
Version : 1.23 Vendor: Fedora Project
Release : 7.fc14 Build Date: Mon 15 Nov 2010
[root@box172 tmp]# rm -f /tmp/backup-inc.tgz /tmp/snapshot.snar ; find /bin -not -type s -print | tar cvTf - /tmp/backup-inc.tgz --no-recursion -z --listed-incremental=/tmp/snapshot.snar
tar: /bin: Directory is new
Yep, your test fails on RHEL-6, so the f-14 fix has to be extended, thanks for another test, I'll check the f14 binary and make tar update after fix.
This one commit fixes your part of crash - but is completely separate from the previous one - http://git.savannah.gnu.org/gitweb/?p=tar.git;a=commit;h=40dea1ae7fc892a54eae2efd30ddd8559c697525
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.