glusterfs.git/xlators, branch v3.1.1qa5

protocol/server: fix log level of message in server-resolver.c

2010-11-09T11:18:03+00:00

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

BUG: 1092 ()
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1092

replicate: optimistic changelog

2010-11-09T11:07:07+00:00

The standard way of maintaining changelog in replicate has been to
write out pending flags and to unset the pending flag post the
actual operation.

This new optimization kicks in only when all subvolumes are up.

The optimization is that, during pre-op, no changelog is written for
METADATA and ENTRY/RENAME operations. If during the operation nothing
failed, no changelog is updated in post-op either. If however,
something does fail during an operation, then, pending flags get
written during post op pointing only towards the failed nodes.

DATA transactions continue to work the way they are.

If one subvolume is down, pending flags are written in pre-op changelog
itself as before.

The impact of this optimization is only in the case when both servers
die or the client dies while the 'FOP' stage of the transaction is
in progress. By nature of METADATA and ENTRY operations, detecting a
mismatch later is not dependent on the presence of changelog. Changelog
only determines the direction in which self-heal happens for these types
of transactions. For the direction too this optimization does not have
a major impact because in the cases of failure (both servers dieing or
client dieing) the final state (direction of self-heal) would be
arbitrary anyways as the syscall wouldn't have completed.

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

BUG: 2068 (performance enhancements)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2068

client: Return correct pre/post iatt for dst during rename

2010-11-09T10:12:20+00:00

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

BUG: 2050 ()
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2050

mnt3: Fail mount requests for disallowed clients

2010-11-09T10:12:15+00:00

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

BUG: 1385 (showmount says no access though it can be mounted.)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1385

check if the brick being added is the destination brick of replace brick

2010-11-09T10:12:07+00:00

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

BUG: 2033 ()
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2033

nfs: Support nfs.port to allow changing nfs port numbers

2010-11-09T10:12:03+00:00

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

BUG: 1743 (XenServer is not compatible with GlusterNFS)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1743

nfs: Use only 38467 as default port instead of 3846[567]

2010-11-09T10:11:59+00:00

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

BUG: 1743 (XenServer is not compatible with GlusterNFS)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1743

nfsrpc: Decouple TCP connections from programs

2010-11-09T10:11:55+00:00

..so that multiple programs can be served from the same connection
or multiple ports can be bound to the same port number.

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

BUG: 1743 (XenServer is not compatible with GlusterNFS)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1743

protocol/server: array declarations changed to alloca()

2010-11-08T10:08:37+00:00

This is to make sure we don't spend CPU cycles in memset(0) on the
array, instead do a 'alloca()' on size of the request.

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

BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

access-control: Allow Writes/Reads to proceed without perm checks

2010-11-08T10:08:30+00:00

a. We expect that when the fds are opened through FUSE, thats when the
perm checks happen, depending on the read/write mode used.

b. In case of nfs clients, we expect the nfs clients to perform the checks
based on getattr/access nfs requests.

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

BUG: 2058 (posix permission compliance error)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2058