public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: CaT <cat@zip.com.au>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.47 / unusual ext3 fs errors
Date: Tue, 12 Nov 2002 10:32:45 +1100	[thread overview]
Message-ID: <20021111233245.GA616@zip.com.au> (raw)
In-Reply-To: <3DD03CDC.562D7C0@digeo.com>

On Mon, Nov 11, 2002 at 03:27:24PM -0800, Andrew Morton wrote:
> CaT wrote:
> > And again, on reboot into single user mode and a full fsck bad inode
> > count errors were present. There were no errors detected whilst testing
> > the disk with -c.
> 
> There was a problem in 2.5.46 which mucked up these counters.  On disk.
> 
> 2.5.47 fixed that bug, and now you have fixed the on-disk mess which 2.5.46
> created, all should be well.

Sweet. Thanks. :)

-- 
        All people are equal,
        But some are more equal then others.
            - George W. Bush Jr, President of the United States
              September 21, 2002 (Abridged version of security speech)

      reply	other threads:[~2002-11-11 23:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-11 23:10 2.5.47 / unusual ext3 fs errors CaT
2002-11-11 23:27 ` Andrew Morton
2002-11-11 23:32   ` CaT [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=20021111233245.GA616@zip.com.au \
    --to=cat@zip.com.au \
    --cc=akpm@digeo.com \
    --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