From: Wengang Wang <wen.gang.wang@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 3/3] ocfs2:freeze-thaw: make it work
Date: Thu, 28 Jan 2010 02:14:29 +0800 [thread overview]
Message-ID: <20100127181429.GA4635@laptop.oracle.com> (raw)
In-Reply-To: <4B5749CF.6070004@oracle.com>
Sunil,
On 10-01-20 10:22, Sunil Mushran wrote:
> Wengang Wang wrote:
>> seems we need a noqueue version of the ocfs2_freeze_lock(). timeout it
>> after some retries.
>
> noqueue will not help. Launch a timer to fire off after 30 secs to do
> a cancel convert. If freeze succeeds before that, then cancel the timer.
I think the timer is not a very good idea. Canceling an ocfs2 cluster
lock is not complex though it needs lines of code changes.
By your word, I felt you are meaning that the timer is a separated thing
from ocfs2_cluster_lock(). If so, we have to ensure the ocfs2_cluster_lock()
is really issued before the timer acts. Though here 30s is good that but are
we sure that it must be enough at any case? --I think we aren't.
Making sure cluster lock is issued before the timer acts, I guess we
need more code change and I think that is not worthy --it introduces bugs
and it's only for freeze/thaw, not a common demand.
So to avoid very long time waiting of a mount when cluster is frozen, I
want it make tries of no-queue cluster lock. And so does it when acquiring EX.
regards,
wengang.
next prev parent reply other threads:[~2010-01-27 18:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-09 18:00 [Ocfs2-devel] [PATCH 3/3] ocfs2:freeze-thaw: make it work Wengang Wang
2010-01-16 2:22 ` Sunil Mushran
2010-01-18 13:06 ` Wengang Wang
2010-01-18 16:17 ` Wengang Wang
2010-01-20 0:50 ` Sunil Mushran
2010-01-20 4:55 ` Wengang Wang
2010-01-20 18:22 ` Sunil Mushran
2010-01-21 2:18 ` Wengang Wang
2010-01-21 2:32 ` Sunil Mushran
2010-01-27 18:14 ` Wengang Wang [this message]
2010-01-27 20:09 ` Sunil Mushran
2010-01-28 13:00 ` Wengang Wang
2010-01-28 18:08 ` Sunil Mushran
2010-01-22 4:22 ` Wengang Wang
2010-01-22 22:35 ` Sunil Mushran
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=20100127181429.GA4635@laptop.oracle.com \
--to=wen.gang.wang@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.