linux-xfs在dmesg上失败并出现错误

我在使用xfs的 linux机器上有一个奇怪的错误,我不知道如何调试和修复它.

以下是dmesg的摘录：

Info fld=0x17
end_request: I/O error,dev sde,sector 34412208504
sd 7:0:0:0: SCSI error: return code = 0x08000002
sde: Current: sense key: Aborted Command
   <<vendor>> ASC=0xc0 ASCQ=0x23ASC=0xc0 ASCQ=0x23

Info fld=0x17
end_request: I/O error,sector 35840057200
sd 7:0:0:0: SCSI error: return code = 0x08000002
sde: Current: sense key: Aborted Command
   <<vendor>> ASC=0xc0 ASCQ=0x23ASC=0xc0 ASCQ=0x23

Info fld=0x17
end_request: I/O error,sector 35799212408
sd 7:0:0:0: SCSI error: return code = 0x08000002
sde: Current: sense key: Aborted Command
   <<vendor>> ASC=0xc0 ASCQ=0x23ASC=0xc0 ASCQ=0x23

Info fld=0x17
end_request: I/O error,sector 39444095352
sd 7:0:0:1: SCSI error: return code = 0x08000002
sdf: Current: sense key: Aborted Command
   <<vendor>> ASC=0xc0 ASCQ=0x23ASC=0xc0 ASCQ=0x23

Info fld=0x17
end_request: I/O error,dev sdf,sector 32974487928
device-mapper: multipath: Failing path 8:80.
sd 7:0:0:1: SCSI error: return code = 0x08000002
sdf: Current: sense key: Aborted Command
   <<vendor>> ASC=0xc0 ASCQ=0x23ASC=0xc0 ASCQ=0x23

Info fld=0x17
end_request: I/O error,sector 32973734264
sd 7:0:0:1: SCSI error: return code = 0x08000002
sdf: Current: sense key: Aborted Command
   <<vendor>> ASC=0xc0 ASCQ=0x23ASC=0xc0 ASCQ=0x23

Info fld=0x17
end_request: I/O error,sector 22213009752
sd 7:0:0:1: SCSI error: return code = 0x08000002
sdf: Current: sense key: Aborted Command
   <<vendor>> ASC=0xc0 ASCQ=0x23ASC=0xc0 ASCQ=0x23

Info fld=0x17
end_request: I/O error,sector 32940065144
sd 7:0:0:1: SCSI error: return code = 0x08000002
sdf: Current: sense key: Aborted Command
   <<vendor>> ASC=0xc0 ASCQ=0x23ASC=0xc0 ASCQ=0x23

Info fld=0x17
end_request: I/O error,sector 32974552944
sd 7:0:0:1: SCSI error: return code = 0x08000002
sdf: Current: sense key: Aborted Command
   <<vendor>> ASC=0xc0 ASCQ=0x23ASC=0xc0 ASCQ=0x23

Info fld=0x17
end_request: I/O error,sector 17956282744
Buffer I/O error on device dm-3,logical block 9666270717
lost page write due to I/O error on dm-3
I/O error in filesystem ("dm-3") Meta-data dev dm-3 block 0xe7ffb01c2       ("xlog_iodone") error 5 buf count 12800
Buffer I/O error on device dm-3,logical block 4028959741
lost page write due to I/O error on dm-3
xfs_force_shutdown(dm-3,0x2) called from line 956 of file fs/xfs/xfs_log.c.  Return address = 0xffffffff883bec58
Filesystem "dm-3": Log I/O Error Detected.  Shutting down filesystem: dm-3
Please umount the filesystem,and rectify the problem(s)

我怎么调试这个？

谢谢.

解决方法

我知道这是一个非常古老的帖子,但由于答案不正确,我认为未来的访问者发布正确的答案会很有用…

OP报告的错误消息本身与XFS无关,而是驱动器/电缆坏的结果.检查错误条目：

end_request: I/O error,sector 39444095352

系统无法在LBA地址39444095352处检索位于sde上的数据.这通常意味着磁盘上存在坏块.

sd 7:0:0:1: SCSI error: return code = 0x

end_request: I/O error,sector 39444095352

002
sdf: Current: sense key: Aborted Command
vendor ASC=0xc0 ASCQ=0x23ASC=0xc0 ASCQ=0x23

SCSI命令由于超时(由坏块引起)而中止,并且磁盘返回特定的供应商代码,更详细地解释错误.

发出smartctl –all显示各种内部磁盘计数器.具有ID 5(Reallocated_Sector_Ct),197(Current_Pending_Sector)和198(Offline_Uncorrectable)的属性是特别感兴趣的,因为它们显示磁盘块不可读/重新映射的情况.

在这种情况下你能做什么？最安全且最受欢迎的方法是将整个可读内容备份到另一个安全磁盘(可能使用弹性磁盘错误的东西,如ddrescue)

如果不可能采用这种方法,那么仍有两种可能性：

>使用实时发行版重新启动并发出坏块-n< dev> (here for man page)：它将启动非破坏性读/写测试,该测试应触发磁盘坏块重新映射过程
>手动覆盖受影响的坏块,发出与dd类似的东西= = dev / zero of = / dev / sde bs = 512 count = 1 seek = 39444095352

请注意,上述两种方法(尤其是第二种方法)将导致数据丢失,因为受影响的不可读扇区将被覆盖.

恢复/覆盖完成后,您应该运行完整的文件系统检查,在这种情况下发出xfs_repair / dev / sde