On Fri, Sep 27, 2019 at 8:50 AM Sridhar Seshasayee <sseshasa@xxxxxxxxxx> wrote: > This PR https://github.com/ceph/ceph/pull/30285 introduced the slow ops fix recently. > > I haven't been able to reproduce the issue that you hit so far. Can you please let me > know the "--subset" you used for your run (pdonnell-2019-09-14_22:39:31-fs-master-distro-basic-smithi) > on the fs suite? teuthology-suite -p 49 -m smithi --ceph master --ceph-repo https://github.com/ceph/ceph --suite-repo https://github.com/ceph/ceph -S 79847358cf39f1d68c1efdde2eaa215ffb0496f2 --filter '{begin.yaml ceph-thrash/mon.yaml clusters/1-mds-1-client-coloc.yaml conf/{client.yaml mds.yaml mon.yaml osd.yaml} mount/fuse.yaml msgr-failures/osd-mds-delay.yaml objectstore-ec/bluestore-comp-ec-root.yaml overrides/{frag_enable.yaml whitelist_health.yaml whitelist_wrongly_marked_down.yaml} supported-random-distros$/{centos_7.yaml} tasks/cfuse_workunit_suites_fsstress.yaml}' --suite fs --num 10 http://pulpito.ceph.com/pdonnell-2019-10-01_03:28:40-fs-master-distro-basic-smithi/ That was with 10 runs of the same job so it's not trivially reproduced. > Just to clarify, before the fix, even if there were legitimate slow ops on 1 or more osds, > they would not get reported as part of the "ceph -s" output. The above fix just addressed the issue > of the slow ops not getting shown as part of "ceph -s" command if were any reported. Might not be related then. -- Patrick Donnelly, Ph.D. He / Him / His Senior Software Engineer Red Hat Sunnyvale, CA GPG: 19F28A586F808C2402351B93C3301A3E258DD79D _______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
