From: David Ford <david@blue-labs.org>
To: linux-kernel@vger.kernel.org
Subject: Re: ext2 problems in 2.4
Date: Thu, 09 Aug 2001 13:40:05 -0400 [thread overview]
Message-ID: <3B72CAF5.8010101@blue-labs.org> (raw)
Ok, the problem appears to have been fixed. I venture the bug is likely
in the e2fs tools for the simple reason that on the last time I took the
machine down for maintenance, I ran e2fsck five times and got different
results for the first three runs. Now before everyone flys off the
handle with their favorite flamethrower, the server was in single user
mode with nothing else running but the kernel threads. There weren't
any processes left and lsof was also clean. I have also been forcing
fsck on boot every time.
The machine has been up for four days now without any errors and no
unaccounted for disk space.
David
next reply other threads:[~2001-08-09 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-09 17:40 David Ford [this message]
2001-08-15 21:11 ` ext2 problems in 2.4 Theodore Tso
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=3B72CAF5.8010101@blue-labs.org \
--to=david@blue-labs.org \
--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