From: Dave Jones <davej@suse.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Warning, 2.5.3 eats filesystems
Date: Wed, 6 Feb 2002 02:39:37 +0100 [thread overview]
Message-ID: <20020206023937.G25441@suse.de> (raw)
In-Reply-To: <20020205192826.GA112@elf.ucw.cz> <878za7wmg0.fsf@inanna.rimspace.net> <20020206010219.YXFM10804.out006.verizon.net@pool-141-150-235-204.delv.east.verizon.net>
In-Reply-To: <20020206010219.YXFM10804.out006.verizon.net@pool-141-150-235-204.delv.east.verizon.net>; from skip.ford@verizon.net on Tue, Feb 05, 2002 at 07:59:57PM -0500
On Tue, Feb 05, 2002 at 07:59:57PM -0500, Skip Ford wrote:
> I can confirm inode errors also. However, I can't be sure it's 2.5.3 that
> did it.
Recall that pre3/pre4/pre5 had the missing ext2_inode_info initialisation bug.
If you booted any of those, and have only just done a fsck, it could
be a leftover artifact of a now-fixed bug.
> All of the errors I've had all seemed to be files included in the
> pre-patch that broke Configure.help into pieces. I don't know the code
> well enough, but if the errors could only have happened at file creation
> then that would rule out 2.5.3.
Indeed, that change was in pre5, which was the last pre to feature
aforementioned buglet.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-02-06 1:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 19:28 Warning, 2.5.3 eats filesystems Pavel Machek
2002-02-05 23:14 ` Daniel Pittman
2002-02-06 0:59 ` Skip Ford
2002-02-06 1:39 ` Dave Jones [this message]
2002-02-06 4:59 ` Daniel Pittman
2002-02-06 15:42 ` Pavel Machek
2002-02-06 23:30 ` Heinz Diehl
2002-02-06 23:39 ` Alexander Viro
2002-02-07 20:34 ` Heinz Diehl
2002-02-08 10:50 ` Pavel Machek
2002-02-08 21:48 ` Heinz Diehl
2002-02-08 11:14 ` Pavel Machek
2002-02-08 21:50 ` Andre Hedrick
2002-02-08 11:36 ` WARNING: 2.5.3 -- IDE damages data! [was Re: Warning, 2.5.3 eats filesystems] Pavel Machek
2002-02-06 17:49 ` Warning, 2.5.3 eats filesystems Olaf Zaplinski
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=20020206023937.G25441@suse.de \
--to=davej@suse.de \
--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.