SCSI errors resulting in down Object Storage Daemons (OSDs)
This document (7023562) is provided subject to the disclaimer at the end of this document.
Environment
Situation
2018-12-01T05:01:20.649519+01:00 server_name kernel: [40811.416245] sd 0:0:X:0: timing out command, waited 180s
2018-12-01T05:01:20.649528+01:00 server_name kernel: [40811.416279] sd 0:0:X:0: [sdX] tag#8 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
2018-12-01T05:01:20.649528+01:00 server_name kernel: [40811.416290] sd 0:0:X:0: [sdX] tag#8 Sense Key : Not Ready [current]
...
osd.xxx failed (root=xxxx,disktype=xxx,host=serverxxx) (xx reporters from different host after 100.964986 >= grace 100.287216)
we have enough reporters to mark osd.xxx down
map e422871 wrongly marked me down at ee422870
Resolution
Cause
Additional Information
# hdparm -B 255 -S 0 /dev/sd<X># tuned-adm off
# systemctl stop tuned.service
# hdparm -C /dev/sd<X>
# smartctl -a /dev/sd<X>
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7023562
- Creation Date: 05-Dec-2018
- Modified Date:03-Mar-2020
-
- SUSE Enterprise Storage
- SUSE Linux Enterprise Server
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com