Scrub times

Status
Not open for further replies.

Wolfeman0101

Patron
Joined
Jun 14, 2012
Messages
428
So slow...
Code:
[root@nibbler] ~# zpool status -v
  pool: Vol1
 state: ONLINE
  scan: scrub repaired 352K in 69h51m with 0 errors on Sat Nov  3 21:53:07 2012
config:

        NAME                                            STATE     READ WRITE CKSUM
        Vol1                                            ONLINE       0     0     0
          raidz2-0                                      ONLINE       0     0     0
            gptid/6dd242a6-cafb-11e1-915d-001517a03d00  ONLINE       0     0     0
            gptid/6e71f8fa-cafb-11e1-915d-001517a03d00  ONLINE       0     0     0
            gptid/6f39b462-cafb-11e1-915d-001517a03d00  ONLINE       0     0     0
            gptid/6feb82b0-cafb-11e1-915d-001517a03d00  ONLINE       0     0     0
            gptid/709a11f8-cafb-11e1-915d-001517a03d00  ONLINE       0     0     0
            gptid/713a3786-cafb-11e1-915d-001517a03d00  ONLINE       0     0     0

errors: No known data errors


During the scrub I ran a gstat and it looks like ada4 and ada5 are maxing out.
Code:
dT: 1.001s  w: 1.000s  filter: ada
 L(q)  ops/s    r/s   kBps   ms/r    w/s   kBps   ms/w   %busy Name
    0    243    233   8728    2.8     10     84    0.9   26.7| ada0
    0    252    242   8920    3.5     10     84    0.9   29.3| ada1
    0      0      0      0    0.0      0      0    0.0    0.0| ada0p1
    0    243    233   8728    2.8     10     84    0.9   26.9| ada0p2
    0      0      0      0    0.0      0      0    0.0    0.0| ada1p1
    0    252    242   8920    3.5     10     84    1.0   29.6| ada1p2
    0    247    237   8728    2.8     10     84    0.3   26.0| ada2
    0    236    226   8728    2.8     10     84    0.3   25.9| ada3
    4    119    113   9651   85.2      6     48   35.3  100.1| ada4
    5    118    113   9871   86.7      5     48   27.4  102.2| ada5
    0      0      0      0    0.0      0      0    0.0    0.0| ada2p1
    0    247    237   8728    2.8     10     84    0.4   26.2| ada2p2
    0      0      0      0    0.0      0      0    0.0    0.0| ada3p1
    0    236    226   8728    2.9     10     84    0.4   26.1| ada3p2
    0      0      0      0    0.0      0      0    0.0    0.0| ada4p1
    4    119    113   9651   85.2      6     48   35.3  100.1| ada4p2
    0      0      0      0    0.0      0      0    0.0    0.0| ada5p1
    5    118    113   9871   86.7      5     48   27.4  102.2| ada5p2
 

paleoN

Wizard
Joined
Apr 22, 2012
Messages
1,402
During the scrub I ran a gstat and it looks like ada4 and ada5 are maxing out.
At that moment in time or regularly? If the latter that's something you want to address. Two under performing drives will certainly pull down the performance of the entire array.

From an SSH session as root the output of:
Code:
smartctl -q noserial -a /dev/ada4

smartctl -q noserial -a /dev/ada5


FYI, an easier to read gstat:
Code:
gstat -I1s -f ada.$


Also, limiting vfs.zfs.vdev.max_pending to 5 may improve latencies for other activities during the scrub, but it will not improve scrub times. If anything they will take slightly longer.
 

Wolfeman0101

Patron
Joined
Jun 14, 2012
Messages
428
At that moment in time or regularly? If the latter that's something you want to address. Two under performing drives will certainly pull down the performance of the entire array.

From an SSH session as root the output of:
Code:
smartctl -q noserial -a /dev/ada4

smartctl -q noserial -a /dev/ada5


FYI, an easier to read gstat:
Code:
gstat -I1s -f ada.$


