From: "Stephen C. Tweedie" <sct@redhat.com>
To: Christopher Li <chrisl@vmware.com>
Cc: "'Jens Axboe '" <axboe@suse.de>,
"'Linux Kernel '" <linux-kernel@vger.kernel.org>,
"'ext2-devel@lists.sourceforge.net '"
<ext2-devel@lists.sourceforge.net>
Subject: Re: [Ext2-devel] Re: 2.5.46 ext3 errors
Date: Wed, 6 Nov 2002 10:18:06 +0000 [thread overview]
Message-ID: <20021106101806.B2663@redhat.com> (raw)
In-Reply-To: <3C77B405ABE6D611A93A00065B3FFBBA36A493@PA-EXCH2>; from chrisl@vmware.com on Wed, Nov 06, 2002 at 01:43:45AM -0800
Hi,
On Wed, Nov 06, 2002 at 01:43:45AM -0800, Christopher Li wrote:
> Can you put the e2image of that device to some URL I can
> download?
It's unlikely to be useful. A journal abort will cause existing
transactions to be suspended midstream, so any errors afterwards may
be due to updates which were in progress at the time and which didn't
complete. And since a fsck has been done, we've lost those errors
anyway.
Is the problem reproducible? The basic
> EXT3-fs error (device ide1(22,1)): ext3_new_inode: Free inodes count
> corrupted in group 688 Aborting journal on device ide1(22,1).
error is just ext3's normal reaction to a fatal error detected in the
filesystem, so that in itself isn't a worry. The cause of the problem
it spotted is the worry; is this reproducible?
Cheers,
Stephen
next parent reply other threads:[~2002-11-06 10:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C77B405ABE6D611A93A00065B3FFBBA36A493@PA-EXCH2>
2002-11-06 10:18 ` Stephen C. Tweedie [this message]
2002-11-06 13:05 ` [Ext2-devel] Re: 2.5.46 ext3 errors Jens Axboe
2002-11-06 16:12 ` Ewan Mac Mahon
2002-11-06 17:08 ` Jens Axboe
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=20021106101806.B2663@redhat.com \
--to=sct@redhat.com \
--cc=axboe@suse.de \
--cc=chrisl@vmware.com \
--cc=ext2-devel@lists.sourceforge.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