glusterfs.git/xlators/cluster/afr/src/afr-transaction.c, branch v3.0.2

afr: handle fdctx->pre_op_done handling

2009-11-29T13:32:58+00:00

reset pre_op_done[i] to 0 after issuing a postop in flush. this was
missed during the introduction of pre_op_done[] array and was resulting
in a lot of spurious self heals when spurious flushes were received

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

BUG: 170 (Auto-heal fails on files that are open()-ed/mmap()-ed)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=170

cluster/afr: Include "common-utils.h" instead of alloca.h

2009-11-26T10:48:42+00:00

alloca.h should be included on a platform-specific basis.
Lets common-utils.h handle that.

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

BUG: 349 (FreeBSD compilation error (alloca.h).)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=349

cluster/afr: Do self-heal on unopened fds.

2009-11-25T14:03:39+00:00

This patch completes the previous patch for self-heal of
open fds in replicate.

If an fd was never opened on a subvolume, we remember that
and do the open after we've done self-heal on that fd.

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

BUG: 170 (Auto-heal fails on files that are open()-ed/mmap()-ed)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=170

cluster/afr: Do self-heal on reopened fds.

2009-11-24T14:40:08+00:00

This patch brings in partial support for self-heal of open
fds. The precondition is that the fd should have been opened
successfully during the initial open() (or create()), and we
assume that protocol/client has successfully reopened the fd
when the subvolume comes back up.

It works by doing an "up/down flush" (a dummy flush transaction
to do post-op wherever necessary) and then triggering
data self-heal on the file in the post-post-op hook of the
dummy flush transaction. This ensures that any writes
that come in during self-heal will wait until self-heal completes.

The up/down flush is also done when a subvolume goes down,
so that post-op is done on all subvolumes where pre-op was done.

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

BUG: 170 (Auto-heal fails on files that are open()-ed/mmap()-ed)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=170

cluster/afr: Provide a post-post_op hook in the transaction.

2009-11-24T14:40:04+00:00

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

BUG: 170 (Auto-heal fails on files that are open()-ed/mmap()-ed)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=170

cluster/afr: Hold blocking locks for data self-heal.

2009-11-24T14:39:57+00:00

Data self-heal now holds blocking locks, and instead of locking
on all subvolumes, it only locks on {data-lock-server-count} subvolumes.

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

BUG: 170 (Auto-heal fails on files that are open()-ed/mmap()-ed)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=170

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

2009-11-24T12:36:45+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

afr transaction: fix op_ret check during locking

2009-10-13T13:23:10+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

afr transaction prevent spurious unlocks

2009-10-13T12:46:43+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

cluster/afr: Hold second lock after first lock has been granted for rename transactions.

2009-10-12T17:29:18+00:00

Hold the lock on the {higher_path} only after the lock on the
{lower_path} has been granted successfully.

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