Also, limiting vfs.zfs.vdev.max_pending to 5 may improve latencies for other activities during the scrub, but it will not improve scrub times. If anything they will take slightly longer.
Well it was during the scrub but is there a way to put some load on the drives and see if 4 & 5 are acting up? Thanks for the gstat tip.





Code:
[root@nibbler] ~# smartctl -q noserial -a /dev/ada4
smartctl 5.43 2012-06-30 r3573 [FreeBSD 8.3-RELEASE-p4 amd64] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Caviar Green (Adv. Format)
Device Model:     WDC WD20EARX-00PASB0
Firmware Version: 51.0AB51
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Fri Nov  9 20:01:24 2012 PST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x85)	Offline data collection activity
					was aborted by an interrupting command from host.
					Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(38460) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 371) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x3035)	SCT Status supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       1
  3 Spin_Up_Time            0x0027   201   164   021    Pre-fail  Always       -       4950
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       56
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   097   097   000    Old_age   Always       -       2873
 10 Spin_Retry_Count        0x0032   100   253   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       54
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       50
193 Load_Cycle_Count        0x0032   195   195   000    Old_age   Always       -       16585
194 Temperature_Celsius     0x0022   119   098   000    Old_age   Always       -       31
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       1
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%      2858         -
# 2  Short offline       Completed without error       00%      2835         -
# 3  Short offline       Completed without error       00%      2811         -
# 4  Short offline       Completed without error       00%      2787         -
# 5  Short offline       Completed without error       00%      2770         -
# 6  Short offline       Completed without error       00%      2744         -
# 7  Short offline       Completed without error       00%      2736         -
# 8  Short offline       Completed without error       00%      2699         -
# 9  Short offline       Completed without error       00%      2695         -
#10  Short offline       Completed without error       00%      2648         -
#11  Short offline       Completed without error       00%      2576         -
#12  Short offline       Completed without error       00%      2553         -
#13  Short offline       Completed without error       00%      2529         -
#14  Short offline       Completed without error       00%      2505         -
#15  Short offline       Completed without error       00%      2481         -
#16  Short offline       Completed without error       00%      2457         -
#17  Short offline       Completed without error       00%      2433         -
#18  Short offline       Completed without error       00%      2409         -
#19  Short offline       Completed without error       00%      2385         -
#20  Short offline       Completed without error       00%      2361         -
#21  Short offline       Completed without error       00%      2338         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.


Code:
[root@nibbler] ~# smartctl -q noserial -a /dev/ada5

smartctl 5.43 2012-06-30 r3573 [FreeBSD 8.3-RELEASE-p4 amd64] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Caviar Green (Adv. Format)
Device Model:     WDC WD20EARX-00PASB0
Firmware Version: 51.0AB51
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Fri Nov  9 20:03:43 2012 PST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x85)	Offline data collection activity
					was aborted by an interrupting command from host.
					Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(38160) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 368) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x3035)	SCT Status supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   204   168   021    Pre-fail  Always       -       4775
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       56
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   097   097   000    Old_age   Always       -       2873
 10 Spin_Retry_Count        0x0032   100   253   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       54
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       50
193 Load_Cycle_Count        0x0032   196   196   000    Old_age   Always       -       14699
194 Temperature_Celsius     0x0022   121   101   000    Old_age   Always       -       29
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%      2859         -
# 2  Short offline       Completed without error       00%      2835         -
# 3  Short offline       Completed without error       00%      2811         -
# 4  Short offline       Completed without error       00%      2787         -
# 5  Short offline       Completed without error       00%      2770         -
# 6  Short offline       Completed without error       00%      2745         -
# 7  Short offline       Completed without error       00%      2737         -
# 8  Short offline       Completed without error       00%      2700         -
# 9  Short offline       Completed without error       00%      2696         -
#10  Short offline       Completed without error       00%      2649         -
#11  Short offline       Completed without error       00%      2577         -
#12  Short offline       Completed without error       00%      2553         -
#13  Short offline       Completed without error       00%      2529         -
#14  Short offline       Completed without error       00%      2505         -
#15  Short offline       Completed without error       00%      2481         -
#16  Short offline       Completed without error       00%      2458         -
#17  Short offline       Completed without error       00%      2434         -
#18  Short offline       Completed without error       00%      2410         -
#19  Short offline       Completed without error       00%      2386         -
#20  Short offline       Completed without error       00%      2362         -
#21  Short offline       Completed without error       00%      2338         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
 

