From: Andrew Morton <akpm@zip.com.au>
To: Eric <eric-linuxkernel@dragonglen.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.17 oops - ext2/ext3 fs corruption (?)
Date: Sat, 05 Jan 2002 11:58:01 -0800 [thread overview]
Message-ID: <3C375AC9.52462540@zip.com.au> (raw)
In-Reply-To: <Pine.LNX.4.33.0201051005190.5754-400000@fire.dragonglen.invalid>
Eric wrote:
>
> I seem to be having a reoccurring problem with my Red Hat 7.2 system
> running kernel 2.4.17. Four times now, I have seen the kernel generate an
> oops. After the oops, I find that one of file systems is no longer sane.
> The effect that I see is a Segmentation Fault when things like ls or du
> some directory (the directory is never the same). Also, when the system
> is going down for a reboot, it is unable to umount the file system. The
> umount command returns a "bad lseek" error.
>
> The first time this happened, it resulted in catastrophic corruption of
> /usr and I had to reinstall. At this time, /usr was an ext2 file system.
> When I reinstalled, I took the opportunity to reformat all the file
> systems, except /home, as ext3.
>
Everything here points at failing hardware. Probably memory errors.
People say that memtest86 is good at detecting these things. Another
way to verify this is to move the same setup onto a different computer...
-
next prev parent reply other threads:[~2002-01-05 20:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-05 18:45 2.4.17 oops - ext2/ext3 fs corruption (?) Eric
2002-01-05 19:58 ` Andrew Morton [this message]
2002-01-05 23:31 ` Eric
2002-01-06 10:15 ` Daniel Phillips
2002-01-12 14:25 ` Eric
2002-01-12 14:52 ` Marco Casaroli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C375AC9.52462540@zip.com.au \
--to=akpm@zip.com.au \
--cc=eric-linuxkernel@dragonglen.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox