https://bugzilla.novell.com/show_bug.cgi?id=650640 https://bugzilla.novell.com/show_bug.cgi?id=650640#c0 Summary: tar segfaults with using --listed-incremental Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: Curt.Blank@curtronics.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.10) Gecko/20100914 SUSE/3.6.10-0.3.1 Firefox/3.6.10 openSuSE 11.3 Kernel 2.6.34.7-0.5-default tar 1.23 Filesystem ext4 Not sure if Kernel is the right Component for this but I am seeing a kernel error in messages so I thought I'd start there. When I run tar -vv -cRf test.tar --listed-incremental=root.db --one-file-system -b 256 --totals / > test.log and root.db does not exist tar completes successfully. If root.db exists from a previous run tar segfaults and I see this in messages: Nov 2 03:34:48 router kernel: [21938.384366] tar[29989]: segfault at 0 ip 000000000042e390 sp 00007fffc30ad078 error 4 in tar[400000+58000] This is 100% repeatable whether I output to a file or a SCSI tape drive, delete root.db it runs fine, if root.db exists from a previous run it segfaults. If I backup /opt or any other ext4 filesystem thus mount point I do not have this problem, seems to only occur when attempting to do an incremental backup of / (root). This just started occurring with openSuSE 11.3 install done two days ago worked fine up to then on 11.2, 11.1, 11.0, 10.x etc. Reproducible: Always Steps to Reproduce: 1. Run tar 2. Run tar 3. Run tar Actual Results: See Details Expected Results: Um, for it to work and not segfault... I consider this Critical because it is preventing me from backing up the root partition incrementally, the alternative, doing a full every day uses a lot of tape. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.