glusterfs.git/xlators/protocol/client, branch v3.0.0

Revert "protocol/client: return ENOENT if inode context is missing"

2009-12-06T19:34:07+00:00

This reverts commit 4439876a34f2e5d19db0d8b05ce7d7722c1c466f.

This revert is necessary for path handle resolution to work over the
protocol where client/server talk only with the path, without inode
or parent inode and generation numbers

protocol/client: return ENOENT if inode context is missing

2009-12-04T13:57:41+00:00

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

BUG: 315 (generation number support)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

protocol/server: Changes in protocol client to include lk_owner in protocol header.

2009-12-03T20:45:07+00:00

Signed-off-by: Pavan Vilas Sondur 
Signed-off-by: Anand V. Avati 

BUG: 336 (Use lock owner field from fuse in locks)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=336

core, client, server: Support auxiliary group ids

2009-12-03T10:59:28+00:00

Support for auxiliary group ids is needed for transmission
of more than one group id right through the xlator tree
so that posix can use these group ids to perform
in-house permission tests. The in-house permission checks are
needed so that we do not have to depend on non-POSIX calls
like setfs[ug]id for changing the user for each fop.

The setfs[ug]id  are also limited since they do not allow setting
multiple group id as required for operation with NFS, which sends
us all the group ids for a process issuing file system requests.

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

BUG: 400 (Support auxiliary gids in GlusterFS)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=400

add an extra check for loc->parent when loc->ino is not 1

2009-11-26T10:49:07+00:00

This extra check is needed only in case where setup is
"server -> chain -> client", where for the root inode, inode->ino
is not updated in the first lookup call, hence used to crash.

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

BUG: 377 (segfault in protocol/client with chaining)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=377

changed the log level of failure case in client_setvolume_cbk

2009-11-26T10:48:50+00:00

It *should* be an error when a handshake fails. Its hard to debug
it otherwise

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

BUG: 26 (Version mismatch not handled correctly)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=26

Added boundaries for each fops, mops and cbks.

2009-11-26T10:48:47+00:00

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

BUG: 366 (Infinite loop with centralized logging.)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=366

protocol/client: Make log message print both generation number and inode number.

2009-11-25T14:03:43+00:00

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

BUG: 315 (generation number support)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

Check for other return values as well from call to inode_path.

2009-11-19T08:53:13+00:00

Signed-off-by: Pavan Vilas Sondur 
Signed-off-by: Anand V. Avati 

BUG: 170 (Auto-heal fails on files that are open()-ed/mmap()-ed)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=170

protocol/client: Changed default ping-timeout to 42

2009-11-19T08:53:06+00:00

This change is necessary to avoid frequent disconnections between client and server under load.
A disconnect-connect sequence is costly in terms of clean up and re-building of context,
self-heals etc. This value should be optimal for most use cases. Users requiring a lower
ping-timeout value need to configure it explicitly.

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

BUG: 384 (Increase default timeout in client protocol)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=384