paleoN

Wizard
Joined
Apr 22, 2012
Messages
1,402
Well it was during the scrub but is there a way to put some load on the drives and see if 4 & 5 are acting up?
A scrub is quite intensive. You can also run the dd commands from the [thread=981]performance sticky[/thread]. The main thing is to read/write large files or always read new files to make sure you are hitting the disks.

Speaking of, they both appear fine. I would wdiddle them if you haven't already. Disk ada4 has 199 UDMA_CRC_Error_Count with a value of 1. You want this zero. Given its total power on hours it certainly should be zero. It's only 1 so it may just have been a fluke. I wouldn't worry about it, but I would keep an eye on it.

AFAIK, the short SMART tests are fairly worthless with these drives. They properly update their attributes automatically. Switch them to long tests and don't run them daily.
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,525
AFAIK, the short SMART tests are fairly worthless with these drives. They properly update their attributes automatically. Switch them to long tests and don't run them daily.

Just out of curiosity, is there a recommended schedule for long tests?
 

Wolfeman0101

Patron
Joined
Jun 14, 2012
Messages
428
A scrub is quite intensive. You can also run the dd commands from the [thread=981]performance sticky[/thread]. The main thing is to read/write large files or always read new files to make sure you are hitting the disks.

Speaking of, they both appear fine. I would wdiddle them if you haven't already. Disk ada4 has 199 UDMA_CRC_Error_Count with a value of 1. You want this zero. Given its total power on hours it certainly should be zero. It's only 1 so it may just have been a fluke. I wouldn't worry about it, but I would keep an eye on it.

AFAIK, the short SMART tests are fairly worthless with these drives. They properly update their attributes automatically. Switch them to long tests and don't run them daily.

I have no idea how to run WDIDLE. Any tips?
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,525
My tip would be to go read up on it and set it up if you haven't already. You might not be too happy if you start getting SMART failures that you can't correct because of the head parking count(or whatever it is). You'll have to use a DOS boot disk since WDIDLE only runs from DOS.
 

paleoN

Wizard
Joined
Apr 22, 2012
Messages
1,402
Just out of curiosity, is there a recommended schedule for long tests?
Not really, aside from less then daily and more often then yearly. Personally I run them weekly when nothing else is going on. How much data you have & how often you scrub can come into play as well. If your disks are mostly full and you scrub often then you are already reading most of the disk surface.

Assuming your server isn't heavily accessed 24x7 I would run them at least monthly.
 

Wolfeman0101

Patron
Joined
Jun 14, 2012
Messages
428
So I'm bumping my old thread again. I figure that's better than a new one.

Can someone walk me through figuring out why my scrubs only happen at about 40Mb/s? If it's the CPU I'll go get a new one but I want to be sure that'll help. I just can't seem to figure out why scrubs are sooooo sllooowoowow.
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,525
Literally, there are dozens of reasons why scrubs can be slow. The number of possible causes are almost endless.
 

Wolfeman0101

Patron
Joined
Jun 14, 2012
Messages
428
lol.. walking through how to find that problem is like writing a 20 page book. Literally, there are dozens of reasons why scrubs can be slow.

What you are asking for is like a gamer asking why he can't get 60fps from his game. The number of possible causes are almost endless.

Oh yeah help me with my FPS too :p

I know my disks are crappy consumer level so I'm never going to get crazy speeds. I guess my 2 questions are how can I look at my CPU performance over time and during a scrub to see if the CPU is getting pegged and also are any of my disks causing slowness and maybe need to be replaced.
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,525
I'm crappy consumer level and I have no problems. I do almost 1GB/sec during scrubs on my pool. :)

