From: Andreas Dilger <adilger@clusterfs.com>
To: Arnaldo Carvalho de Melo <acme@conectiva.com.br>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
Pawel Kot <pkot@linuxnews.pl>,
lkml <linux-kernel@vger.kernel.org>,
Andre Hedrick <andre@serialata.org>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
"Stephen C. Tweedie" <sct@redhat.com>
Subject: Re: Another -pre
Date: Mon, 3 Jun 2002 18:10:28 -0600 [thread overview]
Message-ID: <20020604001028.GI18668@turbolinux.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0206031155200.4146-100000@freak.distro.conectiva> <1023149710.6773.82.camel@irongate.swansea.linux.org.uk> <20020603232707.GI6062@conectiva.com.br>
On Jun 03, 2002 20:27 -0300, Arnaldo Carvalho de Melo wrote:
> > 1 Weird corruption report with AMD chipset in PIO mode
>
> Oh, I'm not alone ;) Well, up to now it _seems_ that ext3 is saving my day,
> but it only happened two time after I upgraded to 2.4.19-pre8-ac5, none after
> I upgraded to 2.4.19-pre9-ac3, but I can't manage to make 'hdparm -X68 /dev/hdd'
> to work :( I have already sent detailed information to Andre and discussed
> and tried several things sugested in a irc chat.
>
> Short description: I use ext3 over raid0, using /dev/hda4 and /dev/hdd1,
> /dev/hdc has a CDRW drive, mostly unused, /dev/hdb has nothing, two times
> /dev/hda stopped responding, not reproducible AFAIT.
Well, there was some corruption in ext3 if you used it over MD RAID with
data=journal mode that was discussed recently on ext3-users. There was
a patch posted by Neil Brown which I resend here (full thread archived
at https://listman.redhat.com/pipermail/ext3-users/).
According to Stephen Tweedie, the patch will not correctly handle
filesystems with 1kB or 2kB block sizes, but those are rare these days
(only 1kB blocks are created by default for small filesystems, < 500MB
in size).
This may or may not fix your problem (don't know the details), but it
can't hurt to try. It definitely is not a "/dev/hda stopped responding"
kind of fix, but it _is_ a "weird corruption with ext3 and MD RAID" kind
of fix.
Cheers, Andreas
============================================================================
--- ./fs/jbd/commit.c 2002/05/28 04:15:18 1.1
+++ ./fs/jbd/commit.c 2002/05/28 22:44:48
@@ -663,12 +663,13 @@
* there's no point in keeping a checkpoint record for
* it. */
bh = jh2bh(jh);
- if (buffer_jdirty(bh)) {
+ if (buffer_jdirty(bh) && !__buffer_state(bh, Freed)) {
JBUFFER_TRACE(jh, "add to new checkpointing trans");
__journal_insert_checkpoint(jh, commit_transaction);
JBUFFER_TRACE(jh, "refile for checkpoint writeback");
__journal_refile_buffer(jh);
} else {
+ clear_bit(BH_Freed, &bh->b_state);
J_ASSERT_BH(bh, !buffer_dirty(bh));
J_ASSERT_JH(jh, jh->b_next_transaction == NULL);
__journal_unfile_buffer(jh);
--- ./fs/jbd/transaction.c 2002/05/26 23:13:05 1.2
+++ ./fs/jbd/transaction.c 2002/05/28 09:24:45
@@ -1834,6 +1834,7 @@
* running transaction if that is set, but nothing
* else. */
JBUFFER_TRACE(jh, "on committing transaction");
+ set_bit(BH_Freed, &bh->b_state);
if (jh->b_next_transaction) {
J_ASSERT(jh->b_next_transaction ==
journal->j_running_transaction);
_______________________________________________
Ext3-users mailing list
Ext3-users@redhat.com
https://listman.redhat.com/mailman/listinfo/ext3-users
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/
next prev parent reply other threads:[~2002-06-04 0:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-03 14:23 Another -pre Marcelo Tosatti
2002-06-03 15:47 ` Pawel Kot
2002-06-03 14:55 ` Marcelo Tosatti
2002-06-03 16:02 ` Pawel Kot
2002-06-03 16:13 ` Marcelo Tosatti
2002-06-04 0:15 ` Alan Cox
2002-06-03 23:24 ` Matt Simonsen
2002-06-08 19:42 ` Andre Hedrick
2002-06-03 23:27 ` Arnaldo Carvalho de Melo
2002-06-04 0:10 ` Andreas Dilger [this message]
2002-06-04 8:35 ` Daniela Engert
2002-06-08 19:30 ` Andre Hedrick
-- strict thread matches above, loose matches on Subject: below --
2002-06-04 2:46 Neil Brown
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=20020604001028.GI18668@turbolinux.com \
--to=adilger@clusterfs.com \
--cc=acme@conectiva.com.br \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@serialata.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=neilb@cse.unsw.edu.au \
--cc=pkot@linuxnews.pl \
--cc=sct@redhat.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