From: Andreas Dilger <adilger@turbolabs.com>
To: "Garst R. Reese" <reese@isn.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: e2fsck-1.25 problem
Date: Thu, 22 Nov 2001 21:18:27 -0700 [thread overview]
Message-ID: <20011122211827.T1308@lynx.no> (raw)
In-Reply-To: <3BFDBB15.AD778DA4@isn.net>
In-Reply-To: <3BFDBB15.AD778DA4@isn.net>; from reese@isn.net on Thu, Nov 22, 2001 at 10:57:25PM -0400
On Nov 22, 2001 22:57 -0400, Garst R. Reese wrote:
> 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 take it you did a normal ./configure; make; make install? I am running
1.25 without any problems.
> 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.
e2fsck wouldn't log anything in dmesg or in syslog. It would be helpful
to see what the exact messages are. Note also, that e2fsck 1.10 is
_very_ old (released 4.5 years ago), so it is entirely possible that
your fs has problems in it that it could not detect, but the newer e2fsck
does find.
I would suggest booting from a recovery disk with a statically linked
e2fsck 1.25, and then run it under "script" so you get a log of all
the output. Post it here.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2001-11-23 4:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-23 2:57 e2fsck-1.25 problem Garst R. Reese
2001-11-23 4:18 ` Andreas Dilger [this message]
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=20011122211827.T1308@lynx.no \
--to=adilger@turbolabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reese@isn.net \
/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