OpenVZ Forum


Home » General » Support » *NOT SOLVED* 3ware 8506 - CentOS 4.5 or 5.0 - OpenVZ Stock Kernel - Unstable
*NOT SOLVED* 3ware 8506 - CentOS 4.5 or 5.0 - OpenVZ Stock Kernel - Unstable [message #22458] Mon, 29 October 2007 14:13 Go to previous message
tchipman is currently offline  tchipman
Messages: 28
Registered: June 2006
Junior Member
Hi,

Just want to report this "open issue" I have got, with some slight debug progress. If I have more notes (later today or tomorrow) I'll update this thread in case it is of interest to others. Not positive this is a "bug report" yet.

I have a 32-bit dual xeon system (Tyan server-class motherboard) with a 64-bit PCI slot 3ware Raid card (model 8506, takes 8 x SATA disks)

There appears to be some problem with this 3ware card with certain kernel versions, ie,

(1) stock RHEL/CentOS 5.0 kernel is BAD to use on this card, flat out (you end up with disk failure, dmesg errors logged abundantly after significant disk IO, approx as follows:

3w-xxxx: scsi0: Character ioctl (0x1f) timed out, resetting card.
sd 0:0:0:0: rejecting I/O to offline device

the raid array then flags itself as "rebuild from scratch" state and you lose everything in the array


(2) stock RHEL/CentOS 4.5 which is booted without "noapic" and "acpi=off" kernel flags -- also is unstable. By adding these flags, it becomes stable.

(3) OpenVZ - stock production OpenVZ kernel booted for either CentOS 5 or 4.5 install .. will be unstable, regardless of use of the noapci/acpi=off flags. kernel used for test identified itself as "vmlinuz-2.6.9-023stab044.11-smp"

This machine has been reinstalled about 6 times in the last week for testing. Managed to run solid over the weekend it seems and I'm doing one last cycle of sustained disk activity (500 runs of bonnie) -- if it survives this, then I'm willing to believe that scenarion (2) above is OK (stock CentOS 4.5 kernel with the acpi-noapic flags)

Assuming it survives, I'll then try install of OpenVZ "RHEL Stock" kernel rather than the standard OVZ production kernel, and see if that runs more stable, or if that is also a lost cause.

I suspect based on observations so far,

-there is something new in RHEL5 which breaks 3ware controller hardware
-this feature may also be present in the default build of the OVZ kernel for CentOS 4.X lineage as well?

For anyone who wishes to see, there is a thread open in the CentOS bug-tracker on this 3ware hardware issue. The URL is,

http://bugs.centos.org/view.php?id=2186

(I have been posting to that thread, as have a number of other 3ware customers using CentOS 4.X or 5.X)

Lots of fun,


Tim Chipman

[Updated on: Tue, 04 December 2007 14:27] by Moderator

Report message to a moderator

 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: 2.6.32 kernel - big improvement
Next Topic: iptables shows 0 bytes at INPUT and OUTPUT
Goto Forum:
  


Current Time: Fri Nov 15 12:11:12 GMT 2024

Total time taken to generate the page: 0.03534 seconds