From: Theodore Tso <tytso@mit.edu>
To: David Ford <david@blue-labs.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext2 problems in 2.4
Date: Wed, 15 Aug 2001 17:11:40 -0400 [thread overview]
Message-ID: <20010815171140.A9017@thunk.org> (raw)
In-Reply-To: <3B72CAF5.8010101@blue-labs.org>
In-Reply-To: <3B72CAF5.8010101@blue-labs.org>; from david@blue-labs.org on Thu, Aug 09, 2001 at 01:40:05PM -0400
On Thu, Aug 09, 2001 at 01:40:05PM -0400, David Ford wrote:
> 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.
If you have a problem like this in the future, please download and
compile the latest e2fsprogs (1.23 WIP 9-Aug-2001), and use the
command "e2image -r /dev/xxx raw-image-file". This will create a raw
image file which is a sparse file containing only the filesystem
metadata. Try running fsck on that, and see if you are continuing to
get differing results between runs. If so, then you've isolated away
from it being a hardware problem. Then, if you don't mind letting me
see the directory names/hierarchy in your filesystem, bzip2 the
resulting filesystem and send it to me, along with an indication of
the size of the filesystem.
That will allow me to debug the problem at my end, without my needing
to see any of your file data, as well as making the compressed
filesystem image small enough that it should be feasible to ship it
over the net.
Many thanks,
- Ted
prev parent reply other threads:[~2001-08-15 21:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-09 17:40 ext2 problems in 2.4 David Ford
2001-08-15 21:11 ` Theodore Tso [this message]
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=20010815171140.A9017@thunk.org \
--to=tytso@mit.edu \
--cc=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