Re: OCFS2: ocfs2_read_blocks:285 ERROR: block 532737 had the JBDbit set while I was in lock_buffer!

[Richard Weinberger]

Am 03.09.2013 19:22, schrieb Mark Fasheh:
> On Tue, Sep 03, 2013 at 08:42:37AM +0200, Richard Weinberger wrote:
>> Hi!
>>
>> Am 03.09.2013 05:17, schrieb Jeff Liu:
>>> Hello,
>>>
>>> It seems like Sunil has fixed a similar issue against ocfs2-1.4
>>> several years ago:
>>> https://oss.oracle.com/git/?p=ocfs2-1.4.git;a=commitdiff_plain;h=2fd250839d0f5073af8d42e97f1db74beb621674;hp=e882faf84930431524f84598caea7d4e9a9529c5
>>> https://oss.oracle.com/git/?p=ocfs2-1.4.git;a=commitdiff_plain;h=eccff85213d4c2762f787d9e7cb1503042ba75b9;hp=edc147473ffd9c03790dc4502b893823f44a9ec4
>>>
>>> The old bug ticket for the discussion:
>>> https://oss.oracle.com/bugzilla/show_bug.cgi?id=1235
>>>
>>> This fix is specifically for ocfs2-1.4, but Mark once mentioned that
>>> the BUG() there can be removed if we have a good explanation for this
>>> sort of behavior, is it time to have it in mainline?
>>
>> Hmm, not fun.
>> In my case I'm not using NFS or any other network filesystem.
>> The OCFS2 is also used in local mode (no cluster).
>>
>> What really worries me is that this another proof that Oracles OCFS2 branch is out of sync with mainline.
> 
> Can you show me what branch you are talking about here?

https://oss.oracle.com/git/?p=ocfs2-1.4.git seems to contain fixes for years
which are not mainline.

Thanks,
//richard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/