All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sunil Mushran <sunil.mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] remove lockres from purge list when we are getting it for creating lock
Date: Thu, 09 Jun 2011 17:43:17 -0700	[thread overview]
Message-ID: <4DF168A5.2050601@oracle.com> (raw)
In-Reply-To: <20110610003250.GA3437@laptop.jp.oracle.com>

On 06/09/2011 05:32 PM, Wengang Wang wrote:
> On 11-06-09 11:34, Sunil Mushran wrote:
>> Different issue. That patch plugged a hole when the master was remote.
>> In this case the master is local.
> I think in my case, the master is remote too. The phenomemon is local
> node keeps sending messages infinitely to the master which is dead.
>> In this case, the window is very tiny as we not only need the recovery to
>> kick-in in the that window, we also need the lockres to be moved to the
>> purgelist in that window.
>>
>> But it just so happens that ovm via userdlm hits createlock a lot making
>> this issue more likely to trigger than with the fs.
> Yes, OVM create the lock in every 5 seconds via dlmfs.

Do you have a reproducible testcase? If not, work on that. That would
be most helpful in fixing this issue.

Right now I am also working on a problem in this area. Not the same
though. I can work on this issue too. But I need a testcase.

  reply	other threads:[~2011-06-10  0:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-08 10:04 [Ocfs2-devel] [PATCH] remove lockres from purge list when we are getting it for creating lock Wengang Wang
2011-06-09  5:17 ` Srinivas Eeda
2011-06-09  6:40   ` Wengang Wang
2011-06-09  7:43     ` Srinivas Eeda
2011-06-09  8:10       ` Wengang Wang
2011-06-09 18:34   ` Sunil Mushran
2011-06-10  0:32     ` Wengang Wang
2011-06-10  0:43       ` Sunil Mushran [this message]
2011-06-09 17:53 ` Sunil Mushran
2011-06-10  1:01   ` Wengang Wang
2011-06-10  1:10     ` Sunil Mushran
2011-06-10  1:21       ` Wengang Wang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DF168A5.2050601@oracle.com \
    --to=sunil.mushran@oracle.com \
    --cc=ocfs2-devel@oss.oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.