From: Skip Collins <bernard.collins@jhuapl.edu>
To: linux-kernel@vger.kernel.org
Subject: system hang and corrupt ext2 filesystem with test12-pre5
Date: Wed, 06 Dec 2000 09:48:16 -0500 [thread overview]
Message-ID: <3A2E51B0.76C65771@jhuapl.edu> (raw)
After running 2.4.0-test11 for a while, my system would occasionally
hang during heavy disk activity resulting in a corrupt ext2 filesystem.
Fortunately, none of the damage has been irrecoverable. I checked
linux-kernel to see if anyone else was seeing the same thing. The recent
threads on corruption seemed to be consistent with the behavior I saw:
ide disk access light remains lit, system hangs, fsck finds bad inodes.
I think test12-pre5 was supposed to fix the problem. But after upgrading
my kernel, I can still get the errors.
I have a 900MHz Athlon/Asus A7V mobo system with an onboard ata100
promise controller. I have only had problems when my ata100/udma5
harddrive is connected to the promise controller. Using the ATA66 ide
bus eliminates the problem. I typically see the corruption when copying
large (~1GB) files such as vmware virtual disks. It also happens
frequently inside vmware when doing heavy disk access things like
installing software or defragging a win2000 virtual disk.
For now I am going to fall back to the slower ide bus. But I wanted to
let people know that there still may be problems with ext2 corruption in
the latest test kernel.
sc
please cc any replies to me
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-06 15:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-06 14:48 Skip Collins [this message]
2000-12-06 15:35 ` Mohammad A. Haque
2000-12-06 15:47 ` Udo A. Steinberg
2000-12-06 16:31 ` Skip Collins
2000-12-06 19:40 ` Andre Hedrick
2000-12-06 20:00 ` Dan Hollis
2000-12-06 15:50 ` Tobias Ringstrom
2000-12-06 19:36 ` Andre Hedrick
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=3A2E51B0.76C65771@jhuapl.edu \
--to=bernard.collins@jhuapl.edu \
--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
all inboxes | Powered by JetHome®