glusterfs.git/xlators/cluster/afr, branch v2.0.10rc2

cluster/afr: Check for call_count in ENTRY_RENAME_TRANSACTION.

2010-04-20T08:51:14+00:00

Signed-off-by: Vijay Bellur 
Signed-off-by: Anand V. Avati 

BUG: 824 (Crash in afr rename transaction)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=824

cluster/afr: Send flock returned by locks xlator to user.

2010-01-24T18:59:15+00:00

Signed-off-by: Pavan Vilas Sondur 
Signed-off-by: Anand V. Avati 

BUG: 521 (SPECFS validation fails over distribute + replicate)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=521

cluster/afr: Don't try to self-heal if there are locks held

2009-10-30T11:30:59+00:00

If the inodelk_count or entrylk_count is positive on a
file/directory, don't try to do self-heal on it.

Signed-off-by: Vikas Gorur 
Signed-off-by: Anand V. Avati 

BUG: 326 ([2.0.8rc9] Spurious self-heal)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=326

cluster/afr: Prevent spurious entry self-heal.

2009-10-23T12:54:57+00:00

If the initial lookup shows that 'pending' is positive, then
self-heal will hold a lock and do a lookup again. This lookup
might show that 'pending' is zero everywhere. However, entry
self-heal used to consider this as a case of 'no sources' and
try to merge the directories. This patch checks for that case
and does not do the merge.

Signed-off-by: Anand V. Avati 

BUG: 326 ([2.0.8rc9] Spurious self-heal)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=326

cluster/afr: Attempt to set fd ctx in create only if the call has succeeded.

2009-10-20T07:28:12+00:00

Signed-off-by: Anand V. Avati 

BUG: 325 (crash in afr_fd_ctx_set)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=325

cluster/afr: Unlock only those paths which have been locked during rename.

2009-10-16T12:03:40+00:00

For ENTRY_RENAME_TRANSACTIONs, keep track separately whether the
lower_path and the higher_path have been locked, and unlock only
those which have been.

Signed-off-by: Anand V. Avati 

BUG: 112 (parallel deletion of files mounted by different clients on the same back-end hangs and/or does not completely delete)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=112

cluster/afr: Hold lock on all names under "victim" in rmdir

2009-10-16T10:12:59+00:00

When an rmdir is being done, hold a lock on all names under it, so
that new entries cannot be created while the rmdir is in progress.

Without this lock, rmdir and create operations under the
victim directory race with each other leading to
inconsistencies among the subvolumes.

Signed-off-by: Anand V. Avati 

BUG: 112 (parallel deletion of files mounted by different clients on the same back-end hangs and/or does not completely delete)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=112

afr transaction: fix op_ret check during locking

2009-10-13T13:23:14+00:00

Signed-off-by: Anand V. Avati 

BUG: 112 (parallel deletion of files mounted by different clients on the same back-end hangs and/or does not completely delete)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=112

prevent spurious unlocks from afr selfheal

2009-10-13T12:46:55+00:00

afr selfheal now remembers all the nodes on which locks were successfully
held and sends unlocks only to those nodes

Signed-off-by: Anand V. Avati 

BUG: 112 (parallel deletion of files mounted by different clients on the same back-end hangs and/or does not completely delete)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=112

afr transaction prevent spurious unlocks

2009-10-13T12:46:52+00:00

mark a subvol with held lock only if op_ret == 0

Signed-off-by: Anand V. Avati 

BUG: 112 (parallel deletion of files mounted by different clients on the same back-end hangs and/or does not completely delete)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=112