From: Stephan von Krawczynski <skraw@ithnet.com>
To: maney@pobox.com
Cc: maney@two14.net, marcelo@conectiva.com.br, linux-kernel@vger.kernel.org
Subject: Re: 2.4.22-rc2 ext2 filesystem corruption
Date: Tue, 12 Aug 2003 12:18:44 +0200 [thread overview]
Message-ID: <20030812121844.521dcca3.skraw@ithnet.com> (raw)
In-Reply-To: <20030812035803.GA17921@furrr.two14.net>
On Mon, 11 Aug 2003 22:58:03 -0500
maney@two14.net (Martin Maney) wrote:
>
> Okay, further testing is clearly indicated (and I'm recompiling a test
> kernel while writing this to try to narrow it down a little), but I've
> got a very repeatable file corruption under 2.4.22-rc2 that does not
> manifest under 2.4.21. My repeatable test case only (so far?) causes
> the data in the file to be corrupted, but I suspect metadata can get
> hit as well, and I have seen some filesystem errors that were probably
> caused by this, but not so that I can say so with certainty.
Did you do a long check of your system memory with memtest? long meaning some
days...
Regards,
Stephan
next prev parent reply other threads:[~2003-08-12 10:18 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 [this message]
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
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
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=20030812121844.521dcca3.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maney@pobox.com \
--cc=maney@two14.net \
--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;
as well as URLs for NNTP newsgroup(s).