It's not about the disk. In fact, its rarely about the disks. It's more about the overall system design and finding the bottleneck. There's tons of places it can be, both software and hardware.
 

titan_rw

Guru
Joined
Sep 1, 2012
Messages
586
I also have consumer drives and hit 1.1 - 1.2 GB/sec during scrub.

A fragmented zpool can slow down scrubs. I cut scrub times by more than half by removing 10% of total pool data one time.

I'd suggest starting a scrub manually, and investigating what the bottleneck is. Check "top -SH", and "gstat" and such.
 

Wolfeman0101

Patron
Joined
Jun 14, 2012
Messages
428
I'm crappy consumer level and I have no problems. I do almost 1GB/sec during scrubs on my pool. :)

It's not about the disk. In fact, its rarely about the disks. It's more about the overall system design and finding the bottleneck. There's tons of places it can be, both software and hardware.
Maybe it's the onboard controller and the CPU. I need to find a 6 port SATA PCI-X card. What CPU do you use?

I also have consumer drives and hit 1.1 - 1.2 GB/sec during scrub.

A fragmented zpool can slow down scrubs. I cut scrub times by more than half by removing 10% of total pool data one time.

I'd suggest starting a scrub manually, and investigating what the bottleneck is. Check "top -SH", and "gstat" and such.


Code:
last pid:  8614;  load averages:  0.14,  0.19,  0.21                        up 0+00:30:01  11:26:25
469 processes: 5 running, 443 sleeping, 21 waiting
CPU:  0.5% user,  0.0% nice,  4.4% system,  0.4% interrupt, 94.7% idle
Mem: 388M Active, 344M Inact, 1018M Wired, 1168K Cache, 94M Buf, 14G Free
ARC: 445M Total, 150M MFU, 260M MRU, 2096K Anon, 6174K Header, 27M Other
Swap: 12G Total, 12G Free
 
  PID USERNAME   PRI NICE   SIZE    RES STATE   C   TIME   WCPU COMMAND
   11 root       155 ki31     0K    64K CPU3    3  28:21 100.00% idle{idle: cpu3}
   11 root       155 ki31     0K    64K CPU2    2  28:53 96.09% idle{idle: cpu2}
   11 root       155 ki31     0K    64K RUN     0  28:27 95.75% idle{idle: cpu0}
   11 root       155 ki31     0K    64K CPU1    1  27:49 91.46% idle{idle: cpu1}
    0 root       -16    0     0K  2768K -       1   0:39  4.79% kernel{zio_read_intr_2}
    0 root       -16    0     0K  2768K -       3   0:39  4.69% kernel{zio_read_intr_1}
    0 root       -16    0     0K  2768K -       3   0:39  4.30% kernel{zio_read_intr_0}
   12 root       -88    -     0K   336K WAIT    1   0:16  1.27% intr{irq15: ata1}
 4526    816      21    0   302M   107M select  1   0:17  1.17% python2.7{python2.7}
 4526    816      21    0   302M   107M select  1   0:12  1.07% python2.7{python2.7}
   14 root        -8    -     0K    48K -       2   0:12  0.59% geom{g_down}
   12 root       -88    -     0K   336K WAIT    3   0:09  0.20% intr{irq22: ahci0}
  292 root        -8    -     0K    96K spa->s  1   0:07  0.10% zfskern{txg_thread_enter}
    0 root       -16    0     0K  2768K swapin  3   1:59  0.00% kernel{swapper}
 4526    816      20    0   302M   107M usem    3   0:21  0.00% python2.7{python2.7}
 4526    816      20    0   302M   107M usem    2   0:12  0.00% python2.7{python2.7}
 4526    816      20    0   302M   107M usem    0   0:09  0.00% python2.7{python2.7}
   14 root        -8    -     0K    48K -       2   0:07  0.00% geom{g_up}
    0 root       -92    0     0K  2768K -       0   0:03  0.00% kernel{dummynet}
 6758    972      52   15   265M 79000K piperd  3   0:03  0.00% python{python}
   12 root       -60    -     0K   336K WAIT    1   0:02  0.00% intr{swi4: clock}
 6802    972      52    0   207M 44836K piperd  1   0:02  0.00% python{python}
 2526 root        20    0   260M 94164K usem    2   0:01  0.00% python2.7{python2.7}
    5 root       -16    -     0K    16K ccb_sc  0   0:01  0.00% xpt_thrd
 4594    816      20    0   236M 81656K kqread  2   0:01  0.00% python2.7{python2.7}
 4594    816      20    0   236M 81656K select  3   0:01  0.00% python2.7{python2.7}
 4526    816      20    0   302M   107M select  1   0:01  0.00% python2.7{python2.7}
   15 root       -16    -     0K    16K -       1   0:01  0.00% yarrow


