From: "Mohammad A. Haque" <mhaque@haque.net>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Alexander Viro <viro@math.psu.edu>,
linux-kernel <linux-kernel@vger.kernel.org>,
Tigran Aivazian <tigran@veritas.com>
Subject: Re: ext2 filesystem corruptions back from dead? 2.4.0-test11
Date: Tue, 28 Nov 2000 17:55:50 -0500 [thread overview]
Message-ID: <3A2437F6.6380A1BF@haque.net> (raw)
In-Reply-To: <14877.53881.182935.597766@notabene.cse.unsw.edu.au> <Pine.GSO.4.21.0011240006040.12702-100000@weyl.math.psu.edu> <14881.62969.786424.812353@notabene.cse.unsw.edu.au>
Ok, I'm not sure what else to try. I've even tried throwing around 1.6
GB of data, and copying and deleting at the same time. Nothing. Again,
this is _without_ the patches sent by Alexander.
I think I'm just gonna go on to test12-pre2.
Neil Brown wrote:
>
> Turns out my data is a false alarm. It was a bug in my raid5 code -
> and not a recent bug either - that was causing my filesystem
> corruption.
>
> So if your earlier patches work for everybody else then they look like
> a good way to go. I have fixed my fatal flaw and I cannot reproduce
> the problems any more. Patch has gone to Alan.
--
=====================================================================
Mohammad A. Haque http://www.haque.net/
mhaque@haque.net
"Alcohol and calculus don't mix. Project Lead
Don't drink and derive." --Unknown http://wm.themes.org/
batmanppc@themes.org
=====================================================================
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-28 23:26 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-23 5:51 ext2 filesystem corruptions back from dead? 2.4.0-test11 Mohammad A. Haque
2000-11-23 6:03 ` Neil Brown
2000-11-23 9:37 ` Alexander Viro
2000-11-23 11:05 ` Neil Brown
2000-11-23 12:12 ` Neil Brown
2000-11-23 16:36 ` Alexander Viro
2000-11-23 17:12 ` Alexander Viro
2000-11-23 20:51 ` Tigran Aivazian
2000-11-23 20:56 ` Mohammad A. Haque
2000-11-24 2:29 ` Neil Brown
2000-11-24 5:32 ` Alexander Viro
2000-11-24 5:42 ` Mohammad A. Haque
2000-11-24 5:57 ` Alexander Viro
2000-11-27 5:49 ` Neil Brown
2000-11-28 22:55 ` Mohammad A. Haque [this message]
2000-11-29 4:37 ` Mohammad A. Haque
2000-11-29 6:44 ` Ion Badulescu
2000-11-29 7:08 ` Mohammad A. Haque
2000-11-29 7:20 ` Ion Badulescu
2000-11-29 7:23 ` Mohammad A. Haque
2000-11-29 8:54 ` Tigran Aivazian
2000-11-29 10:01 ` Mohammad A. Haque
2000-11-23 12:52 ` Guest section DW
2000-11-24 4:58 ` Ion Badulescu
2000-11-24 5:29 ` Guest section DW
2000-11-24 5:34 ` Mohammad A. Haque
2000-11-24 8:51 ` Ion Badulescu
2000-11-24 13:35 ` Guest section DW
2000-11-24 17:41 ` Linus Torvalds
2000-11-24 15:06 ` Mohammad A. Haque
2000-11-24 5:59 ` Andre Hedrick
2000-11-24 6:11 ` Alexander Viro
2000-11-24 6:30 ` Andre Hedrick
2000-11-24 7:03 ` Alexander Viro
2000-11-24 7:58 ` Andre Hedrick
2000-11-24 8:43 ` Ion Badulescu
2000-11-24 11:06 ` Mike Ricketts
2000-11-24 11:11 ` Tigran Aivazian
2000-11-25 2:21 ` Andre Hedrick
2000-11-23 6:40 ` Andreas Dilger
2000-11-23 7:22 ` Pär-Ola Nilsson
-- strict thread matches above, loose matches on Subject: below --
2000-11-25 22:42 Rick Bunke
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=3A2437F6.6380A1BF@haque.net \
--to=mhaque@haque.net \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=tigran@veritas.com \
--cc=viro@math.psu.edu \
/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