Hi Eugen, my hypothesis is that these recursive counters are uncritical and, in fact, updated when the dir/file is modified/accessed. Attributes like ceph.dir.rbytes will show somewhat incorrect values, but these are approximate anyway (updates are propagated asynchronously).
It would just be great to have confirmation or a "no, its critical". There was something similar when a read error occurred with "fast read" enabled. It also logged an "[ERR]" event even though it is expected to happen every now and then. In recent releases this was downgraded to a "[WRN]" event to reduce unwarranted panic amongst admins. My suspicion is that we have here a similar situation, these messages might better be "[WRN]" or even just "[DBG]". By the way, I have these on more than one rank, so it is probably not a fall-out of the recent recovery efforts. Best regards, ================= Frank Schilder AIT Risø Campus Bygning 109, rum S14 _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-le...@ceph.io
