Issues with mvsas and SATA drivers (at least not one of the brands I
currently have attached) are unfortunately not solved.

I figured I'd upgrade the server from 10.04 LTS to 10.10 after seeing
josh.k.abbott's message.

As stated/guessed by someone earlier, the issues are indeed NOT ubuntu
specific. The mvsas driver has issues with SATA disks. It is stable with
SAS disks afaik (haven't used them myself).

See for example these:
http://kerneltrap.org/mailarchive/linux-scsi/2010/5/6/6884900/thread#mid-6884900
http://hardforum.com/showthread.php?t=1397855&page=26

Things do see to be improved. In order to test I have only attached 2
drives now (I had more in the past). When building RAID sets on those
mdadm would fail before it was finished (completely). It seems to finish
now, but it stalls frequently (hey it is improvement :)).

It might be nothing, but I only have issues with /dev/sde (only /dev/sde
and /dev/sdf are attached to mvsas. Because of issues and the need to
have the other drives stable they're attached to onboard SATA).

The 2 drives are different brands (on purpose, seen to many drives (from
all brands) fail at more or less the same time if they're from the same
batch).

I'm not sure if certain patches have been backported to this kernel
(they're not in 2.6.36 vanilla anyways), like this one from the scsi
list:

http://marc.info/?l=linux-scsi&m=128509662225051&w=2

Certainly would like to know if that patch is included, so I know if
it's useful to post to SCSI list as well.

One of the drives doesn't seem to fully do SMART (well it does output
stuff but it needs -T permissive).

Drives are:

/dev/sde:

Device Model:     WDC WD20EARS-00MVWB0


/dev/sdf

Model Family:     Seagate Barracuda LP
Device Model:     ST32000542AS

As stated mdadm sync DID complete (it never used to make it that far on
drives this large, although the set previously existed of at least 4
drives).

lspci:

00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 12)
00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root Port 
(rev 12)
00:06.0 PCI bridge: Intel Corporation Core Processor Secondary PCI Express Root 
Port (rev 12)
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 
Enhanced Host Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express 
Root Port 1 (rev 05)
00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express 
Root Port 5 (rev 05)
00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express 
Root Port 6 (rev 05)
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 
Enhanced Host Controller (rev 05)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a5)
00:1f.0 ISA bridge: Intel Corporation 3400 Series Chipset LPC Interface 
Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 6 port 
SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller 
(rev 05)
01:00.0 SCSI storage controller: Marvell Technology Group Ltd. 
MV64460/64461/64462 System Controller, Revision B (rev 01)
02:00.0 SCSI storage controller: Marvell Technology Group Ltd. 
MV64460/64461/64462 System Controller, Revision B (rev 01)
04:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
05:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
06:03.0 VGA compatible controller: Matrox Graphics, Inc. MGA G200eW WPCM450 
(rev 0a)


Messages was rather large, so attached it.

** Attachment added: "/var/log/messages stripped from most irrelevant stuff"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/554398/+attachment/1724737/+files/messages.bz2

-- 
Lucid crash on heavy DB i/o (mvsas?)
https://bugs.launchpad.net/bugs/554398
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to