On 05/13/2011 06:28 AM, Goldwyn Rodrigues wrote:
> Hi Tristan,
>
> On Thu, May 12, 2011 at 7:36 AM, Tristan Ye<tristan...@oracle.com>  wrote:
>> Hi Goldwyn,
>>         The root cause was due to we didn't skip an existing hole somewhere 
>> when
>> punching a hole, to speak more accurately, the bug occurs at the time when we
>> removing a partial extent record(which also means the last extent record to
>> remove), as a result, the hole-punching code attempts to remove more than the
>> length of whole extent record, which leads to the failure of following
>> assert(fs/ocfs2/alloc.c):
>>
>> 5507         BUG_ON(cpos<  le32_to_cpu(rec->e_cpos) || trunc_range>  
>> rec_range);
>>
>>         Could you please make a verification against my coming patch, I 
>> passed xfs's
>> 013 testcase with the patch;-)
>>
> Did you post this patch? ... or am I being impatient?
>
Yes, he posted it.

http://oss.oracle.com/pipermail/ocfs2-devel/2011-May/008077.html

_______________________________________________
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
http://oss.oracle.com/mailman/listinfo/ocfs2-devel

Reply via email to