[Bug 407067] New: bzip2 crash: SIGSEGV or SIGBUS
https://bugzilla.novell.com/show_bug.cgi?id=407067 Summary: bzip2 crash: SIGSEGV or SIGBUS Product: openSUSE 11.0 Version: Final Platform: i686 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: rhg@marxmeier.com QAContact: qa@suse.de Found By: Third Party Developer/Partner Did a tar --create --bzip2 of a huge directory when bzip2 failed with the message below: bzip2: Caught a SIGSEGV or SIGBUS whilst compressing. Possible causes are (most likely first): (1) This computer has unreliable memory or cache hardware (a surprisingly common problem; try a different machine.) (2) A bug in the compiler used to create this executable (unlikely, if you didn't compile bzip2 yourself.) (3) A real bug in bzip2 -- I hope this should never be the case. The user's manual, Section 4.3, has more info on (1) and (2). If you suspect this is a bug in bzip2, or are unsure about (1) or (2), feel free to report it to me at: jseward@bzip.org. Section 4.3 of the user's manual describes the info a useful bug report should have. If the manual is available on your system, please try and read it before mailing me. If you don't have the manual or can't be bothered to read it, mail me anyway. Input file = (stdin), output file = (stdout) After that, I ran memtest86 over the weekend while the sun heated the office, but after 72 hours memtest86 still reported zero errors. Therefore I feel safe to exclude cause (1) mentioned in the error message. After the error above, the size of the resulting tar archive was 5 GB and could be unpacked up to the point where the error occurred (with bzip2 then reporting a consistency error of course). -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=407067
User meissner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=407067#c1
Marcus Meissner
https://bugzilla.novell.com/show_bug.cgi?id=407067
User rhg@marxmeier.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=407067#c2
Roland Genske
https://bugzilla.novell.com/show_bug.cgi?id=407067
User chrubis@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=407067#c3
Cyril Hrubis
https://bugzilla.novell.com/show_bug.cgi?id=407067
User lmichnovic@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=407067#c4
Ladislav Michnovič
https://bugzilla.novell.com/show_bug.cgi?id=407067
User rhg@marxmeier.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=407067#c5
--- Comment #5 from Roland Genske
Roland, have you examined the health status of your disk ?
Yes, both the internal source disk and the external USB destination disk appear healthy. I have smartd running on the internal source disk, no problems reported. Regarding the USB disk I did not find any problem reports yes, neither in the syslog nor on the system console (problem happened last on 4th July, system is up since then).
No IO errors in logs?
No, the logs are clean. This is the relevant excerpt from the log created by my backup script: Backup start ... Fri Jul 4 03:14:01 CEST 2008 Backing-up files ... tar: Removing leading `/' from member names tar: Removing leading `/' from hard link targets .. tar: /dev/log: socket ignored bzip2: Caught a SIGSEGV or SIGBUS whilst compressing. Possible causes are (most likely first): (1) This computer has unreliable memory or cache hardware (a surprisingly common problem; try a different machine.) (2) A bug in the compiler used to create this executable (unlikely, if you didn't compile bzip2 yourself.) (3) A real bug in bzip2 -- I hope this should never be the case. The user's manual, Section 4.3, has more info on (1) and (2). If you suspect this is a bug in bzip2, or are unsure about (1) or (2), feel free to report it to me at: jseward@bzip.org. Section 4.3 of the user's manual describes the info a useful bug report should have. If the manual is available on your system, please try and read it before mailing me. If you don't have the manual or can't be bothered to read it, mail me anyway. Input file = (stdin), output file = (stdout) Backup failed: Fri Jul 4 05:31:14 CEST 2008 And this is the syslog from the same time: Jul 4 03:14:01 rhg-lx /usr/sbin/cron[29090]: (root) CMD ( /root/bin/backup.sh) Jul 4 04:00:05 rhg-lx syslog-ng[25113]: STATS: dropped 0 Jul 4 05:00:05 rhg-lx syslog-ng[25113]: STATS: dropped 0 Jul 4 06:00:05 rhg-lx syslog-ng[25113]: STATS: dropped 0 Problem happened twice in a row but then unfortunately did not happen again :-( -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=407067
User lmichnovic@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=407067#c6
--- Comment #6 from Ladislav Michnovič
https://bugzilla.novell.com/show_bug.cgi?id=407067
User lmichnovic@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=407067#c7
Ladislav Michnovič
participants (1)
-
bugzilla_noreply@novell.com