On Thu, May 26, 2011 at 3:30 PM, Fyodor Ustinov <ufm@xxxxxx> wrote: > On 05/26/2011 08:37 PM, Gregory Farnum wrote: >> >> That means something in the messaging layers got a bit busted, and you >> should generally respond by filing bug reports.:) What version are >> you on right now? I think we fixed some issues with this a couple >> weeks ago. > > [72845.480649] libceph: get_reply unknown tid 475665 from osd0 > [72845.481518] libceph: get_reply unknown tid 475622 from osd0 > [72845.482140] libceph: get_reply unknown tid 475618 from osd0 > [72845.482725] libceph: get_reply unknown tid 475592 from osd0 > [72845.483164] libceph: get_reply unknown tid 475587 from osd0 > [72845.483753] libceph: get_reply unknown tid 475570 from osd0 > [72846.838239] libceph: get_reply unknown tid 475660 from osd4 > [72846.839034] libceph: get_reply unknown tid 475649 from osd4 > [72846.840702] libceph: get_reply unknown tid 475610 from osd4 > [72846.841548] libceph: get_reply unknown tid 475608 from osd4 > [72846.842243] libceph: get_reply unknown tid 475598 from osd4 > > > Ie it happens regularly. > > Messages on client (kernel) 2.6.29 > ceph - 0.28.1 Sage reminded me that this can also happen if the OSD configuration changes and the kernel client has to resend ops to a different OSD. Is your cluster changing while this happens? -- 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
