ocfs2-devel.oss.oracle.com archive mirror
 help / color / mirror / Atom feed
From: Sunil Mushran <sunil.mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: Add some trace log for orphan scan.
Date: Tue, 01 Jun 2010 10:23:09 -0700	[thread overview]
Message-ID: <4C0541FD.9050406@oracle.com> (raw)
In-Reply-To: <1275371893-6452-1-git-send-email-tao.ma@oracle.com>

Signed-off-by: Sunil Mushran<sunil.mushran@oracle.com>


On 05/31/2010 10:58 PM, Tao Ma wrote:
> Now orphan scan worker has no trace log, so it is
> very hard to tell whether it is finished or blocked.
> So add 2 mlog trace log so that we can tell whether
> the current orphan scan worker is blocked or not.
> It does help when I analyzed a orphan scan bug.
>
> Signed-off-by: Tao Ma<tao.ma@oracle.com>
> ---
>   fs/ocfs2/journal.c |    3 +++
>   1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/fs/ocfs2/journal.c b/fs/ocfs2/journal.c
> index 47878cf..776ab2f 100644
> --- a/fs/ocfs2/journal.c
> +++ b/fs/ocfs2/journal.c
> @@ -1888,6 +1888,8 @@ void ocfs2_queue_orphan_scan(struct ocfs2_super *osb)
>
>   	os =&osb->osb_orphan_scan;
>
> +	mlog(0, "Begin orphan scan\n");
> +
>   	if (atomic_read(&os->os_state) == ORPHAN_SCAN_INACTIVE)
>   		goto out;
>
> @@ -1920,6 +1922,7 @@ void ocfs2_queue_orphan_scan(struct ocfs2_super *osb)
>   unlock:
>   	ocfs2_orphan_scan_unlock(osb, seqno);
>   out:
> +	mlog(0, "Orphan scan completed\n");
>   	return;
>   }
>
>    

  reply	other threads:[~2010-06-01 17:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-01  5:58 [Ocfs2-devel] [PATCH] ocfs2: Add some trace log for orphan scan Tao Ma
2010-06-01 17:23 ` Sunil Mushran [this message]
2010-08-12  0:31 ` Joel Becker

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=4C0541FD.9050406@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).