glusterfs.git/xlators/mgmt, branch v3.2.5qa6

cli: add geo-replication log-rotate command

2011-11-04T09:06:44+00:00

Rotating geo-replication master/monitor log files from cli.
On invocation, the log file for a given master-slave session
is backed up with the current timestamp suffixed to the file
name and signal is sent to gsyncd to start logging to a new
log file.

Sample commands:

* Rotate log file for this : session:
gluster volume geo-replication   log-rotate

* Rotate log files for all session for master volume 
gluster volume geo-replication  log-rotate

* Rotate log files for all sessions:
gluster volume geo-replication log-rotate

Change-Id: If801743e9f37bd282e68d262203141626ce77e55
BUG: 3519
Reviewed-on: http://review.gluster.com/653
Tested-by: Gluster Build System 
Reviewed-by: Csaba Henk

glusterd rebalance: fail rebalance command on non-distribute volumes

2011-11-03T13:15:18+00:00

Change-Id: Id8cf3cbc8297b5f24f67c152d789b7c2ac299ccc
BUG: 3729
Reviewed-on: http://review.gluster.com/652
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

glusterd: Fixed volume profile's "are all bricks down?" algo.

2011-10-28T15:08:13+00:00

"count" key is not set if no brick in the volume (located across peers) is
running. Sending "count" even when zero bricks are running from originator
glusterd to client, simplifies "are all bricks down?" algo.

Change-Id: I3a8db48c4c61cd31ba96031638a3c3d26efd2887
BUG: 3553
Reviewed-on: http://review.gluster.com/641
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

glusterd: Removing delayed moving of op sm for stop vol/remove brick op.

2011-10-28T11:58:18+00:00

Earlier we would wait until brick disconnect or 5s whichever was earlier,
before we move op sm from brick op stage to commit stage. This involves a race
where both the above mentioned events can happen 'concurrently' and result in
double free of the event context.

Change-Id: Ia369994448e71a052679d2373b8ab9177d56a541
BUG: 3700
Reviewed-on: http://review.gluster.com/626
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

glusterd: Fail volume 'modify' operations when rb is ongoing.

2011-10-24T13:17:34+00:00

add-brick, stop-volume, remove-brick are the operations that are explicitly
'failed' when attempted while replace-brick is in progress.

Change-Id: Ia8034177e03a9ab10f9e8d5c8bc417427a1218e3
BUG: 3738
Reviewed-on: http://review.gluster.com/631
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi 
Reviewed-by: Vijay Bellur

glusterd: Refactored rb subcmds code and fixed some minor issues.

2011-10-19T10:19:56+00:00

Change-Id: Ie14492451cab821e7ed60e68dbaff22d7d78fba9
BUG: 3709
Reviewed-on: http://review.gluster.com/609
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi 
Reviewed-by: Vijay Bellur

glusterd rebalance: ignore 'selinux' xattrs

2011-10-18T06:35:40+00:00

Change-Id: I145c12f529459f5c10ba1b8a28cb64ac07d2d2a9
BUG: 3721
Reviewed-on: http://review.gluster.com/605
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

mgmt/glusterd: send the duplicate brick info to the cli

2011-10-17T08:49:57+00:00

suppose one gives create volume from a peer whose bricks are
hostname:/a/b hostname:/a/b/c, then send that error information
to the cli.

Change-Id: Ic2149647f753fcf9218e468f13c52d0fc013a5d3
BUG: 2803
Reviewed-on: http://review.gluster.com/582
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

glusterd: Should not cleanup peerinfo too soon.

2011-10-17T05:59:10+00:00

friend_remove_cbk cleans up peerinfo and the unrefs the associated rpc_clnt
obj. When the cbk is run inside call_bail or saved_frames_unwind, we might end
up destroying the rpc_clnt and associated saved_frames_pool while we are still
using saved_frames to iterate through the frames.

Change-Id: I9c43797cb35104d35b011c26d773a0b375248f2d
BUG: 3511
Reviewed-on: http://review.gluster.com/513
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi 
Reviewed-by: Vijay Bellur

glusterd rebalance: remove stale temporary file if migration fails

2011-10-10T10:57:55+00:00

Change-Id: Ie13b0f2748b15c0359b7868460d4bc65ec05a217
BUG: 3576
Reviewed-on: http://review.gluster.com/552
Tested-by: Gluster Build System 
Reviewed-by: Jeff Darcy 
Reviewed-by: Vijay Bellur