现代的磁盘基本上都支持S.M.A.R.T.技术，关于S.M.A.R.T.， 维基百科的条文如下：

    S.M.A.R.T. (Self-Monitoring, Analysis, and Reporting Technology; sometimes written as SMART) is a monitoring system for computer hard disk drives to detect and report on various indicators of reliability, in the hope of anticipating failures.

    When a failure is anticipated by S.M.A.R.T., the drive should be replaced, and can sometimes be returned to the manufacturer, who can use these failed drives to discover where faults lie and how to prevent them from recurring on the next generation of hard disk drives.

    Smartmontool是sourceforge上的一个开源项目，可以对磁盘的S.M.A.R.T.进行提取和定期监控。Smartmontool包含两个工具： smartctl和smartd。

$sudo apt-get install smartmontools

    Smartctl用于提取和修改硬盘的某些属性和统计信息。Smartd则可以作为守护进程运行，定期收集信息，监控硬盘状态。在我的Thinkpad X200上运行smartctl的结果如下：

ningoo@ning:/sys/block/sda/queue$ sudo smartctl --all /dev/sda
smartctl 5.40 2010-03-16 r3077 [i686-pc-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:     FUJITSU MJA2320BH G2
Serial Number:    K95DTA52FWAA
Firmware Version: 0084001C
User Capacity:    320,072,933,376 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 3f
Local Time is:    Tue Mar 22 19:14:04 2011 CST
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:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
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: 		 (1009) 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: 	 ( 143) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   253   000    Old_age   Always       -       2
200 Multi_Zone_Error_Rate   0x000f   100   100   060    Pre-fail  Always       -       4364
203 Run_Out_Cancel          0x0002   100   100   000    Old_age   Always       -       1533219504675
240 Head_Flying_Hours       0x003e   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 1
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 1 occurred at disk power-on lifetime: 1222 hours (50 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 51 03 97 95 a6 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  00 08 01 01 00 00 00 ff      02:19:49.864  NOP [Reserved subcommand]
  60 08 00 90 95 a6 40 08      02:19:49.862  READ FPDMA QUEUED
  60 10 00 c8 3c a6 40 08      02:19:49.850  READ FPDMA QUEUED
  60 20 00 a8 3c a6 40 08      02:19:49.841  READ FPDMA QUEUED
  60 08 00 88 95 a6 40 08      02:19:49.833  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

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.

    对于使用了RAID卡的硬盘，还需要RAID卡的支持才能读取到磁盘的S.M.A.R.T.信息，同时intel的SSD也将自身的一些健康指标如磨损率等写入了S.M.A.R.T.信息，于是我们就能通过smartctl来获取安装了RAID卡的SSD的寿命等关键指标了。有了这些指标，可以提前预知到SSD的健康状况，对于SSD单点有写入极限这个担忧，就可以稍微降低那么一点，在生产环境中使用也就更有谱了。具体的用法，之前褚霸和B2B的DBA都有写过blog介绍，这里就不展开了。

    值得一提的是，SSD的磨损率一般通过E9(233)来获取，也就是Media_Wearout_Indicator指标，是0~100的值，精度还是比较粗的，B2B这边线上用了很久，写入了40TB的测试数据，这个值也还是比较高(99，只少了一滴血，这个boss很难打啊^_^)。如果需要更细粒度的数据，上次Intel的人过来交流的时候，说可以取E2(226 Timed Workload Indicator)，E3(227 Timed Workload Read Ratio)，E4((228 Timed Workload Timer)的值来做更高精度的计算，在开始压力测试前，先将对应的E2/E3/E4的值清零

smartctl -t vendor, 0x40 -a /dev/hdx

    然后执行一次测试(至少60分钟)，得到E2 = 22， 则该次测试的磨损率为 22 / 1024 / 100= 0.021%(E9的一点血是E2的100点血，也就是说E2的精度比E9高100倍，所以可以在较短时间的测试中看到其变化)。E3 =99 说明读写比例为 99%。该次测试的时间则为E4 = 981分钟，通过计算可以得到该SSD在这样的工作压力下的寿命为E4*1024*100/E2/1440/365 = 8.68年(一年按365天计算)。当然，这个结果是假设这些E2/E3/E4/E9的值都是线性变化的前提下得出的，如果像某些手机的电池指示一样，第一格电可以用一天，最后一格电只能用一个小时，那么这些估算就都是浮云。欲知后事如何，只能等某块SSD用到寿命正常终止，再回头来分析这些指标是否靠谱了。

建议继续学习：

1. Mysql监控指南    (阅读：19863)
2. 批量添加主机到cacti+nagios的监控报警系统中    (阅读：13338)
3. 我常用的主机监控shell脚本    (阅读：11568)
4. 7 天打造前端性能监控系统    (阅读：10234)
5. 如何监控HP服务器硬件状态    (阅读：9163)
6. Cacti 添加 Nginx 监控    (阅读：8985)
7. Linux下三种常用的流量监控软件对比    (阅读：8746)
8. Cacti 添加 Memcached 监控    (阅读：8184)
9. 提升磁盘IO性能的几个技巧    (阅读：7617)
10. Cacti 添加 Apache 监控    (阅读：7644)