All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Collins <bcollins@debian.org>
To: Andrew Morton <akpm@zip.com.au>, linux-kernel@vger.kernel.org
Subject: Re: Bug in ext3
Date: Thu, 15 Nov 2001 17:58:33 -0500	[thread overview]
Message-ID: <20011115175833.K329@visi.net> (raw)
In-Reply-To: <20011115092452.Z329@visi.net> <3BF3F9ED.17D55B35@zip.com.au>, <3BF3F9ED.17D55B35@zip.com.au> <20011115153442.A329@visi.net> <3BF42A1A.5AE96A78@zip.com.au> <20011115160232.H329@visi.net> <20011115145803.R5739@lynx.no> <20011115170628.J329@visi.net> <20011115144904.C23386@mikef-linux.matchmail.com>
In-Reply-To: <20011115144904.C23386@mikef-linux.matchmail.com>

On Thu, Nov 15, 2001 at 02:49:04PM -0800, Mike Fedyk wrote:
> > > 
> > > Please run e2fsck (1.25) to clear this up.  It may be that you have other
> > > corruption in your filesystem.  If you are sure you _never_ tried ext3
> > > on this filesystem before, yet the has_journal bit is set, this could
> > > be an indication of memory or cable problems.
> > 
> > Uh, something corrupted it. Believe me, there is no other corruption.
> > I've reverted to a non-ext3 kernel, and after a day of serious IO, no
> > problems have shown. So something is wrong, and it isn't my filesystem
> > (the erroneous flag needs to be cleared, yes, but the fact remains that
> > there is a problem in this case).
> 
> Yes, true.
> 
> Can you try again with a journal in this FS with ext3?

Can't really do that. This is a production system. I will however try to
reproduce it on another system. If I can do that, I'll try your
suggestion.


Ben

-- 
 .----------=======-=-======-=========-----------=====------------=-=-----.
/                   Ben Collins    --    Debian GNU/Linux                  \
`  bcollins@debian.org  --  bcollins@openldap.org  --  bcollins@linux.com  '
 `---=========------=======-------------=-=-----=-===-======-------=--=---'

  reply	other threads:[~2001-11-15 22:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-15 14:24 Bug in ext3 Ben Collins
2001-11-15 17:22 ` Andrew Morton
2001-11-15 20:34   ` Ben Collins
2001-11-15 20:48     ` Andrew Morton
2001-11-15 21:02       ` Ben Collins
2001-11-15 21:10         ` Andrew Morton
2001-11-15 22:04           ` Ben Collins
2001-11-15 21:58         ` Andreas Dilger
2001-11-15 22:06           ` Ben Collins
2001-11-15 22:49             ` Mike Fedyk
2001-11-15 22:58               ` Ben Collins [this message]
2001-11-15 23:21             ` Andreas Dilger
2001-11-15 23:38               ` Ben Collins
2001-11-16  0:07                 ` Andreas Dilger
2001-11-16  0:55                   ` Ben Collins
2001-11-16  3:09                     ` Andreas Dilger
2001-11-16  3:20                       ` Ben Collins
2001-11-16  3:37                         ` Mike Fedyk
2001-11-16  4:50                         ` Andreas Dilger
2001-11-16 18:38               ` Stephen C. Tweedie
2001-11-16 18:44                 ` Stephen C. Tweedie
2001-11-16 14:52         ` Stephen C. Tweedie

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=20011115175833.K329@visi.net \
    --to=bcollins@debian.org \
    --cc=akpm@zip.com.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.