From: "Mike Black" <mblack@csihq.com>
To: "linux-kernel@vger.kernel.or" <linux-kernel@vger.kernel.org>
Subject: 2..4.5-pre5 bad fsck
Date: Thu, 24 May 2001 09:01:25 -0400 [thread overview]
Message-ID: <030d01c0e451$a3680100$e1de11cc@csihq.com> (raw)
2.4.2 works fine.
2.4.5-pre5 won't get past fsck of /dev/md0 -- locks up towards the end. I'm
running the same kernel on two other machine (different motherboards though)
I'm using gcc-3.0 and glibc-2.2.3
/dev/md0 is a dual-IDE RAID1 (2nd drive is currently disabled)
md0 : active raid1 hda1[0]
39082560 blocks [2/1] [U_]
Under 2.4.2 boot fsck ends
/dev/md0 was not cleanly unmounted, check forced.
/dev/md0: x/x files (x% non-contiguous), x/x blocks
But under 2.4.5-pre5 it doesn't get past the first "check forced" message.
It just locks up completely after it runs for a couple of minutes.
Motherboard is SuperMicro 370dl3
Disk WDC WD400BB-00AUA1
PCI Info:
00:00.0 Host bridge: Relience Computer CNB20HE (rev 05)
00:00.1 Host bridge: Relience Computer CNB20HE (rev 05)
00:0f.1 IDE interface: Relience Computer: Unknown device 0211
________________________________________
Michael D. Black Principal Engineer
mblack@csihq.com 321-676-2923,x203
http://www.csihq.com Computer Science Innovations
http://www.csihq.com/~mike My home page
FAX 321-676-2355
reply other threads:[~2001-05-24 13:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='030d01c0e451$a3680100$e1de11cc@csihq.com' \
--to=mblack@csihq.com \
--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