glusterfs-afrv1.git/xlators, branch v3.5.0beta4

gNFS: Set default outstanding RPC limit to 16

2014-03-07T20:11:28+00:00

Backport of http://review.gluster.org/#/c/6696/

With 64, NFS server hangs with large I/O load (~ 64 threads writing
to NFS server). The test results from Ben England (Performance expert)
suggest to set it as 16 instead of 64.

Change-Id: Iaa9dda512904d2e359d8122a05e5bf65f99a7e78
BUG: 1073441
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: http://review.gluster.org/7200
Tested-by: Gluster Build System 
Reviewed-by: Santosh Pradhan

geo-rep/gfid-access: Fix errno for non-existent GFID.

2014-03-03T05:05:29+00:00

Because of http://review.gluster.org/#/c/6318/ patch,
ESTALE is returned for a lookukp on non-existent GFID.
But ENOENT is more appropriate when lookup happens
through virtual .gfid directory on aux-gfid-mount
point. This is avoids confusion for the consumers
of gfid-access-translator like geo-rep which expects
ENOENT.

Change-Id: I4add2edf5958bb59ce55d02726e6b3e801b101bb
BUG: 1069191
Signed-off-by: Kotresh H R 
Reviewed-on: http://review.gluster.org/7154
Tested-by: Gluster Build System 
Reviewed-by: Raghavendra G 
Reviewed-by: Venky Shankar 
Reviewed-by: Anand Avati 
Reviewed-on: http://review.gluster.org/7163
Reviewed-by: Vijay Bellur

storage/posix: perform chmod after chown.

2014-02-17T09:51:03+00:00

Problem:
When a replica brick is added to a volume, set-user-ID and set-group-ID
permission bits of files are not set correctly in the new brick. The issue
is in the posix_setattr() call where we do a chmod followed by a chown.

But according to the man pages for chown:
When the owner or group of an executable file are changed by an unprivileged
user the S_ISUID and S_ISGID mode bits are cleared.  POSIX does not specify
whether this also  should  happen  when  root does the chown().

Fix:
Swap the chmod and chown calls in posix_setattr()

BUG: 1058797
Change-Id: Id2fbd8394cf6faf669f414775409f20f46009f2b
Signed-off-by: Ravishankar N 
Reviewed-on: http://review.gluster.org/6988
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

features/quota: fix crash in error handling after building ancestry.

2014-02-08T16:22:22+00:00

Change-Id: Ifbebf1aa496d49a6c4bb30258b83aaf9792828e5
BUG: 1059833
Signed-off-by: Raghavendra G 
Reviewed-on: http://review.gluster.org/6924
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

glusterd: Reset opinfo.op ONLY if lock succeeded

2014-02-08T03:00:19+00:00

... and also initialise @this before doing anything else.

Change-Id: I0244a7f61a826b32f4c2dfe51e246f2593a38211
BUG: 1060434
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/6885
Reviewed-by: Kaushal M 
Reviewed-by: Krishnan Parthasarathi 
Tested-by: Gluster Build System 
Reviewed-on: http://review.gluster.org/6922
Reviewed-by: Vijay Bellur

libxlator: fix memleak in cluster_markerxtime_cbk and cluster_markeruuid_cbk

2014-02-07T16:53:38+00:00

Change-Id: Ide3574bf9f661b077f707990d47821feda18b1a3
BUG: 841617
Reviewed-on: http://review.gluster.org/6872
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

POSIX : gefattr fails and mount point become inaccessible

2014-02-07T10:45:21+00:00

Problem : getfattr fails and mount point becomes inaccessible while
fetching glusterfs.ancestry.path key value for a gfid from aux-gfid-mount based mount point.

Analysis : The caller of posix_make_ancestryfromgfid() function i.e.
posix_get_ancestry_non_directory() is sending an incorrect type value as
an argument leading to a crash in posix_make_ancestral_node() (head
dirent pointer is NULL and an attempt to dereference causes seg fault).
For a non directory operation this piece of code should not have been
executed but due to incorrect type value this happened.

Solution : In posix_make_ancestryfromgfid() call type is passed as
logical or of type and POSIX_ANCESTRY_PATH instead of logical or of
POSIX_ANCESTRY_PATH and POSX_ANCESTRY_DENTRY.

Please note this patch is backport picked up from following patch:
http://review.gluster.org/#/c/6892/

Change-Id: Iaf844bea91396c5e2ee295d5a082998fda66f0a9
BUG: 1060104
Signed-off-by: Atin Mukherjee 
Reviewed-on: http://review.gluster.org/6892
Reviewed-by: Raghavendra G 
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur 
Reviewed-on: http://review.gluster.org/6921

quota: get directory size before enforcing quota on rename

2014-02-06T07:05:59+00:00

        Backport of http://review.gluster.org/6155

BUG: 1023974
Change-Id: Icb4bca8c4a5fa9b14855478e69b1315f2e9a3c3d
Signed-off-by: Krishnan Parthasarathi 
Reviewed-on: http://review.gluster.org/6887
Reviewed-by: Raghavendra G 
Tested-by: Gluster Build System

quota: fix recording of last alert log message

2014-02-06T07:05:51+00:00

        Backport of http://review.gluster.org/6532

PROBLEM:

Alert log messages, corresponding to disk usage crossing soft-limit on a
directory, weren't being logged as often as expected.

CAUSE:

The mechanism in place to log alert messages, once every alert-time
seconds, set the previous logged time incorrectly.

FIX:

Update previous logged time only if we logged an alert message, ie. when
the "time was right" to alert.

BUG: 969461
Change-Id: Ie019c180c97d2b049fa664b14ce087b88e3b578f
Signed-off-by: Krishnan Parthasarathi 
Reviewed-on: http://review.gluster.org/6886
Reviewed-by: Raghavendra G 
Tested-by: Gluster Build System

mgmt/glusterd: Set right op versions for few options.

2014-02-03T13:45:17+00:00

compression and changelog translators appear first in 3.5. op-versions
of options corresponding to these translators should be 3.

Change-Id: Ib514207743e36eba53c3d5cf477c85136cf30b42
BUG: 923540
Signed-off-by: Vijay Bellur 
Reviewed-on: http://review.gluster.org/6849
Reviewed-by: Kaushal M 
Tested-by: Gluster Build System