l’un des disques d’un de mes serveurs a commencé à générer des erreurs d’écriture (contrôle ECC) … .
Le smart de ce dernier indiquant tout de même son bon état de fonctionnement grâce à l’allocation de secteur de secours (le raid étant toujours aussi en bon marche).
Naturellement, le Load du serveur est donc monté en flèche.
Il est passé de 0,5-0,8 à 5 en moyenne
=> le service était toujours accessible avec un petit temps de Latence de connexion sur le webmail
Puis de temps à autre le Load est monté à 10-12
=> l’authentification devient difficile et la consultation des mails avec de fort latence.
Et en pointe, avec le Load de 18-20
=> le service est devenu down, et des messages d’erreurs d’écriture du cache ext4
=> Impossible de gérer les services bluemind, et la queue du Postfix se charge des divers mails envoyés depuis les Thunderbird et ceux en arrivé …
======
Donc un serveur avec un Load de 10 est déjà inconcevable en terme d’exploitation …
BlueMind sait très bien vivre dans cette enfer …
root@terrasse:~# smartctl -a -d ata /dev/sdb
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-2.6.32-26-pve] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Device Model: TOSHIBA DT01ACA200
Serial Number: 63TLUGXKS
LU WWN Device Id: 5 000039 ff3d6a5d6
Firmware Version: MX4OABB0
User Capacity: 2,000,398,934,016 bytes [2.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Tue Sep 2 01:49:12 2014 CEST
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: (0x82) Offline data collection activity
was completed without error.
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: (14918) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No 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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 249) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control 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 0x000b 100 100 016 Pre-fail Always - 0
2 Throughput_Performance 0x0005 140 140 054 Pre-fail Offline - 67
3 Spin_Up_Time 0x0007 130 130 024 Pre-fail Always - 296 (Average 285)
4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 26
5 Reallocated_Sector_Ct 0x0033 040 040 005 Pre-fail Always - 1241
7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 124 124 020 Pre-fail Offline - 33
9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 5363
10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 26
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 167
193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 167
194 Temperature_Celsius 0x0002 187 187 000 Old_age Always - 32 (Min/Max 17/40)
196 Reallocated_Event_Count 0x0032 008 008 000 Old_age Always - 1830
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 72
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 18 (device log contains only the most recent five errors)
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 18 occurred at disk power-on lifetime: 5291 hours (220 days + 11 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
-- -- -- -- -- -- --
40 51 08 00 89 8c 08 Error: UNC at LBA = 0x088c8900 = 143427840
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 08 00 89 8c 40 00 5d+14:17:06.724 READ FPDMA QUEUED
61 08 00 80 5f e0 40 00 5d+14:17:06.724 WRITE FPDMA QUEUED
ea 00 00 00 00 00 a0 00 5d+14:17:06.710 FLUSH CACHE EXT
60 08 10 00 89 4c 40 00 5d+14:17:06.686 READ FPDMA QUEUED
60 78 08 90 2f 00 40 00 5d+14:17:06.686 READ FPDMA QUEUED
Error 17 occurred at disk power-on lifetime: 4830 hours (201 days + 6 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
-- -- -- -- -- -- --
40 51 88 58 f2 56 05 Error: UNC at LBA = 0x0556f258 = 89584216
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 10 80 a6 75 40 00 5d+02:18:24.981 READ FPDMA QUEUED
60 c0 08 c0 a5 75 40 00 5d+02:18:24.981 READ FPDMA QUEUED
60 c0 00 20 f2 56 40 00 5d+02:18:24.940 READ FPDMA QUEUED
60 60 00 20 a5 75 40 00 5d+02:18:24.907 READ FPDMA QUEUED
60 50 00 60 bf ec 40 00 5d+02:18:24.873 READ FPDMA QUEUED
Error 16 occurred at disk power-on lifetime: 4830 hours (201 days + 6 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
-- -- -- -- -- -- --
40 51 a8 18 f6 56 05 Error: UNC at LBA = 0x0556f618 = 89585176
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 18 c0 f5 56 40 00 5d+02:18:07.007 READ FPDMA QUEUED
60 40 08 40 f5 56 40 00 5d+02:18:07.007 READ FPDMA QUEUED
60 00 00 20 ed 56 40 00 5d+02:18:05.795 READ FPDMA QUEUED
60 40 10 e0 ec 56 40 00 5d+02:18:05.467 READ FPDMA QUEUED
60 60 08 60 ec 56 40 00 5d+02:18:05.467 READ FPDMA QUEUED
Error 15 occurred at disk power-on lifetime: 4650 hours (193 days + 18 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
-- -- -- -- -- -- --
40 51 50 30 b5 01 02 Error: UNC at LBA = 0x0201b530 = 33666352
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 80 88 80 ba 01 40 00 3d+19:54:37.720 READ FPDMA QUEUED
60 80 80 00 ba 01 40 00 3d+19:54:37.720 READ FPDMA QUEUED
60 80 f0 80 b9 01 40 00 3d+19:54:37.702 READ FPDMA QUEUED
60 80 78 00 b9 01 40 00 3d+19:54:37.702 READ FPDMA QUEUED
60 80 08 80 b8 01 40 00 3d+19:54:37.701 READ FPDMA QUEUED
Error 14 occurred at disk power-on lifetime: 4562 hours (190 days + 2 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
-- -- -- -- -- -- --
40 51 e8 00 fe db 02 Error: WP at LBA = 0x02dbfe00 = 47971840
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 00 58 00 58 63 40 00 04:21:12.942 WRITE FPDMA QUEUED
61 00 50 00 54 63 40 00 04:21:12.942 WRITE FPDMA QUEUED
61 00 48 00 50 63 40 00 04:21:12.942 WRITE FPDMA QUEUED
61 00 38 00 4c 63 40 00 04:21:12.940 WRITE FPDMA QUEUED
61 00 28 00 48 63 40 00 04:21:12.938 WRITE FPDMA QUEUED
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% 4541 -
# 2 Short offline Completed without error 00% 4537 -
# 3 Short offline Completed without error 00% 4534 -
# 4 Short offline Completed without error 00% 4533 -
# 5 Short offline Completed without error 00% 4531 -
# 6 Short offline Completed without error 00% 4530 -
# 7 Short offline Completed without error 00% 4511 -
# 8 Short offline Completed without error 00% 4510 -
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.
root@terrasse:~#
C’est le dsque d’un serveur physique, virtualisant plusieurs serveurs dont un BlueMind …
Mais j’ai déjà eu cela sur mon avant dernier serveur bluemind physique
Ce cas de figure peut aussi se produire avec les montages NFS utilisés pour la sauvegarde et/ou l’archivage par exemple.
En cas de disparition du serveur NFS correspondant, la charge du serveur peut très rapidement monter lors des tentatives d’accès aux arborescences correspondantes.
En cas de doute sur la fiabilité du serveur NFS, nous vous conseillons de faire les montages NFS avec l’option soft.
