From: maney@two14.net (Martin Maney)
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: maney@pobox.com, linux-kernel@vger.kernel.org
Subject: Re: 2.4.22-rc2 ext2 filesystem corruption
Date: Tue, 12 Aug 2003 11:56:24 -0500 [thread overview]
Message-ID: <20030812165624.GA1070@furrr.two14.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0308121109530.5995-100000@logos.cnet>
On Tue, Aug 12, 2003 at 11:10:51AM -0300, Marcelo Tosatti wrote:
> I'll try to reproduce around here. In the meantime can you try to isolate
> the corruption. You said it didnt happen with 2.4.21 -- which pre shows up
> the problem?
The problem appears only in rc2 (okay, assuming it's not a
regression). With 2.4.21-rc1 the file corruption I've been seeing does
not happen. From what Stephan has said I think I should try some more
varied tests. At this point I plan to do that a little later; I will
also try an rc2 with unnecessary features omitted from the build. So
far I've stayed with the base config, but it's a config shared by most
of the machines on the LAN and thus has plenty of extras.
--
Self-pity can make one weep, as can onions. -- Fodor
next prev parent reply other threads:[~2003-08-12 16:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-12 3:58 2.4.22-rc2 ext2 filesystem corruption Martin Maney
2003-08-12 10:18 ` Stephan von Krawczynski
2003-08-12 13:12 ` Marcelo Tosatti
2003-08-12 13:42 ` Martin Maney
2003-08-12 14:10 ` Marcelo Tosatti
2003-08-12 15:14 ` Martin Maney
2003-08-12 16:58 ` Marcelo Tosatti
2003-08-12 17:11 ` Alan Cox
2003-08-12 16:56 ` Martin Maney [this message]
2003-08-12 17:09 ` Marcelo Tosatti
2003-08-12 21:36 ` Martin Maney
2003-08-13 11:28 ` Alan Cox
2003-08-13 11:37 ` Stephan von Krawczynski
2003-08-13 14:55 ` Marcelo Tosatti
2003-08-13 18:13 ` Martin Maney
2003-08-13 19:40 ` Alan Cox
2003-08-16 6:35 ` Martin Maney
2003-08-17 0:09 ` Mike Fedyk
2003-08-13 22:58 ` Nerijus Baliunas
-- strict thread matches above, loose matches on Subject: below --
2003-08-12 6:20 Alex Davis
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=20030812165624.GA1070@furrr.two14.net \
--to=maney@two14.net \
--cc=linux-kernel@vger.kernel.org \
--cc=maney@pobox.com \
--cc=marcelo@conectiva.com.br \
/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