Bug 1682967

Summary:	[RHCS3] Ceph doesn't change OSD status when osd daemon faces read error
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Keisuke Matsuzaki <k-matsuzaki>
Component:	RADOS	Assignee:	David Zafman <dzafman>
Status:	CLOSED ERRATA	QA Contact:	Pawan <pdhiran>
Severity:	medium	Docs Contact:	Aron Gunn <agunn>
Priority:	medium
Version:	3.1	CC:	agunn, dzafman, gfarnum, hfukumot, jdurgin, kchai, k-matsuzaki, knoha, nojha, pdhiran, redhat-bz, tserlin, ykawada
Target Milestone:	z2
Target Release:	4.1
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	ceph-14.2.8-100.el8cp, ceph-14.2.8-100.el7cp	Doc Type:	Enhancement
Doc Text:	.The storage cluster status changes when a Ceph OSD encounters an I/O error With this release, the Ceph Monitor now has a `mon_osd_warn_num_repaired` option, which is set to `10` by default. If any Ceph OSD has repaired more than this many I/O errors in stored data, a `OSD_TOO_MANY_REPAIRS` health warning status is generated. To clear this warning, the new `clear_shards_repaired` option has been added to the `ceph tell` command. For example: [source,subs="verbatim,quotes"] ---- ceph tell osd._NUMBER_ clear_shards_repaired [_COUNT_] ---- By default, the `clear_shards_repaired` option sets the repair count to `0`. To be warned again if additional Ceph OSD repairs are performed, you can specify the value of the `mon_osd_warn_num_repaired` option.	Story Points:	---
Clone Of:
Clones:	1855470 (view as bug list)		Environment:
Last Closed:	2020-09-30 17:24:49 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1658754, 1816167, 1855470

Comment 39 errata-xmlrpc 2020-09-30 17:24:49 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Red Hat Ceph Storage 4.1 Bug Fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4144