glusterfs.git/xlators/protocol/server/src/server-helpers.c, branch v3.0.3rc2

Revert "Server backend storage hang should not cause the mount point to hang."

2010-01-26T15:23:19+00:00

This reverts commit a0b148ea4e2a0163548eeb89b7580be4adbb8070.

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

BUG: 272 (Server backend storage hang should not cause the mount point to hang)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=272

protocol/server: cleanup whitespaces

2010-01-23T10:58:38+00:00

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

BUG: 272 (Server backend storage hang should not cause the mount point to hang)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=272

Server backend storage hang should not cause the mount point to hang.

2010-01-23T10:58:34+00:00

Submitted-by: Krishna Srinivas 
NOTE: fixed compilation issues in posix.c introduced while merging

storage/posix polls for FS/kernel being functional by issuing
statvfs() call. In case statvfs expires the timer, storage/posix will
send CHILD_DOWN to upper translator. Ultimately this will cause
protocol/server to disconnect all clients connected and also cleans up
the data structures. Hence if soft lockup or other kernel bug causes
backend FS to hang, the clients will not be hung.

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

BUG: 272 (Server backend storage hang should not cause the mount point to hang)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=272

fix crash in server protocol server-connection-destroy

2009-12-05T08:49:22+00:00

a variable allocated inside a condition was getting reffered outside
the block. If the condition fails, there used to be a crash.

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

BUG: 439 (crash in server protocol, while destroying connection)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=439

protcol/server: server_connection_destroy - destroy frame after issuing flush

2009-12-04T09:46:23+00:00

frame was getting destroyed after unlocking, but before issuing flush. This
could result in corruption if an fd was opened between server_connection_cleanup
and server_connection_destroy because of pending open calls in io-threads at the
time of POLLERR disconnection

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

BUG: 430 (Server crash when client is killed)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=430

features/locks: Release all locks of an fd when a client disconnects.

2009-12-03T20:45:14+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

protocol/server: deep resolution support

2009-10-23T14:03:23+00:00

when requested ino/gen is not available in the inode table cache,
then use the path presented by the client to lookup entries with
the hope that the requested ino/gen gets populated into the cache.

re-perform regular search after finishing the deep component
lookup

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: generation number and dentry resolution

2009-10-20T17:34:14+00:00

- handle generation number in protocol
- rewrite server dentry resolution code for inode cache miss

Signed-off-by: Anand V. Avati 

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

Changed occurrences of Z Research to Gluster.

2009-10-07T10:54:49+00:00

Signed-off-by: Anand V. Avati

server-protocol: fix in server-loc-fill()

2009-07-28T16:42:40+00:00

to continue with 'hashed' inode, even if inode_path() on the inode
fails. This will is needed for few lock operations, to unlock the
lock held on inode. (ie, it fixes 'rm -rf *' hang issue, seen from
multiple clients).

Signed-off-by: Anand V. Avati 

BUG: 112 (parallel deletion of files mounted by different clients on the same back-end hangs and/or does not completely delete)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=112