From: "Garst R. Reese" <reese@isn.net>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: e2fsck-1.25 problem
Date: Thu, 22 Nov 2001 22:57:25 -0400 [thread overview]
Message-ID: <3BFDBB15.AD778DA4@isn.net> (raw)
Sorry if I'm OT here, but reading the docs on ext3fs I had to upgrade
from e2fsck-1.19 so I got the latest, 1.25 and installed it before
booting 2.4.15pre6.
make check said all was fine. But, when I rebooted some messages sailed
by about not being able to load shared libraries and libgcc_s.so.1 and
fsck said something about errors in the fs and REBOOT NOW. Very scary
always.
I booted up a recovery disk and ran e2fsck-1.10 on both of the relevant
devices and with -f and all was well. I rebooted back to 2.4.14 and got
the same messages flying by. Nothing of the sort in dmesg or the logs.
Can anybody give me a clue as to what is going on? The system goes ahead
and reboots and runs fine with either kernel AFAIK.
gcc-3.0.2
cc reese@isn.net
Thanks a bunch, Garst
next reply other threads:[~2001-11-23 2:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-23 2:57 Garst R. Reese [this message]
2001-11-23 4:18 ` e2fsck-1.25 problem Andreas Dilger
2001-11-23 8:32 ` Garst R. Reese
2001-11-23 23:30 ` Mike Castle
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=3BFDBB15.AD778DA4@isn.net \
--to=reese@isn.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