glusterfs.git/xlators/cluster/afr/src/afr-self-heal-entry.c, branch v3.0.3

cluster/afr: Don't do entry self-heal in the background.

2009-12-07T13:31:32+00:00

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

storage/posix: Added janitor thread.

2009-12-02T18:29:23+00:00

The janitor thread deletes all files and directories in
the "/" GF_REPLICATE_TRASH_DIR directory. This directory
is used by replicate self-heal to dump files and
directories it deletes.

This is needed because letting replicate walk the directory
tree and delete a directory and all its children is too racy.
Instead, replicate self-heal only does an atomic rename(),
and the janitor thread takes care of actually deleting them.

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

BUG: 227 (replicate selfheal does not remove directory with contents in it)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=227

cluster/afr: Refactored the self-heal interface.

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

Cleaned up the self-heal interface to callers.

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: Ensure directory contents are in sync during opendir.

2009-11-13T10:13:43+00:00

The problem: If some files on the first subvolume disappeared
without leaving a trace in the entry changelog (this can happen,
for example, when an fsck has deleted files or when a hard drive
is replaced), those files would never be self-healed even though
they would be present on the second subvolume. This is because
readdir is sent only to the first subvolume, and since the files
don't appear in the directory listing, no lookup would ever be
sent on them.

This patch fixes this problem by doing a readdir on all the subvolumes
during the first opendir on a directory inode. If a discrepancy in the
contents is detected, entry self-heal in a special "force merge" mode
is triggered on that directory.

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

BUG: 249 (Self heal of a file that does not exist on the first subvolume)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=249

cluster/afr: Move deleted files to /.trash in entry self-heal.

2009-10-29T17:17:19+00:00

If entry self-heal determines that a file/directory should
be deleted from a subvolume, move that entry to a directory
called "/.trash" on that subvolume. This is for two reasons:

1) It limits the damage that can be done by a "wrong" entry
   self-heal.

2) It solves the problem of a to-be-deleted directory not
   being empty.

Signed-off-by: Anand V. Avati 

BUG: 227 (replicate selfheal does not remove directory with contents in it)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=227

cluster/afr: Check the target of symlink's in entry self-heal.

2009-10-26T14:09:28+00:00

During entry self-heal, make sure not only that a symlink
exists on all subvolumes, but also that their targets match.

Signed-off-by: Anand V. Avati 

BUG: 193 (symlink contents not self-healed by replicate)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=193

cluster/afr: Do self-heal in the background.

2009-10-26T14:09:05+00:00

This patch introduces a new option "background-self-heal-count", with a
default value of 16.

This means that upto {background-self-heal-count} number of files/directories
will be healed in the background at any given time. If such number of self-heals
are already in progress, further self-heals take place in the foreground.

Signed-off-by: Anand V. Avati 

BUG: 320 (Improve self-heal performance)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=320

cluster/afr: Prevent spurious entry self-heal.

2009-10-23T12:54:53+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: entry self-heal: Store parent_loc on the heap for impunge_parent_setattr.

2009-10-22T13:05:13+00:00

Signed-off-by: Anand V. Avati 

BUG: 137 (Parent directory mtime not reset after a create in self-heal)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=137

cluster/afr: entry self-heal: Set parent directory's attributes using a new frame.

2009-10-22T11:15:43+00:00

There was a race condition in assuming that afr_sh_entry_impunge_parent_setattr_cbk will
   always return before impunge_xattrop_cbk and impunge_setattr_cbk.

   This patch fixes two additional problems:

1) Building the parent_loc from impunge_local->loc after STACK_WIND to
   impunge_xattrop_cbk has happened. In a simple afr-posix configuration
   the stack will have been destroyed by the time building of parent_loc is
   attempted.

2) parent_loc built in impunge_newfile_cbk was not being loc_wipe'd.

Signed-off-by: Anand V. Avati 

BUG: 137 (Parent directory mtime not reset after a create in self-heal)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=137