On Tue, Mar 25, 2014 at 9:03 PM, Alex Elder <[email protected]> wrote:
> On 03/25/2014 01:53 PM, Olivier Bonvalet wrote:
>> Le mardi 25 mars 2014 à 12:43 -0500, Alex Elder a écrit :
>>> Please try applying this, on top of the previous patch.
>>> If you can then reproduce the problem we'll have a bunch
>>> of new information about the particular request that's
>>> leading to the failure. That might tell us what more we
>>> can do to find the root cause. Thank you.
>>>
>>> -Alex
>>>
>>> PS I hope my mailer doesn't botch the long lines. It might.
>>>
>>
>> Here the execution will continue, no more kernel panic after this
>> debugging display. Is it wanted ?
>
>
> I guess it should panic. I'm glad you mentioned this.
Just in case, if you haven't done it already: stick rbd_assert(0);
after the last printk in that if statement, so it looks like this:
if (which != img_request->next_completion) {
printk("%s: bad image object request information:\n", __func__);
printk("obj_request %p\n", obj_request);
printk(" ->object_name <%s>\n", obj_request->object_name);
...
printk("img_request %p\n", img_request);
printk(" ->snap 0x%016llx\n", img_request->snap_id);
...
printk(" ->result %d\n", img_request->result);
rbd_assert(0);
}
Thanks,
Ilya
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
