glusterfs.git/xlators/features, branch v3.2.6qa5

gsyncd: geo-rep: Reduce excessive verbosity in logging

2012-03-06T17:46:21+00:00

Backport logging enhancement from master. This patch
reduces per-second logging to per-minute logging during
crawl

Change-Id: Ie51207e6dd8a0257e59f90239cc6960803673223
BUG: 789078
Signed-off-by: Venky Shankar 
Reviewed-on: http://review.gluster.com/2879
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

geo-rep / syncdaemon: make the timeout for establishing the connection to slave configurable

2012-03-01T17:28:20+00:00

It can be set through the connection-timeout tunable but we keep it hidden,
intended as a workaround for some special scenarios not for general use.

Change-Id: I31f9fa3873afa7babc2106ee34484123a01bdc57
BUG: 789078
Signed-off-by: Csaba Henk 
Reviewed-on: http://review.gluster.com/2840
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

features/marker: xtime should not be updated for modifications done by special client.

2012-01-24T11:34:52+00:00

Change-Id: I4b34d449b3ab08e2189fe1ff088299617b640206
BUG: 769494
Signed-off-by: Junaid 
Reviewed-on: http://review.gluster.com/2564
Tested-by: Gluster Build System 
Reviewed-by: Csaba Henk

features/marker-quota: Use stack_wind_cookie in place of stack_wind to preserve the cookie value.

2011-11-11T12:41:29+00:00

In marker_rename, some of the call back functions make use of cookies sent by the calling functions. In case of stack_wind the
frame->cookie is over written with the address of new frame.

Change-Id: I8ec98f3305700e2c3295a10dff159ca6a19a380a
BUG: 3808
Reviewed-on: http://review.gluster.com/717
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

cli: add geo-replication log-rotate command

2011-11-04T09:06:44+00:00

Rotating geo-replication master/monitor log files from cli.
On invocation, the log file for a given master-slave session
is backed up with the current timestamp suffixed to the file
name and signal is sent to gsyncd to start logging to a new
log file.

Sample commands:

* Rotate log file for this : session:
gluster volume geo-replication   log-rotate

* Rotate log files for all session for master volume 
gluster volume geo-replication  log-rotate

* Rotate log files for all sessions:
gluster volume geo-replication log-rotate

Change-Id: If801743e9f37bd282e68d262203141626ce77e55
BUG: 3519
Reviewed-on: http://review.gluster.com/653
Tested-by: Gluster Build System 
Reviewed-by: Csaba Henk

check the return value of inode_path for less than or equal to zero

2011-10-28T11:14:56+00:00

Change-Id: I9bbdfe79664c1339b66819a6c7ea4b7698beb5c6
BUG: 3757
Reviewed-on: http://review.gluster.com/640
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi

locks: perform inode_ref of pl_update_refkeeper outside locked region

2011-10-27T10:47:54+00:00

Performing inode_ref inside the critical section of pl_update_refkeeper
(around pl_inode_t->mutex) causes a deadlock with inode_table_t->lock.
The other thread (process state dump) holds the inode_table_t->lock first
to loop over inodes and then while dumping an inode's lock context, tries
to acquire pl_inode_t->mutex thereby completing the deadlock.

The fix is to perform inode_ref outside the critical section in
pl_update_refkeeper

Change-Id: I689ab4a9b46b36287740279fdec6159182c86119
BUG: 3753
Reviewed-on: http://review.gluster.com/629
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

features/marker-quota: Donot log when inode or inode-ctx is NULL.

2011-10-27T09:57:34+00:00

When running rm -rf from mount point, quota-updation process may endup in a state where the
inode is already removed from the gluster inode table, but the updation has process is still in
progress. This is not a error condition because the updation is done asynchronously.

Change-Id: I2d3aad716bb1c971115004a70ca76e2dd5088e44
BUG: 3609
Reviewed-on: http://review.gluster.com/603
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

features/marker-quota: Return error when inode-contribution not present in inode_ctx.

2011-09-30T07:13:18+00:00

Also, create the inode_contribution node even before checking for dirty and xattr not present in mq_inspect_directory_xattr function.

Change-Id: Ie5b6e6ba8d5abcfc6aeb9b192720ac10aac1319e
BUG: 3624
Reviewed-on: http://review.gluster.com/538
Tested-by: Gluster Build System 
Reviewed-by: Raghavendra G

Revert "cluster/afr: eager locking of FD writes"

2011-09-22T15:42:01+00:00

This reverts commit 81456ec2dfb312ae60c5c4e6f960a3cbf8aaaa4c.

Change-Id: Id03335117f5137f5d09781850bf4fba6eca0f73d
Reviewed-on: http://review.gluster.com/492
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur