From: Sunil Mushran <sunil.mushran@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 10:08:56 -0800 [thread overview]
Message-ID: <4B61D2B8.9030807@oracle.com> (raw)
In-Reply-To: <20100128130014.GA4083@laptop.oracle.com>
Wengang Wang wrote:
> cancel convert for what? only the freeze lock or a command interface for
> all cluster lock?
> I don't know if it's needed for a commond cluster lock. But anyway,
> seems the freeze/thaw relies on a cancelable(or a timeout version of) cluster
> lock. Otherwise, the lock will wait for thaw for ever. If there is a umount at
> the time, ocfs2 cleaning up hangs(at flushing work queue). Yes maybe we have a
> way to postpone the umount if we are aquiring the PR lock, but that also
> means if the cluster is frozen, umount has to wait until cluster thawed(this
> is bad).
>
> So, if we have plan to implement cancelable cluster lock(or a timeout version of
> cluster lock). I think we'd better do that before supporting freeze/thaw.
No. Please ignore the timer bit for now. Implement the rest first.
We'll get to this later.
next prev parent reply other threads:[~2010-01-28 18:08 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
2010-01-27 20:09 ` Sunil Mushran
2010-01-28 13:00 ` Wengang Wang
2010-01-28 18:08 ` Sunil Mushran [this message]
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=4B61D2B8.9030807@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.