Code:
dT: 1.001s  w: 1.000s
L(q)  ops/s    r/s  kBps  ms/r    w/s  kBps  ms/w  %busy Name
    2    171    122  6793    6.0    47    444    0.2  53.7| ada0
    0      0      0      0    0.0      0      0    0.0    0.0| ada0p1
    2    171    122  6793    6.0    47    444    0.2  53.7| ada0p2
    2    170    120  7297    6.2    48    468    0.2  52.8| ada1
    2    162    115  7756    7.2    45    468    0.2  58.4| ada2
    2    152    104  7233    8.2    46    468    0.2  57.1| ada3
    2    136    86  7700  17.6    48    491    0.3  88.3| ada4
    2    139    91  7904  17.8    46    460    0.3  97.6| ada5
    0      0      0      0    0.0      0      0    0.0    0.0| ada1p1.eli
    2    171    122  6793    6.0    47    444    0.2  53.8| gptid/6dd242a6-cafb-11e1-915d-001517a03d00
    0      0      0      0    0.0      0      0    0.0    0.0| ada1p1
    2    170    120  7297    6.2    48    468    0.2  52.9| ada1p2
    0      0      0      0    0.0      0      0    0.0    0.0| ada2p1
    2    162    115  7756    7.2    45    468    0.2  58.4| ada2p2
    0      0      0      0    0.0      0      0    0.0    0.0| ada3p1
    2    152    104  7233    8.2    46    468    0.2  57.1| ada3p2
    0      0      0      0    0.0      0      0    0.0    0.0| ada4p1
    2    136    86  7700  17.6    48    491    0.3  88.4| ada4p2
    0      0      0      0    0.0      0      0    0.0    0.0| ada5p1
    2    139    91  7904  17.8    46    460    0.3  97.6| ada5p2
    0      0      0      0    0.0      0      0    0.0    0.0| ada2p1.eli
    2    170    120  7297    6.2    48    468    0.2  52.9| gptid/6e71f8fa-cafb-11e1-915d-001517a03d00
    0      0      0      0    0.0      0      0    0.0    0.0| ada3p1.eli
    2    162    115  7756    7.2    45    468    0.2  58.5| gptid/6f39b462-cafb-11e1-915d-001517a03d00
    0      0      0      0    0.0      0      0    0.0    0.0| ada4p1.eli
    2    152    104  7233    8.2    46    468    0.2  57.1| gptid/6feb82b0-cafb-11e1-915d-001517a03d00
    0      0      0      0    0.0      0      0    0.0    0.0| ada5p1.eli
    2    136    86  7700  17.6    48    491    0.3  88.4| gptid/709a11f8-cafb-11e1-915d-001517a03d00
    2    139    91  7904  17.9    46    460    0.3  97.6| gptid/713a3786-cafb-11e1-915d-001517a03d00
    0      0      0      0    0.0      0      0    0.0    0.0| da0
    0      0      0      0    0.0      0      0    0.0    0.0| da0s1
    0      0      0      0    0.0      0      0    0.0    0.0| da0s2
    0      0      0      0    0.0      0      0    0.0    0.0| da0s3
    0      0      0      0    0.0      0      0    0.0    0.0| da0s4
    0      0      0      0    0.0      0      0    0.0    0.0| da0s1a
    0      0      0      0    0.0      0      0    0.0    0.0| da0s2a
    0      0      0      0    0.0      0      0    0.0    0.0| ufs/FreeNASs3
    0      0      0      0    0.0      0      0    0.0    0.0| ada0p1.eli
    0      0      0      0    0.0      0      0    0.0    0.0| ufs/FreeNASs4
    0      0      0      0    0.0      0      0    0.0    0.0| ufs/FreeNASs1a
    0      0      0      0    0.0      0      0    0.0    0.0| ufsid/521c684590455604
    0      0      0      0    0.0      0      0    0.0    0.0| ufs/FreeNASs2a
    0      0      0      0    0.0      0      0    0.0    0.0| md0
    0      0      0      0    0.0      0      0    0.0    0.0| md1
    0      0      0      0    0.0      0      0    0.0    0.0| md2
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,525
I have an Intel Xeon e3-1230v2. Full fledged CPU.
 

