Bug 113411 - commands segfault ;filesystem corrupted even after fsck
commands segfault ;filesystem corrupted even after fsck
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
noarch Linux
high Severity high
: ---
: ---
Assigned To: Dave Jones
Depends On:
  Show dependency treegraph
Reported: 2004-01-13 12:44 EST by Prashant Jaikumar
Modified: 2015-01-04 17:04 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-29 15:57:38 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Prashant Jaikumar 2004-01-13 12:44:52 EST
Description of problem:
Many commands suddenly segfault.On rebooting  cannot mount
proc(probably because mount is segfaulting) and put  into a filesystem
repair shell.But even after fsck it says corrupt filesystem .busybox
could mount proc from repair shell.This happened thrice on an athlon
xp and also on two PIIIs.Once it gave error loading shared libraries
memtest didnt report any errors.Works fine for some time after
Other distributions(Mandrake,Mepis)dont seem to have this problem. 

Version-Release number of selected component (if applicable):
kernel 2.4.22-1.2115.nptl

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 1 Dave Jones 2004-01-13 13:36:36 EST
Still a problem with the latest errata kernel ?
Comment 2 Prashant Jaikumar 2004-02-29 01:40:25 EST
same problem on 2174 kernel also. all of a sudden commands started
segfaulting, error loading shared libraries. 
Comment 3 David Lawrence 2004-09-29 15:57:38 EDT
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/

Note You need to log in before you can comment on or make changes to this bug.