similar to: Orphan scan fixes - V2

Patch 5 has been respun with the recommended change... remove the ex argument in ocfs2_orphan_scan_lock() and ocfs2_orphan_scan_unlock(). Sunil

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

Resending after implementing review comments.

Resending after implementing review comments.

Next two patches are backport of orphan scan timer patches to ocfs2-1.4

All, Please review the patches backported to 1.4 from mainline. Sunil

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

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

On unlink, all nodes check for the dentry in dcache and if present they mark the node as unlinked. The last node that purges the inode will clean it from orphan directory. When there is a memory pressure, a dentry may not be around and hence the inode is not marked as deleted and this will lead the file to be in the orphan directory till the slot is re-used during next mount. This patch initiates

Resending after adding another patch to display delayed orphan scan statistics.

The following series of patches comprises the bulk of our outstanding changes for Ocfs2. Aside from the usual set of cleanups and fixes that were inappropriate for 2.6.25, there are a few highlights: The '/sys/o2cb' directory has been moved to '/sys/fs/o2cb'. The new location meshes better with modern sysfs layout. A symbolic link has been placed in the old location so as to

Now the discussion moves to kernel space, I move the email from ocfs2-tools-devel to ocfs2-devel. The original discussion can be found from http://oss.oracle.com/pipermail/ocfs2-tools-devel/2009-June/001891.html Joel Becker Wrote: > On Sat, Jun 27, 2009 at 03:46:04AM +0800, Coly Li wrote: >> Joel Becker Wrote: >>> On Sat, Jun 27, 2009 at 03:00:05AM +0800, Coly Li wrote: >>

OS: Fedora Core release 4 (Stentz) KERNEL: Linux rack1.ape 2.6.17-1.2142_FC4smp #1 SMP Tue Jul 11 22:57:02 EDT 2006 i686 i686 i386 GNU/Linux CLUSTER: 11 Linux kernels, mixed environment FC4,FC5,FC6 SAN: FC Infortrend storage, QLogic16 port FC switch, FC adapter LSI FC929X (21224,1):ocfs2_truncate_file:242 ERROR: bug expression: le64_to_cpu(fe->i_size) != i_size_read(inode)

Srini, Ok, you can go ahead and cook up the background orphan cleaner. Now, we can do this in a workqueue, a thread, or a timer. I don't see why a timer doesn't work. When the timer fires, you do this: 1. Take EX on a new orphan_scan lock. 2. check the LVB for the last scan time. If it's less than the scan timeout, reset the timer for (timeout - last scan), drop the EX, and

Wether the dlm_lock needs to access lvb or not depends on dlm_lock_resource it belongs to. So a new parameter "struct dlm_lock_resource *res" is added to dlm_new_lock() so that we can know if we need to allocate lvb for the dlm_lock. And we have to make the lockres availale for calling dlm_new_lock(). Signed-off-by: Wengang Wang <wen.gang.wang at oracle.com> ---

Hi list, Here is a bug report on novell bugzilla (https://bugzilla.novell.com/show_bug.cgi?id=456280) that mount point inside node A can be removed from node B. The problem is, node B does not know an empty dir is be using as mount point on another node. Is there any solution to return -EBUSY when a dir is be using as mount point on another node ? Thanks in advance. -- Coly Li SuSE Labs

llseek requires ocfs2 inode lock for updating the file size in SEEK_END. because the file size maybe update on another node. if it not . after call llseek in SEEK_END. the position is old. this bug can be reproduce the following scenario: at first ,we dd a test fileA,the file size is 10k. on NodeA: --------- 1) open the test fileA, lseek the end of file. and print the position. 2) close the test

hello, i am a newbie to this list and i don't know if this has been posted before (if so, plzz accept my apologies) i just noticed a nice mini-howto on ext2-ext3 conversion at http://www.symonds.net/~rajesh/howto/ext3/index.html i think that maybe a link can be added to this after the download section... cheers Sayamindu *********************************************************************

Found 15 patches (out of 162) that appeared relevant to ocfs2 1.4. Please review. Sunil

Set auth-nxdomain yes; And stop/start bind9 Other source : https://blogs.technet.microsoft.com/teamdhcp/2015/09/10/a-description-of-the-dns-dynamic-update-message-format/ /snap The DNS Client and Server services support the use of dynamic updates, as described in Request for Comments (RFC) 2136, "Dynamic Updates in the Domain Name System." The DNS Server service allows dynamic