Interesting from this situation is:
Feb 21 21:44:46 ceph-mgr: 2022-02-21 20:44:46.913 7f70896f9700 -1 os_release_parse - failed to open /etc/os-release: (5) Input/output error
Feb 21 21:44:46 ceph-mgr: 2022-02-21 20:44:46.913 7f70896f9700 -1 distro_detect - /etc/os-release is required
Feb 21 21:44:46 ceph-mgr: 2022-02-21 20:44:46.913 7f70896f9700 -1 os_release_parse - failed to open /etc/os-release: (5) Input/output error
Feb 21 21:44:46 ceph-mgr: 2022-02-21 20:44:46.913 7f70896f9700 -1 distro_detect - /etc/os-release is required
Feb 21 21:44:46 ceph-mgr: 2022-02-21 20:44:46.913 7f70896f9700 -1 distro_detect - can't detect distro
Feb 21 21:44:46 ceph-mgr: 2022-02-21 20:44:46.913 7f70896f9700 -1 distro_detect - can't detect distro_description
Feb 21 21:44:46 ceph-mgr: 2022-02-21 20:44:46.913 7f70896f9700 -1 distro_detect - can't detect distro
Feb 21 21:44:46 ceph-mgr: 2022-02-21 20:44:46.913 7f70896f9700 -1 distro_detect - can't detect distro_description
Why does this mgr even try to open this? It looks like this mgr is ok, so why does it want to open this file in a loop? Why not just once at startup. I do not think the distro file will change that much. This can only make it worse.
[@]# ceph -s
cluster:
id:
health: HEALTH_WARN
1 clients failing to respond to cache pressure
noout,noscrub,nodeep-scrub flag(s) set
2 pool(s) have no replicas configured
1/3 mons down, quorum a,b
services:
mon: 3 daemons, quorum a,b (age 7h), out of quorum: c
mgr: a(active, since 10w), standbys: b, c
mds: cephfs:1 {0=a=up:active} 1 up:standby
osd: 42 osds: 42 up (since 3w), 42 in (since 4M)
flags noout,noscrub,nodeep-scrub
rgw: 1 daemon active (rgw1)
rgw-nfs: 1 daemon active (rgwnfs1)
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
