[technique] I/O Error sur un volume de 788Go

[manu chez Z]

Bonjour

Depuis quelques jours nous avons des ennuis avec la machine picbackup 
hébergée par tetaneutral: les sauvegardes se font partiellement. Dans le 
syslog j'ai des messages comme ça:

*Feb 19 03:17:49 picbackup kernel: [9090496.299702] sd 2:0:0:1: [sdb] 
tag#29 abort
Feb 19 03:17:49 picbackup kernel: [9090496.302511] sd 2:0:0:1: [sdb] 
tag#29 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK
Feb 19 03:17:49 picbackup kernel: [9090496.302513] sd 2:0:0:1: [sdb] 
tag#29 CDB: Read(10) 28 00 4c 40 1b f8 00 00 08 00
Feb 19 03:17:49 picbackup kernel: [9090496.302515] blk_update_request: 
I/O error, dev sdb, sector 1279269880
Feb 19 03:17:49 picbackup kernel: [9090496.306412] sd 2:0:0:1: [sdb] 
tag#28 abort
Feb 19 03:17:49 picbackup kernel: [9090496.306460] sd 2:0:0:1: [sdb] 
tag#28 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK
Feb 19 03:17:49 picbackup kernel: [9090496.306462] sd 2:0:0:1: [sdb] 
tag#28 CDB: Read(10) 28 00 4c 40 1b f0 00 00 08 00
Feb 19 03:17:49 picbackup kernel: [9090496.306464] blk_update_request: 
I/O error, dev sdb, sector 1279269872
Feb 19 03:17:49 picbackup kernel: [9090496.311759] sd 2:0:0:1: [sdb] 
tag#27 abort
Feb 19 03:17:49 picbackup kernel: [9090496.311800] sd 2:0:0:1: [sdb] 
tag#27 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK
Feb 19 03:17:49 picbackup kernel: [9090496.311802] sd 2:0:0:1: [sdb] 
tag#27 CDB: Read(10) 28 00 4c 40 1b e8 00 00 08 00
Feb 19 03:17:49 picbackup kernel: [9090496.311803] blk_update_request: 
I/O error, dev sdb, sector 1279269864
Feb 19 03:17:49 picbackup kernel: [9090496.317959] sd 2:0:0:1: [sdb] 
tag#26 abort
Feb 19 03:17:49 picbackup kernel: [9090496.318003] sd 2:0:0:1: [sdb] 
tag#26 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK
Feb 19 03:17:49 picbackup kernel: [9090496.318019] sd 2:0:0:1: [sdb] 
tag#26 CDB: Read(10) 28 00 4c 40 1b e0 00 00 08 00
Feb 19 03:17:49 picbackup kernel: [9090496.318020] blk_update_request: 
I/O error, dev sdb, sector 1279269856
Feb 19 03:17:49 picbackup kernel: [9090496.323346] sd 2:0:0:1: [sdb] 
tag#25 abort
Feb 19 03:17:49 picbackup kernel: [9090496.323779] sd 2:0:0:1: [sdb] 
tag#25 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK
Feb 19 03:17:49 picbackup kernel: [9090496.323782] sd 2:0:0:1: [sdb] 
tag#25 CDB: Read(10) 28 00 4c 40 1b d8 00 00 08 00
Feb 19 03:17:49 picbackup kernel: [9090496.323783] blk_update_request: 
I/O error, dev sdb, sector 1279269848
Feb 19 03:17:56 picbackup kernel: [9090503.591304] sd 2:0:0:1: [sdb] 
tag#95 abort
Feb 19 03:17:58 picbackup kernel: [9090505.443884] sd 2:0:0:1: [sdb] 
tag#93 abort
Feb 19 03:17:58 picbackup kernel: [9090505.443922] sd 2:0:0:1: [sdb] 
tag#59 abort
Feb 19 03:17:58 picbackup kernel: [9090505.443942] sd 2:0:0:1: [sdb] 
tag#60 abort
Feb 19 03:36:35 picbackup kernel: [9091622.138159] sd 2:0:0:1: [sdb] 
tag#0 abort
Feb 19 03:36:38 picbackup kernel: [9091625.802056] sd 2:0:0:1: [sdb] 
tag#1 abort
Feb 19 03:42:14 picbackup kernel: [9091961.558076] sd 2:0:0:1: [sdb] 
tag#49 abort
Feb 19 03:42:19 picbackup kernel: [9091966.886413] sd 2:0:0:1: [sdb] 
tag#48 abort
Feb 19 03:42:19 picbackup kernel: [9091966.886456] sd 2:0:0:1: [sdb] 
tag#47 abort
Feb 19 03:42:19 picbackup kernel: [9091966.886529] sd 2:0:0:1: [sdb] 
tag#46 abort
Feb 19 03:42:19 picbackup kernel: [9091966.886567] sd 2:0:0:1: [sdb] 
tag#45 abort
Feb 19 03:42:19 picbackup kernel: [9091966.886580] sd 2:0:0:1: [sdb] 
tag#39 abort
Feb 19 03:42:19 picbackup kernel: [9091966.886593] sd 2:0:0:1: [sdb] 
tag#38 abort
Feb 19 03:42:19 picbackup kernel: [9091966.886623] sd 2:0:0:1: [sdb] 
tag#4 abort
Feb 19 03:42:19 picbackup kernel: [9091966.886652] sd 2:0:0:1: [sdb] 
tag#3 abort
Feb 19 03:42:19 picbackup kernel: [9091966.886710] sd 2:0:0:1: [sdb] 
tag#52 abort
Feb 19 03:42:19 picbackup kernel: [9091966.918025] sd 2:0:0:1: [sdb] 
tag#51 abort
Feb 19 03:42:19 picbackup kernel: [9091966.918053] sd 2:0:0:1: [sdb] 
tag#50 abort
*

Je pense exécuter cette commande:

*fsck -y /dev/sdb >FSCK.LOG 2>&1*

Est-ce que vous pensez que c'est une bonne idée, ou y a-t-il autre chose 
à faire ?

Merci d'avance pour vos conseils,

Emmanuel

-------------- section suivante --------------
Une pièce jointe HTML a été nettoyée...
URL: <http://lists.tetaneutral.net/pipermail/technique/attachments/20200219/06629c96/attachment.htm>