From: Andrew Morton <akpm@osdl.org>
To: linux-scsi@vger.kernel.org
Cc: Neela.Kolli@engenio.com, Andi Kleen <ak@muc.de>,
"bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@bugzilla.kernel.org>,
bloch@verdurin.com
Subject: Fw: [Bugme-new] [Bug 6052] New: Megaraid file corruption and performance degradation on x86_64 with 8G RAM
Date: Fri, 10 Feb 2006 11:26:40 -0800 [thread overview]
Message-ID: <20060210112640.4637dfdb.akpm@osdl.org> (raw)
Begin forwarded message:
Date: Fri, 10 Feb 2006 10:19:45 -0800
From: bugme-daemon@bugzilla.kernel.org
To: bugme-new@lists.osdl.org
Subject: [Bugme-new] [Bug 6052] New: Megaraid file corruption and performance degradation on x86_64 with 8G RAM
http://bugzilla.kernel.org/show_bug.cgi?id=6052
Summary: Megaraid file corruption and performance degradation on
x86_64 with 8G RAM
Kernel Version: 2.6.15-1.2005_FC4smp
Status: NEW
Severity: normal
Owner: andmike@us.ibm.com
Submitter: bloch@verdurin.com
Most recent kernel where this bug did not occur:
Distribution:
Fedora Core 4
Hardware Environment:
Tyan S2882
2 x Opteron 252
8G RAM
LSI MegaRAID SATA 150-4
Software Environment:
Problem Description:
A RAID1 mirror was setup using the MegaRAID card and 2 x 250 GB drives.
After only a day or so of use, there was severe filesystem corruption (using
ext3) and the user complained that even before the corruption it was incredibly
slow (the mirror is used to house $HOME).
We have other machines here with only 4G RAM using the same card and setup.
Performance there is fine and there's been no filesystem corruption.
In one case I removed the drives from the card and connected them to the SATA
ports on the motherboard, using software RAID. That machine is working fine.
In the other case I have tried using a Fedora test kernel, equivalent to
2.6.16-rc2, which has the latest version of the MegaRAID driver (2.20.4.7).
I was unable to recover the filesystem on the original partition when running
fsck using the new kernel. However, at least on this occasion fsck kept running
(for two days...) instead of crashing.
When running mkfs on the hardware RAID1 mirror, performance still seems to be
very slow.
Hence it appears there is a specific problem with the LSI megaraid driver on
x86_64 machines with more than 4G RAM.
Steps to reproduce:
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2006-02-10 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 19:26 Andrew Morton [this message]
2006-02-10 20:04 ` Fw: [Bugme-new] [Bug 6052] New: Megaraid file corruption and performance degradation on x86_64 with 8G RAM Gorazd Golob
2006-02-11 9:37 ` Andi Kleen
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=20060210112640.4637dfdb.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=Neela.Kolli@engenio.com \
--cc=ak@muc.de \
--cc=bloch@verdurin.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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