Displaying 13 results from an estimated 13 matches for "ocfs2_orphan_scan_lock".
2009 Jun 22
1
Orphan Scan - v3
Patch 5 has been respun with the recommended change... remove the ex
argument in ocfs2_orphan_scan_lock() and ocfs2_orphan_scan_unlock().
Sunil
2009 May 19
2
[PATCH 1/1] OCFS2: timer to queue scan of all orphan slots
...E_USES_LVB,
+};
+
static struct ocfs2_lock_res_ops ocfs2_dentry_lops = {
.get_osb = ocfs2_get_dentry_osb,
.post_unlock = ocfs2_dentry_post_unlock,
@@ -637,6 +641,15 @@ static void ocfs2_nfs_sync_lock_res_init(struct ocfs2_lock_res *res,
&ocfs2_nfs_sync_lops, osb);
}
+static void ocfs2_orphan_scan_lock_res_init(struct ocfs2_lock_res *res,
+ struct ocfs2_super *osb)
+{
+ ocfs2_lock_res_init_once(res);
+ ocfs2_build_lock_name(OCFS2_LOCK_TYPE_ORPHAN_SCAN, 0, 0, res->l_name);
+ ocfs2_lock_res_init_common(osb, res, OCFS2_LOCK_TYPE_ORPHAN_SCAN,
+ &ocfs2_orphan_scan_lops, osb);
+}
+...
2009 Jun 04
2
Backport that adds delayed orphan scan timer to 1.4
Next two patches are backport of orphan scan timer patches to ocfs2-1.4
2009 Jun 04
3
Patches that adds delayed orphan scan timer (rev 3)
Resending after implementing review comments.
2009 Jun 02
3
Patches that adds delayed orphan scan timer (rev 2)
Resending after implementing review comments.
2009 Jun 02
3
Patches that adds delayed orphan scan timer
Resending after adding another patch to display delayed orphan scan statistics.
2009 Jun 18
3
[PATCH 0/2] orphan lock fixes for local mode.
Hi Joel/Srini,
Here are 2 patches for orphan lock in local mode.
patch 1:
In local mode, we don't need lvb, so don't init it.
patch 2:
In local mode, orphan lock and unlock don't need to go to dlm part.
Regards,
Tao
2009 Jun 19
6
Orphan scan fixes - V2
Implemented the suggestions.
Also, moved the ocfs2_orphan_scan_init() to the end of ocfs2_fill_super()
instead of calling it earlier in ocfs2_initialize_super().
Sunil
2009 Jun 19
6
[PATCH 1/5] ocfs2: Pin journal head before accessing jh->b_committed_data
This patch adds jbd_lock_bh_state() and jbd_unlock_bh_state() around accessses
to jh->b_committed_data.
Fixes oss bugzilla#1131
http://oss.oracle.com/bugzilla/show_bug.cgi?id=1131
Signed-off-by: Sunil Mushran <sunil.mushran at oracle.com>
---
fs/ocfs2/suballoc.c | 28 ++++++++++++++++++++++++----
1 files changed, 24 insertions(+), 4 deletions(-)
diff --git a/fs/ocfs2/suballoc.c
2013 Apr 28
2
Is it one issue. Do you have some good ideas, thanks a lot.
...6 kernel: [ 3959.124092] [<ffffffffa053beb3>] __ocfs2_cluster_lock.isra.34+0x1f3/0x810 [ocfs2]
Apr 27 17:39:45 ZHJD-VM6 kernel: [ 3959.124116] [<ffffffffa05543e0>] ? ocfs2_queue_orphan_scan+0x270/0x270 [ocfs2]
Apr 27 17:39:45 ZHJD-VM6 kernel: [ 3959.124136] [<ffffffffa053d0a9>] ocfs2_orphan_scan_lock+0x99/0xf0 [ocfs2]
Apr 27 17:39:45 ZHJD-VM6 kernel: [ 3959.124159] [<ffffffffa05543e0>] ? ocfs2_queue_orphan_scan+0x270/0x270 [ocfs2]
Apr 27 17:39:45 ZHJD-VM6 kernel: [ 3959.124181] [<ffffffffa05541c5>] ocfs2_queue_orphan_scan+0x55/0x270 [ocfs2]
Apr 27 17:39:45 ZHJD-VM6 kernel: [ 3959....
2013 Apr 28
2
Is it one issue. Do you have some good ideas, thanks a lot.
...6 kernel: [ 3959.124092] [<ffffffffa053beb3>] __ocfs2_cluster_lock.isra.34+0x1f3/0x810 [ocfs2]
Apr 27 17:39:45 ZHJD-VM6 kernel: [ 3959.124116] [<ffffffffa05543e0>] ? ocfs2_queue_orphan_scan+0x270/0x270 [ocfs2]
Apr 27 17:39:45 ZHJD-VM6 kernel: [ 3959.124136] [<ffffffffa053d0a9>] ocfs2_orphan_scan_lock+0x99/0xf0 [ocfs2]
Apr 27 17:39:45 ZHJD-VM6 kernel: [ 3959.124159] [<ffffffffa05543e0>] ? ocfs2_queue_orphan_scan+0x270/0x270 [ocfs2]
Apr 27 17:39:45 ZHJD-VM6 kernel: [ 3959.124181] [<ffffffffa05541c5>] ocfs2_queue_orphan_scan+0x55/0x270 [ocfs2]
Apr 27 17:39:45 ZHJD-VM6 kernel: [ 3959....
2009 Jun 18
8
Patches backported from mainline
All,
Please review the patches backported to 1.4 from mainline.
Sunil
2009 Jun 19
1
[PATCH] ocfs2: Provide the ocfs2_dlm_lvb_valid() stack API.
The Lock Value Block (LVB) of a DLM lock can be lost when nodes die and
the DLM cannot reconstruct its state. Clients of the DLM need to know
this.
ocfs2's internal DLM, o2dlm, explicitly zeroes out the LVB when it loses
track of the state. This is not a standard behavior, but ocfs2 has
always relied on it. Thus, an o2dlm LVB is always "valid".
ocfs2 now supports both o2dlm and