From: Andrew Morton <akpm@zip.com.au>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: Frank Krauss <fmfkrauss@mindspring.com>,
linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linus Torvalds <torvalds@transmeta.com>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
ext2-devel@lists.sourceforge.net
Subject: Re: [PATCH] Re: Possible EXT2 File System Corruption in Kernel 2.4
Date: Thu, 11 Apr 2002 13:10:48 -0700 [thread overview]
Message-ID: <3CB5EDC8.F817E382@zip.com.au> (raw)
In-Reply-To: <E16vKwg-00056q-00@barry.mail.mindspring.net> <02041112492500.01786@sevencardstud.cable.nu> <20020411191255.GK3509@turbolinux.com>
Andreas Dilger wrote:
>
> ...
> EXT2 FILE SYSTEM
> -P: Remy Card
> -M: Remy.Card@linux.org
> -L: linux-kernel@vger.kernel.org
> +L: ext2-devel@lists.sourceforge.net
> S: Maintained
Yes, I'd support that. It's a sad thing to do, but there
is no point in misleading people in this way. Remy already
has an entry in ./CREDITS for ext2.
> This is unfortunately only a symptom of a problem and not the original
> cause. There should have previously been errors saying "error - freeing
> blocks in system zone". There is a patch I posted a few months ago to
> fix this symptom, but not the actual cause.
Do you have time to dust that patch off? Shit happens, and the
filesystems should be robust in the presence of software and
hardware failures. In this case the filesystem has reached
a point where it *knows* that it is about to do the wrong
thing, it emits a warning and then it just goes ahead and does it!
-
next prev parent reply other threads:[~2002-04-11 21:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E16vKwg-00056q-00@barry.mail.mindspring.net>
2002-04-11 16:40 ` Possible EXT2 File System Corruption in Kernel 2.4 Frank Krauss
2002-04-11 19:12 ` [PATCH] " Andreas Dilger
2002-04-11 20:10 ` Andrew Morton [this message]
2002-04-17 7:56 ` [PATCH] " Andreas Dilger
2002-05-20 9:38 ` Juan Quintela
2002-05-21 3:57 ` Andreas Dilger
2002-05-21 4:02 ` David S. Miller
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=3CB5EDC8.F817E382@zip.com.au \
--to=akpm@zip.com.au \
--cc=adilger@clusterfs.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ext2-devel@lists.sourceforge.net \
--cc=fmfkrauss@mindspring.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=torvalds@transmeta.com \
/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