glusterfs.git/xlators/protocol/client, branch v3.1.6qa4

protocol/client: changes in volume_options to assist

2011-07-17T14:47:06+00:00

Signed-off-by: Kaushik BV 
Signed-off-by: Anand Avati 

BUG: 2041 (volume set help option)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2041

client-handshake: skip CHILD_DOWN notifications when client is querying port using different volume names in the presence of rdma.

2011-07-12T07:07:10+00:00

Signed-off-by: Raghavendra G 
Signed-off-by: Anand Avati 

BUG: 3091 (rebalance fails with "transport endpoint not connected" in 3.2.1 rdma set-up)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3091

fix multiple transport related portmap issues in client handshake

2011-06-19T09:16:34+00:00

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

BUG: 2258 (enhance gluster volume rebalance)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2258

loc_t: add 'gfid' and 'pargfid' fields

2011-06-14T07:13:43+00:00

these fields are used mainly in case of selfheal path, where
'inode->gfid'||'parent->gfid' is not yet set.

These fields in 'loc' will have lower precedence than 'inode->gfid'
in client protocol.

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

BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

Introduce client-allow-insecure xlator-option.

2011-05-31T16:12:04+00:00

Allows glusterfs clients to bind to any port and does not restrict it
to 1024.

This is a xlator-option only, and is not supported in volume set cmd.
The reason is, few clients may choose this, and few may not. Hence
only supported as a xlator-option during mount time.

For this to work with glusterfs, server.allow-insecure should be set
to on

Signed-off-by: shishir gowda 
Signed-off-by: Anand Avati 

BUG: 2868 (Add xlator-option to support insecure-bind for clients)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2868

protocol/client: make sure to send only genuine events up to parent

2011-04-06T19:06:10+00:00

that way parent notify logic is fine.

also, remove 'xlator_notify()' call in code, instead use 'default_notify()'

Signed-off-by: Amar Tumballi 
Signed-off-by: Vijay Bellur 

BUG: 2584 (Inode number changes on a directory when one of subvolumes is down in replicate)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2584

rpc/rpc-clnt: don't use iobref passed from caller to hold iobufs required for building program and rpc headers.

2011-02-22T10:11:40+00:00

- clustering translators like replicate assume iobrefs will be used as
    read-only by lower layers and there by use the same iobref while
    winding calls to multiple children. Since iobrefs can hold only limited
    number of iobufs, this limits the number of children these translators
    can have without overflowing iobrefs.

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

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

rpc/xdr: update .x files

2011-02-19T07:32:26+00:00

* now, 'rpcgen $filename-xdr.x' file will result in $filename-xdr.h

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

BUG: 2153 (glusterfs3.x does not match "generated" source)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2153

protocol/client: decrement reopen fd count in cases of re-open errors

2011-02-07T19:33:07+00:00

In post-client-handshake client tries to re-open files, dirs, but if those
files/dirs are already deleted when the brick is down the reopens
won't even get triggered. In those cases the re-open fd count needs to
be decremented to make sure the child up is triggered.
I have also made similar changes in all the error cases of re-open/re-open-dir
cbks. Lock recovery is already handling all these errors.

Signed-off-by: Pranith Kumar K 
Signed-off-by: Anand V. Avati 

BUG: 1761 (incorrect self-heal behaviour when files are deleted)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1761

protocol: fix warnings due to format string mismatches during invocation of gf_log.

2010-12-13T07:38:47+00:00

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

BUG: 2211 ((re)introduce warnings for format string/parameter mismatch)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2211