From: "Otto Meier" <gf435@gmx.net>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "neilb@cse.unsw.edu.au" <neilb@cse.unsw.edu.au>
Subject: Serious file system corruption with RAID5+SMP and kernels above 2.4.0
Date: Sat, 20 Jan 2001 17:23:27 +0100 [thread overview]
Message-ID: <200101201622.f0KGMQT03162@gate2.private.net> (raw)
Two days ago I tried new kernels on my SMP SW RAID5 System
and expirienced serous file system corruption with kernels 2.4.1-pre8,9 as 2.4.0-ac8,9,10.
The same error has been reported by other people on this list. With 2.4.0 release
everything runs fine. So I backsteped to it and had no error since.
Comparing Patches from 2.4.1-pre8,9 and 2.4.0-ac10,9 leads me to the question if the
chances to the MMX und i387 code in this patches could have broken raid5 under SMP?
My boot.log file states that it uses p5_mmx block moves for performance reasons.
In the 2.4.1 series are no changes to raid5 but the corruption issue which expirience are in both
kernel series the same.
Best regards
-
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/
reply other threads:[~2001-01-20 16:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200101201622.f0KGMQT03162@gate2.private.net \
--to=gf435@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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
Powered by JetHome