summaryrefslogtreecommitdiffstats
path: root/fs/ocfs2/journal.c
diff options
context:
space:
mode:
authorTao Ma <tao.ma@oracle.com>2010-06-01 13:58:13 +0800
committerJoel Becker <joel.becker@oracle.com>2010-09-10 08:35:51 -0700
commit3c3f20c9813391ba4004764072989744395cf405 (patch)
treed02ae291a1d9d591398b956fb8f0dac90f032af3 /fs/ocfs2/journal.c
parentddee5cdb70e6f87de2fc696b87bd7bd184a51eb8 (diff)
downloadop-kernel-dev-3c3f20c9813391ba4004764072989744395cf405.zip
op-kernel-dev-3c3f20c9813391ba4004764072989744395cf405.tar.gz
ocfs2: Add some trace log for orphan scan.
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> Signed-off-by: Joel Becker <joel.becker@oracle.com>
Diffstat (limited to 'fs/ocfs2/journal.c')
-rw-r--r--fs/ocfs2/journal.c3
1 files changed, 3 insertions, 0 deletions
diff --git a/fs/ocfs2/journal.c b/fs/ocfs2/journal.c
index 9b57c03..04d41df 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;
}
OpenPOWER on IntegriCloud