New: Megaraid file corruption and performance degradation on x86_64 with 8G RAM
Begin forwarded message:
Date: Fri, 10 Feb 2006 10:19:45 -0800
From: [email protected]
To: [email protected]
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: [email protected]
Submitter: [email protected]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.
Switching off the directio in megaraid's setup to cacheio should help. It's controller's (32bit) problem not drivers.
Quoted 66 lines · Andrew Morton
Begin forwarded message:
Date: Fri, 10 Feb 2006 10:19:45 -0800
From: [email protected]
To: [email protected]
Subject: [Bugme-new] [Bug 6052] New: Megaraid file corruption and performance degradation onx86_64with 8G RAMhttp://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: [email protected] Submitter: [email protected]Most recent kernel where this bug did not occur:
Distribution:
Fedora Core 4Hardware Environment:
Tyan S2882
2 x Opteron 252
8G RAM
LSI MegaRAID SATA 150-4Software 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_64machines 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. -
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 3 lines · Andrew Morton
Begin forwarded message:
Hmm, could be the merging issue too? Does megaraid do anything funny with sg lists? Does iommu=nomerge help?
If yes apply
ftp://ftp.firstfloor.org/pub/ak/x86_64/quilt/patches/gart-dma-merge
and report back.
-Andi