From: Frédéric L. W. Meunier <0@pervalidus.net>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.2 ext2 filesystem corruption ? (was 2.4.2: What happened ? (No such file or directory))
Date: Mon, 5 Mar 2001 03:37:35 -0300 [thread overview]
Message-ID: <20010305033735.D103@pervalidus> (raw)
Maybe I should give details about my hardware. The system was
installed 5 months ago, and this is the first problem.
I used 2.2.16 stock Kernel from Slackware 7.1
2.2.17
2.2.18
2.4.0
2.4.1
And the only problem was with 2.4.2.
FYI, I'm not using hdparm or changing the BIOS to use UDMA 66.
It'd fail with 2.4.1 and 2.4.2 (CRC errors), so the setting
is AUTO and it's using UDMA 33.
And please note that this machine is fine, but I actually only
open 2 consoles and run GNU screen. No XFree86, and only a few
applications running.
If needed, my /var/log/dmesg is at
http://members.nbci.com/pervalidus/dmesg-2.4.2.txt
--
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
next reply other threads:[~2001-03-06 6:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-05 6:37 Frédéric L. W. Meunier [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-05 5:21 2.4.2 ext2 filesystem corruption ? (was 2.4.2: What happened ? (No such file or directory)) Frédéric L. W. Meunier
2001-03-06 6:49 ` Ben Greear
2001-03-06 10:14 ` SteveC
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=20010305033735.D103@pervalidus \
--to=0@pervalidus.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