Here are the iostats:<br><br><br>Device: rrqm/s wrqm/s r/s w/s rsec/s wsec/s avgrq-sz avgqu-sz await svctm %util<br>sda 0.15 2.47 0.41 0.82 13.01 26.36 31.97 0.01 6.98 1.01 0.12<br>
sda1 0.02 0.00 0.00 0.00 0.04 0.00 24.50 0.00 5.38 4.82 0.00<br>sda2 0.01 0.00 0.00 0.00 0.03 0.00 37.79 0.00 6.77 5.85 0.00<br>sda3 0.12 2.47 0.40 0.82 12.93 26.36 31.98 0.01 6.96 1.01 0.12<br>
sdb 1.48 0.00 315.21 0.01 40533.39 0.75 128.59 26.94 85.45 2.80 88.24<br>sdb1 1.47 0.00 315.21 0.01 40533.30 0.75 128.59 26.94 85.45 2.80 88.24<br>sdc 1.04 0.00 315.65 0.01 40533.48 1.09 128.41 1.92 6.07 0.88 27.69<br>
sdc1 1.02 0.00 315.65 0.01 40533.39 1.09 128.41 1.92 6.07 0.88 27.68<br>md0 0.00 0.00 0.00 0.00 0.00 0.00 8.00 0.00 0.00 0.00 0.00<br><br>Device: rrqm/s wrqm/s r/s w/s rsec/s wsec/s avgrq-sz avgqu-sz await svctm %util<br>
sda 0.00 16.80 0.00 1.00 0.00 142.40 142.40 0.00 1.00 0.60 0.06<br>sda1 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00<br>sda2 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00<br>
sda3 0.00 16.80 0.00 1.00 0.00 142.40 142.40 0.00 1.00 0.60 0.06<br>sdb 56.40 0.00 189.60 0.00 30822.40 0.00 162.57 17.45 93.23 5.28 100.02<br>sdb1 56.40 0.00 189.60 0.00 30822.40 0.00 162.57 17.45 93.23 5.28 100.02<br>
sdc 0.00 0.00 239.40 0.00 30643.20 0.00 128.00 0.69 2.89 0.68 16.24<br>sdc1 0.00 0.00 239.40 0.00 30643.20 0.00 128.00 0.69 2.89 0.68 16.24<br>md0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00<br>
<br><br>The samsung is on sdb and almost always 100% and svctm is higher than 2.....<br><br><br><br><div class="gmail_quote">On Mon, Sep 27, 2010 at 7:05 PM, Tom Bishop <span dir="ltr"><<a href="mailto:bishoptf@gmail.com">bishoptf@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Thanks ROss, I poured through my dmesg logs and all looks well, things appear fine but i don't think the samsung should be running at 100%...something is not right but it hasn't bit me yet....her are my dmesg logs...<br>
<br>scsi0 : ahci<br>scsi1 : ahci<br>scsi2 : ahci<br>scsi3 : ahci<br>scsi4 : ahci<br>scsi5 : ahci<br>ata1: SATA max UDMA/133 abar m1024@0xfe6ffc00 port 0xfe6ffd00 irq 225<br>ata2: SATA max UDMA/133 abar m1024@0xfe6ffc00 port 0xfe6ffd80 irq 225<br>
ata3: SATA max UDMA/133 abar m1024@0xfe6ffc00 port 0xfe6ffe00 irq 225<br>ata4: SATA max UDMA/133 abar m1024@0xfe6ffc00 port 0xfe6ffe80 irq 225<br>ata5: SATA max UDMA/133 abar m1024@0xfe6ffc00 port 0xfe6fff00 irq 225<br>ata6: SATA max UDMA/133 abar m1024@0xfe6ffc00 port 0xfe6fff80 irq 225<br>
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)<br>ata1.00: ATA-8: WDC WD3200AAJS-00L7A0, 01.03E01, max UDMA/133<br>ata1.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 31/32)<br>ata1.00: configured for UDMA/133<br>
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)<br>ata2.00: ATA-8: SAMSUNG HD103SJ, 1AJ10001, max UDMA/133<br>ata2.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)<br>ata2.00: configured for UDMA/133<br>ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)<br>
ata3.00: ATA-8: ST31000528AS, CC3E, max UDMA/133<br>ata3.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)<br>ata3.00: configured for UDMA/133<br>ata4: SATA link down (SStatus 0 SControl 300)<br>ata5: SATA link down (SStatus 0 SControl 300)<br>
ata6: SATA link down (SStatus 0 SControl 300)<br> Vendor: ATA Model: WDC WD3200AAJS-0 Rev: 01.0<br> Type: Direct-Access ANSI SCSI revision: 05<br>SCSI device sda: 625142448 512-byte hdwr sectors (320073 MB)<br>
sda: Write Protect is off<br>sda: Mode Sense: 00 3a 00 00<br>SCSI device sda: drive cache: write back<br>SCSI device sda: 625142448 512-byte hdwr sectors (320073 MB)<br>sda: Write Protect is off<br>sda: Mode Sense: 00 3a 00 00<br>
SCSI device sda: drive cache: write back<br> sda: sda1 sda2 sda3<br>sd 0:0:0:0: Attached scsi disk sda<br> Vendor: ATA Model: SAMSUNG HD103SJ Rev: 1AJ1<br> Type: Direct-Access ANSI SCSI revision: 05<br>
SCSI device sdb: 1953525168 512-byte hdwr sectors (1000205 MB)<br>sdb: Write Protect is off<br>sdb: Mode Sense: 00 3a 00 00<br>SCSI device sdb: drive cache: write back<br>SCSI device sdb: 1953525168 512-byte hdwr sectors (1000205 MB)<br>
sdb: Write Protect is off<br>sdb: Mode Sense: 00 3a 00 00<br>SCSI device sdb: drive cache: write back<br> sdb: sdb1<br>sd 1:0:0:0: Attached scsi disk sdb<br> Vendor: ATA Model: ST31000528AS Rev: CC3E<br> Type: Direct-Access ANSI SCSI revision: 05<br>
SCSI device sdc: 1953525168 512-byte hdwr sectors (1000205 MB)<br>sdc: Write Protect is off<br>sdc: Mode Sense: 00 3a 00 00<br>SCSI device sdc: drive cache: write back<br>SCSI device sdc: 1953525168 512-byte hdwr sectors (1000205 MB)<br>
sdc: Write Protect is off<br>sdc: Mode Sense: 00 3a 00 00<br>SCSI device sdc: drive cache: write back<br> sdc: sdc1<br>sd 2:0:0:0: Attached scsi disk sdc<br>device-mapper: uevent: version 1.0.3<br>device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised: <a href="mailto:dm-devel@redhat.com" target="_blank">dm-devel@redhat.com</a><br>
device-mapper: dm-raid45: initialized v0.2594l<br><br><br>Also, smartctl output...<br><br>smartctl -A /dev/sdb<br>smartctl version 5.38 [x86_64-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen<br>Home page is <a href="http://smartmontools.sourceforge.net/" target="_blank">http://smartmontools.sourceforge.net/</a><br>
<br>=== START OF READ SMART DATA SECTION ===<br>SMART Attributes Data Structure revision number: 16<br>Vendor Specific SMART Attributes with Thresholds:<br>ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE<br>
1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 0<br> 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0<br> 3 Spin_Up_Time 0x0023 071 071 025 Pre-fail Always - 9011<br>
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 5<br> 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0<br> 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0<br>
8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0<br> 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 64<br> 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0<br>
11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always - 0<br> 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 5<br>191 G-Sense_Error_Rate 0x0022 252 252 000 Old_age Always - 0<br>
192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0<br>194 Temperature_Celsius 0x0002 057 053 000 Old_age Always - 43 (Lifetime Min/Max 20/47)<br>195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0<br>
196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0<br>197 Current_Pending_Sector 0x0032 252 252 000 Old_age Always - 0<br>198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0<br>
199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0<br>200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 0<br>223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0<br>
225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 5<div><div></div><div class="h5"><br><br><br><br><br><br><br><br><br><div class="gmail_quote">On Mon, Sep 27, 2010 at 5:54 PM, Ross Walker <span dir="ltr"><<a href="mailto:rswwalker@gmail.com" target="_blank">rswwalker@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div>On Sep 27, 2010, at 1:24 PM, Les Mikesell <<a href="mailto:lesmikesell@gmail.com" target="_blank">lesmikesell@gmail.com</a>> wrote:<br>
<br>
> On 9/27/2010 12:19 PM, Benjamin Franz wrote:<br>
>> On 09/27/2010 08:15 AM, Tom Bishop wrote:<br>
>>> So I'm in the process of building and testing a raid setup and it<br>
>>> appeared to take along time to build I came across some settings for<br>
>>> setting the min amount of time and that helped but it appears that one<br>
>>> of the disks is struggling (100 utilization) vs the other one...I was<br>
>>> wondering if anyone else has seen this and if so, is their a solution<br>
>>> for it...my 2 disks are 1 Samsung F3 1tb /dev/sdb and 1 Seagate<br>
>>> 7200.12 1Tb /dev/sdc...smartctl looks good on both....<br>
>>><br>
>>><br>
>><br>
>> [...]<br>
>><br>
>> What is the output from 'cat /proc/mdstat'?<br>
><br>
> Also, head position/motion is the usual limiting factor with disk<br>
> performance. Do you have other disk activity that will keep yanking the<br>
> head on the active drive away from the track currently needed for the<br>
> rebuild?<br>
<br>
</div>Also, also, if any of the drives are operating in PIO mode (Legacy Mode) then rebuild times will be horrific, as well as performance afterward. Make sure all drives are in SATA/AHCI mode.<br>
<font color="#888888"><br>
-Ross<br>
</font><br>
PS look at svc_tm in iostat and make sure all drives are performing correctly. Maybe a bad cable or flakey port expander...<br>
<div><div></div><div>_______________________________________________<br>
CentOS mailing list<br>
<a href="mailto:CentOS@centos.org" target="_blank">CentOS@centos.org</a><br>
<a href="http://lists.centos.org/mailman/listinfo/centos" target="_blank">http://lists.centos.org/mailman/listinfo/centos</a><br>
</div></div></blockquote></div><br>
</div></div></blockquote></div><br>