[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: high iowait (100%) on SATA disks

Hello!
I can only tell you that we replaces some dozen "pata" machines with "sata", most times on the onboard sata controller (via). I cannot report bad things about that. No high cpu load (With newer seagate disk you even get command queueing on the sata disk!). 

My $.02:
1) sil is silicon image. We *never* made good experience with anything silicon-image-based. No matter if pata or sata. Even if they were on "high quality" SATA RAID cards. 2) To check disk health use Maxtor's powermax bootdisk. check website. You could also swap disk scsi0 with scsi1. 3) Could you check what happend when you copy from a non "sil" disk (pata) oder from network to the disk on scis0? Load? Maybe the sil has interrup problems? cat /proc/interrupts and check for unusual high number or so. 

rgds,
Andreas


Michael Moritz wrote:
We just put up a new machine with 3 SATA disks. The first one is doing fine. We had to use sata_sil, so they show up as scsi devices: 
$ cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: Maxtor 6Y080M0   Rev: YAR5
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: HDS724040KLSA80  Rev: KFAO
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: HDS724040KLSA80  Rev: KFAO
  Type:   Direct-Access                    ANSI SCSI revision: 05
The other two ones show all problems. I first thought they were broken disks (which is still a possibility). I checked them with badblocks. sdb gets stuck at some point and stops responding. sdc gets through but takes ages. Is this normal - they are 400G disks. I have turned my attention to sdc, after sdb segfaulted a cp with huge amounts of data. I noticed that even accesing the better one, sdc, causes the iowait to go up to 100% for longer periods of time. This is on a stock debian kernel 2.6.11-1-686 (apparently I should be using a smp kernel for hyperthreading support - would this make any difference?).
Has anyone seem anything similiar, hints? I'm running out of ideas but find it strange that both disks should be broken. 

Thanks,

mimo
Some more info lspci 
00:00.0 Host bridge: Intel Corp.: Unknown device 254c (rev 01)
00:00.1 Class ff00: Intel Corp. e7500 [Plumas] DRAM Controller Error Reporting (rev 01) 00:02.0 PCI bridge: Intel Corp. e7500 [Plumas] HI_B Virtual PCI Bridge (F0) (rev 01) 
00:1d.0 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #1) (rev 02)
00:1d.1 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #2) (rev 02)
00:1d.2 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #3) (rev 02)
00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB PCI Bridge (rev 42)
00:1f.0 ISA bridge: Intel Corp. 82801CA ISA Bridge (LPC) (rev 02)
00:1f.1 IDE interface: Intel Corp. 82801CA IDE U100 (rev 02)
00:1f.3 SMBus: Intel Corp. 82801CA/CAM SMBus (rev 02)
01:1c.0 PIC: Intel Corp. 82870P2 P64H2 I/OxAPIC (rev 04)
01:1d.0 PCI bridge: Intel Corp. 82870P2 P64H2 Hub PCI Bridge (rev 04)
01:1e.0 PIC: Intel Corp. 82870P2 P64H2 I/OxAPIC (rev 04)
01:1f.0 PCI bridge: Intel Corp. 82870P2 P64H2 Hub PCI Bridge (rev 04)
02:03.0 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01) 02:03.1 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01) 03:02.0 Unknown mass storage controller: CMD Technology Inc Silicon Image SiI 3112 SATARaid Controller(rev 02) 03:03.0 Unknown mass storage controller: CMD Technology Inc Silicon Image SiI 3112 SATARaid Controller(rev 02) 
04:01.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)

dmesg
: SCSI subsystem initialized
: libata version 1.10 loaded.
: sata_sil version 0.8
: ACPI: PCI interrupt 0000:03:02.0[A] -> GSI 26 (level, low) -> IRQ 169
: ata1: SATA max UDMA/100 cmd 0xF8802080 ctl 0xF880208A bmdma 0xF8802000 irq 169 : ata2: SATA max UDMA/100 cmd 0xF88020C0 ctl 0xF88020CA bmdma 0xF8802008 irq 169 : ata1: dev 0 cfg 49:2f00 82:7c6b 83:7b09 84:4003 85:7c69 86:3a01 87:4003 88:207f 
: ata1: dev 0 ATA, max UDMA/133, 160086528 sectors:
: ata1: dev 0 configured for UDMA/100
: scsi0 : sata_sil
: ata2: dev 0 cfg 49:2f00 82:74eb 83:7feb 84:4123 85:74e8 86:3c03 87:4123 88:207f 
: ata2: dev 0 ATA, max UDMA/133, 781422768 sectors: lba48
: ata2: dev 0 configured for UDMA/100
: scsi1 : sata_sil
:   Vendor: ATA       Model: Maxtor 6Y080M0    Rev: YAR5
:   Type:   Direct-Access                      ANSI SCSI revision: 05
:   Vendor: ATA       Model: HDS724040KLSA80   Rev: KFAO
:   Type:   Direct-Access                      ANSI SCSI revision: 05
: ACPI: PCI interrupt 0000:03:03.0[A] -> GSI 27 (level, low) -> IRQ 177
: ata3: SATA max UDMA/100 cmd 0xF8804480 ctl 0xF880448A bmdma 0xF8804400 irq 177 : ata4: SATA max UDMA/100 cmd 0xF88044C0 ctl 0xF88044CA bmdma 0xF8804408 irq 177 : ata3: dev 0 cfg 49:2f00 82:74eb 83:7feb 84:4123 85:74e8 86:3c03 87:4123 88:207f 
: ata3: dev 0 ATA, max UDMA/133, 781422768 sectors: lba48
: ata3: dev 0 configured for UDMA/100
: scsi2 : sata_sil
: ata4: no device found (phy stat 00000000)
: scsi3 : sata_sil
:   Vendor: ATA       Model: HDS724040KLSA80   Rev: KFAO
:   Type:   Direct-Access                      ANSI SCSI revision: 05
: NET: Registered protocol family 1
: SCSI device sda: 160086528 512-byte hdwr sectors (81964 MB)
: SCSI device sda: drive cache: write back
: SCSI device sda: 160086528 512-byte hdwr sectors (81964 MB)
: SCSI device sda: drive cache: write back
:  /dev/scsi/host0/bus0/target0/lun0: p1 p2 p3 p4 < p5 p6 >
: Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
: SCSI device sdb: 781422768 512-byte hdwr sectors (400088 MB)
: SCSI device sdb: drive cache: write back
: SCSI device sdb: 781422768 512-byte hdwr sectors (400088 MB)
: SCSI device sdb: drive cache: write back
:  /dev/scsi/host1/bus0/target0/lun0: unknown partition table
: Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0
: SCSI device sdc: 781422768 512-byte hdwr sectors (400088 MB)
: SCSI device sdc: drive cache: write back
: SCSI device sdc: 781422768 512-byte hdwr sectors (400088 MB)
: SCSI device sdc: drive cache: write back
:  /dev/scsi/host2/bus0/target0/lun0: unknown partition table
: Attached scsi disk sdc at scsi2, channel 0, id 0, lun 0
Reply to: