On Mon, Jan 28, 2013 at 8:55 PM, Andrey Korolyov <andrey@xxxxxxx> wrote: > On Mon, Jan 28, 2013 at 5:48 PM, Sam Lang <sam.lang@xxxxxxxxxxx> wrote: >> On Sun, Jan 27, 2013 at 2:52 PM, Andrey Korolyov <andrey@xxxxxxx> wrote: >> >>> Ahem. once on almost empty node same trace produced by qemu >>> process(which was actually pinned to the specific numa node), so seems >>> that`s generally is a some scheduler/mm bug, not directly related to >>> the osd processes. In other words, the less percentage of memory >>> actually is an RSS, the more is a probability of such allocation >>> failure. >> >> This might be a known bug in xen for your kernel? The xen users list >> might be able to help. >> -sam > > It is vanilla-3.4, I really wonder from where comes paravirt bits in the trace. Bug exposed only in 3.4 and really harmless, at least in ways I have tested that. Ceph-osd memory allocation behavior more likely to trigger those messages than most other applications in ``same'' conditions. -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
