From: Hartvig Ekner <hartvig@ekner.info>
To: Linux MIPS mailing list <linux-mips@linux-mips.org>
Subject: ext3 problem solved
Date: Fri, 11 Apr 2003 19:55:23 +0200 [thread overview]
Message-ID: <3E97018B.3435D14C@ekner.info> (raw)
I found out (sort of) what the problem was and found a fix.
Apparantly there is something wrong with e2fsprogs 1.27, since it was unable to repair
the problem I had in the filesystem (just kept repairing the same thing again and again).
I took the disk and attached it to a x86 PC, and ran fsck.ext3 there (an older version, 1.26).
It found exactly the same errors as the MIPS system, but actually fixed them so that
subsequent runs with "-f" reported no errors. I then put the disk back on the MIPS
system - voila, no more filesystem problems. Then did another unclean shutdown,
and the same problem reappeared, and once again fsck (on MIPS) was unable to fix
it.
Then I downloaded e2fsprogs-1.32-6.mipsel.rpm from redhat 9, and installed that on my
MIPS system. And that removed the problem for good.
So the conclusion must be: The e2fsprogs-1.27 package which is part of the MIPS 7.3
RedHat distribution (CDROM and FTP) is broken. Don't leave home without a newer
e2fsprogs RPM just in case!
Thanks to everybody who replied!
/Hartvig
reply other threads:[~2003-04-11 17:55 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=3E97018B.3435D14C@ekner.info \
--to=hartvig@ekner.info \
--cc=linux-mips@linux-mips.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