[Ocfs2-users] dlm_lockres_release:507 ERROR: Resource W0000000000000001b027d69b591f15 not on the Tracking list

[Sunil Mushran]

On 09/29/2011 08:56 AM, Herman L wrote:
>> On Wednesday, September 21, 2011 4:00 PM, Sunil Mushran wrote:
>> On 09/21/2011 12:37 PM, Herman L wrote:
>>>>> On 09/19/2011 08:35 AM, Herman L wrote:
>>>>> Hi all,
>>>>>
>>>>> Got a couple of these messages recently, but I don't know what they mean.  Can anyone let me know if I need to panic?  I'm using OCFS2 compiled from the kernel source of RHEL 6.0's 2.6.32-71.18.2.el6.x86_64.
>>>>>
>>>>> Sep 19 08:07:15 server-1 kernel: [3892420.222240] (10387,12):dlm_lockres_release:507 ERROR: Resource W0000000000000001b027d69b591f15 not on the Tracking list
>>>>> Sep 19 08:07:15 server-1 kernel: [3892420.398194] lockres: W0000000000000001b027d69b591f1, owner=1, state=0
>>>>> Sep 19 08:07:15 server-1 kernel: [3892420.398195]  last used: 8197071325, refcnt: 0, on purge list: no
>>>>> Sep 19 08:07:15 server-1 kernel: [3892420.398197]  on dirty list: no, on reco list: no, migrating pending: no
>>>>> Sep 19 08:07:15 server-1 kernel: [3892420.398198]  inflight locks: 0, asts reserved: 0
>>>>> Sep 19 08:07:15 server-1 kernel: [3892420.398199]  refmap nodes: [ ], inflight=0
>>>>> Sep 19 08:07:15 server-1 kernel: [3892420.398200]  granted queue:
>>>>> Sep 19 08:07:15 server-1 kernel: [3892420.398200]  converting queue:
>>>>> Sep 19 08:07:15 server-1 kernel: [3892420.398201]  blocked queue:
>>>>>
>>>>> Thanks!
>>>>> Herman
>>>> From: Sunil Mushran
>>>> To: Herman L
>>>> Sent: Monday, September 19, 2011 12:57 PM
>>>> Subject: Re: [Ocfs2-users] dlm_lockres_release:507 ERROR: Resource W0000000000000001b027d69b591f15 not on the Tracking list
>>>>
>>>>      I've no idea of the state of the source that you are using. The message
>>>>      is a warning indicating a race. While it probably did not affect the functioning,
>>>>      there is no guarantee that that would be the case the next time around.
>>>>
>>>>      The closest relevant patch is over 2 years old.
>>>> http://oss.oracle.com/git/?p=smushran/linux-2.6.git;a=commit;h=b0d4f817ba5de8adb875ace594554a96d7737710
>>> Thanks Sunil for responding.  I know you can't easily support my setup, but anyways I checked the sources.
>>>
>>> Looks like the patch you mention is in the sources I compiled from ( RHEL6.0 kernel-2.6.32-71.24.1.el6.src.rpm ), so I guess the source of the problem is elsewhere.
>>>
>>> The fs/ocfs2 directory from the RHEL6 sources I compiled from is almost exactly the same as the mainline 2.6.32 kernel, except
>>> 1) It looks like they implemented the changes in aops.c from the "cleanup blockdev_direct_IO locking" patch that's in 2.6.33.
>>> 2) In journal.c, they rename ocfs2_commit_trigger to ocfs2_frozen_trigger, which seems to be from 2.6.35.
>>> 3) In cluster/masklog.c they add a "const" to the mlog_attr_ops declaration
>>> 4) And in quota.h, they are missing "#define QFMT_OCFS2 3"
>>>
>>> Not sure if that helps any, but thanks in any case!
>> All those changes are ok. And unrelated. This is a new one.
>
> Sorry, I think I accidentally wrote a message with only the quoted block... oops.  Sorry.
>
>
> Sunil, are you able to and interested in looking at this issue?  If so, is there any information that I can provide that might help?  Fortunately, after those few initial days of daily errors, it seems to have stopped for now.  But of course, I'm still worried about this.
>

http://oss.oracle.com/~smushran/0001-ocfs2-dlm-Use-dlm-track_lock-when-adding-resource-to.patch

This should fix it. But do note that the patch is untested.