All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Florian Lohoff <flo@rfc822.org>
Cc: Andrew Morton <akpm@zip.com.au>,
	"ext3-users@redhat.com" <ext3-users@redhat.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: ext3-0.9.16 against linux-2.4.17-pre2
Date: Wed, 5 Dec 2001 04:36:18 -0800	[thread overview]
Message-ID: <20011205123618.GA8966@mikef-linux.matchmail.com> (raw)
In-Reply-To: <3C0B12C5.F8F05016@zip.com.au> <20011205133204.C4916@paradigm.rfc822.org>
In-Reply-To: <20011205133204.C4916@paradigm.rfc822.org>

On Wed, Dec 05, 2001 at 01:32:04PM +0100, Florian Lohoff wrote:
> On Sun, Dec 02, 2001 at 09:51:01PM -0800, Andrew Morton wrote:
> > 
> > An ext3 update which also applies to linux-2.4.16 is available at
> > 
> 
> It seems something broken between 2.4.15-pre2 and this update - I am
> seeing filesystem corruption:
>

Hmm, that's strange.

> I am backing out the 2417 changes now - I already did a forced fsck
> which (e2fs 1.25) which didnt find anything abnormal.
> 
> (flo@ping)~# uname -a
> Linux ping.mediaways.net 2.4.16 #1 Tue Dec 4 19:42:30 CET 2001 i686 unknown
> 

Did you apply it against 2.4.16?  It was meant for 2.4.17-pre2.  Andrew, do
you know if that could be the cause of this problem?

Mike


  reply	other threads:[~2001-12-05 12:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-03  5:51 ext3-0.9.16 against linux-2.4.17-pre2 Andrew Morton
2001-12-05 12:32 ` Florian Lohoff
2001-12-05 12:36   ` Mike Fedyk [this message]
2001-12-05 12:37   ` Florian Lohoff
2001-12-05 23:42 ` Robert Love
2001-12-06  8:30   ` 2.4.17-pre2+ext3-0.9.16+anton's cache aligned smp Yusuf Goolamabbas
2001-12-06  8:39     ` Jens Axboe
2001-12-06  8:45     ` Andrew Morton
2001-12-06 13:02       ` Anton Blanchard
2001-12-07 15:27       ` Daniel Phillips

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=20011205123618.GA8966@mikef-linux.matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=akpm@zip.com.au \
    --cc=ext3-users@redhat.com \
    --cc=flo@rfc822.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 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.