titan_rw

Guru
Joined
Sep 1, 2012
Messages
586
Cpu usage looks fine.

It looks like ada4 and ada5 are holding back the pool. At least at that particular moment in time.
 

Wolfeman0101

Patron
Joined
Jun 14, 2012
Messages
428
Cpu usage looks fine.

It looks like ada4 and ada5 are holding back the pool. At least at that particular moment in time.

Yeah I think at one point I thought those 2 were an issue but I lost momentum on fixing it. I'm going to check them later once I'm home.
 

titan_rw

Guru
Joined
Sep 1, 2012
Messages
586
Not that the drives are necessarily bad. Just that at that moment, those 2 drives were being 'loaded' more than the others. I see that at times in my pools too. If it very consistently those two drives, it might be the drives. I suppose it could be data distribution on the drives too, depending on the pool layout.
 

Wolfeman0101

Patron
Joined
Jun 14, 2012
Messages
428
Not that the drives are necessarily bad. Just that at that moment, those 2 drives were being 'loaded' more than the others. I see that at times in my pools too. If it very consistently those two drives, it might be the drives. I suppose it could be data distribution on the drives too, depending on the pool layout.

I just know in the past those 2 drives have seemed to be a bottleneck as well. I wonder if the drive is bad or the cable or the controller.
 

Starpulkka

Contributor
Joined
Apr 9, 2013
Messages
179
My system:
AMD FX(tm)-4100 Quad-Core Processor
16GB DDR3 ECC RAM
Onboard controller

Code:
state: ONLINE
  scan: scrub repaired 0 in 6h1m with 0 errors on Sun Jan 26 06:01:58 2014
config:
 
        NAME                                            STATE    READ WRITE CKSUM
        *****                                          ONLINE      0    0    0
          raidz2-0                                      ONLINE      0    0    0
            gptid/5a0644da-b996-11e2-89c4-60a44c57d49e  ONLINE      0    0    0
            gptid/5a867495-b996-11e2-89c4-60a44c57d49e  ONLINE      0    0    0
            gptid/5bd3c295-b996-11e2-89c4-60a44c57d49e  ONLINE      0    0    0
            gptid/5c5e1e41-b996-11e2-89c4-60a44c57d49e  ONLINE      0    0    0
            gptid/5ce1d74d-b996-11e2-89c4-60a44c57d49e  ONLINE      0    0    0
            gptid/5d69fbe3-b996-11e2-89c4-60a44c57d49e  ONLINE      0    0    0
 
errors: No known data errors

Edit: oh and pool is 70%full
Do you have system folder on? If my pool would take over 7h i would be worried, very worried of my pool. But in your case your pool has always take that long time to scrub so nothing new failure have not yet happened.
Go to your motherboard bios and check have you enabled achi on sata 5 and 6 ports. looks like that 1-4 is on achi mode and 5-6 ports are not.

Edit: I know also some more speed options but its not worth now on your pool,(pool needs to be re create so i dont recommend it) perhaps next pool then you build it right. from the start.
 
Status
Not open for further replies.
Top