Bug 54008

Summary: crash when un-archiving bz2 files
Product: [Retired] Red Hat Linux Reporter: Ian Beard <ian>
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED CURRENTRELEASE QA Contact: David Lawrence <dkl>
Severity: high Docs Contact:
Priority: high    
Version: 7.1kCC: bero, teg
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-11-28 10:46:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ian Beard 2001-09-25 13:40:57 UTC
Description of Problem:
download insight debugger, un-archive (right click) - BANG

Version-Release number of selected component (if applicable):
kde 2.1 explorer

How Reproducible:
un-archive bz2 file

Steps to Reproduce:
1. download bz2 file
2. right click in file manager
3. un-archive

Actual Results:
reduces linux to rubble - scrambles entire disk system

Expected Results:
un-archived files

Additional Information:
Seriously un-impresses

Comment 1 Trond Eivind Glomsrxd 2001-09-25 15:32:51 UTC
That would be a KDE problem, not a bzip2 problem.

Comment 2 Bernhard Rosenkraenzer 2001-11-27 16:41:29 UTC
I can't reproduce this.
What do you mean by "scrambles entire disk system"?
If it's filesystem corruption, chances are your kernel is doing something odd.


Comment 3 Ian Beard 2001-11-28 10:26:34 UTC
Basically, I had to re-install Red Hat. System would not re-boot. Seemed to me 
a file descriptor may have decided to go walkabout and went into the system 
file space. I did this twice, the second time by mistake. Debugging on Linux a 
big joke, so have decided to do my Unix work on Solaris anyway, so have no 
problem anymore. But thanks for letting me know someone was going to look into 
it, kinda unexpected.

Comment 4 Bernhard Rosenkraenzer 2001-11-28 10:45:38 UTC
This sounds like a kernel problem. Please give some details on your hardware 
and configuration, in particular:
IDE or SCSI controller type
Filesystem used