glusterfs.git/xlators/protocol/client/src, branch v3.1.4qa3 protocol/client: make sure to send only genuine events up to parent 2011-04-06T19:06:10+00:00 Amar Tumballi amar@gluster.com 2011-04-05T04:03:43+00:00 0b91f5be63813e6494283a8ac7d6e1e4348c9f13 that way parent notify logic is fine. also, remove 'xlator_notify()' call in code, instead use 'default_notify()' Signed-off-by: Amar Tumballi <amar@gluster.com> Signed-off-by: Vijay Bellur <vijay@gluster.com> 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 
that way parent notify logic is fine.

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

Signed-off-by: Amar Tumballi <amar@gluster.com>
Signed-off-by: Vijay Bellur <vijay@gluster.com>

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 Raghavendra G raghavendra@gluster.com 2011-02-21T08:45:41+00:00 b00b3d46c226d339a1cfde70ceab101cee2ac865 - 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 <raghavendra@gluster.com> Signed-off-by: Anand V. Avati <avati@dev.gluster.com> BUG: 2157 (glusterfsd crash) URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2157 
- 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 <raghavendra@gluster.com>
Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

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 Amar Tumballi amar@gluster.com 2011-02-18T02:54:49+00:00 069d7765898ef6f8d1334b23bf8ed9aee017b47a * now, 'rpcgen $filename-xdr.x' file will result in $filename-xdr.h Signed-off-by: Amar Tumballi <amar@gluster.com> Signed-off-by: Anand V. Avati <avati@dev.gluster.com> BUG: 2153 (glusterfs3.x does not match "generated" source) URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2153 
* now, 'rpcgen $filename-xdr.x' file will result in $filename-xdr.h

Signed-off-by: Amar Tumballi <amar@gluster.com>
Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

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 Pranith K pranithk@gluster.com 2011-02-07T05:42:18+00:00 9cfa22f828f69c9f1f48b5e8994a4dff48d283a6 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 <pranithk@gluster.com> Signed-off-by: Anand V. Avati <avati@dev.gluster.com> BUG: 1761 (incorrect self-heal behaviour when files are deleted) URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1761 
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 <pranithk@gluster.com>
Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

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 Raghavendra G raghavendra@gluster.com 2010-12-13T00:13:15+00:00 26caaeae10414f9888a438ad8559692a7f74f918 Signed-off-by: Raghavendra G <raghavendra@gluster.com> Signed-off-by: Anand V. Avati <avati@dev.gluster.com> BUG: 2211 ((re)introduce warnings for format string/parameter mismatch) URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2211 
Signed-off-by: Raghavendra G <raghavendra@gluster.com>
Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

BUG: 2211 ((re)introduce warnings for format string/parameter mismatch)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2211
client-reopen-cbk: fix a gf_log() crash due to wrong argument list 2010-12-13T04:07:50+00:00 Amar Tumballi amar@gluster.com 2010-12-10T12:24:16+00:00 df5f71b401decfb32006d7564db1a13bcd5e8be2 Signed-off-by: Amar Tumballi <amar@gluster.com> Signed-off-by: Anand V. Avati <avati@dev.gluster.com> 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 
Signed-off-by: Amar Tumballi <amar@gluster.com>
Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

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
protocol: avoid repetitive disconnect logs 2010-12-10T10:51:12+00:00 Anand Avati avati@gluster.com 2010-12-09T02:06:52+00:00 9f480be0333863a2cb30088504d233fd6eb46ebf Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com> Signed-off-by: Anand V. Avati <avati@dev.gluster.com> 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 
Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

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
rpc-clnt: show disconnect messages in log file by default 2010-12-07T06:18:59+00:00 Anand Avati avati@gluster.com 2010-12-07T00:02:10+00:00 f783ecfbfd8c873d97644b8b6b0d95e3f878b992 Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com> Signed-off-by: Anand V. Avati <avati@dev.gluster.com> 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 
Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

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
protocol/client: skip notify if query portmap is successful 2010-11-18T13:55:43+00:00 shishir gowda shishirng@gluster.com 2010-11-16T03:52:17+00:00 9c80f63d8264718c5855f1f6cca9e5a801392ed3 Mount point does not hang, though stale handle error on / till the downed brick is online again Signed-off-by: shishir gowda <shishirng@gluster.com> Signed-off-by: Anand V. Avati <avati@dev.gluster.com> BUG: 1905 (Mounting volume is not working when any one server is down) URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1905 
Mount point does not hang, though stale handle error on / till the downed brick is
online again
Signed-off-by: shishir gowda <shishirng@gluster.com>
Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

BUG: 1905 (Mounting volume is not working when any one server is down)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1905
protocol/client: use the new rpc_clnt initialization methods 2010-11-16T14:35:14+00:00 Anand Avati avati@gluster.com 2010-11-16T08:17:07+00:00 ce9f328aa93892ea79057c41c70836eb49fae8b5 This way of initializing an rpc_clnt object by splitting into a passive rpc_clnt_new and a delayed rpc_clnt_start between which registration of callback programs and notify methods are performed provides a race-free way to avoid the missing of connect notifications Signed-off-by: Anand V. Avati <avati@amp.gluster.com> Signed-off-by: Anand V. Avati <avati@dev.gluster.com> BUG: 2078 (Volume Migration is not working) URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2078 
This way of initializing an rpc_clnt object by splitting into a
passive rpc_clnt_new and a delayed rpc_clnt_start between which
registration of callback programs and notify methods are performed
provides a race-free way to avoid the missing of connect notifications

Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

BUG: 2078 (Volume Migration is not working)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2078