glusterfs.git, branch v3.3.0qa14

cluster/afr: set the read child ctx only if the self-heal source is valid

2011-10-03T13:34:25+00:00

Change-Id: Ifdf0db71594ce526ad85c21103726798d9aceef4
BUG: 3639
Reviewed-on: http://review.gluster.com/556
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

core: made changes to return value of __is_root_gfid()

2011-10-03T05:08:02+00:00

now returns 'true(1)' is gfid is root, 'false(0)' if not.
earlier it was the inverse, which was bit confusing

Change-Id: Id103f444ace048cbb0fccdc72c6646da06631584
BUG: 3518
Reviewed-on: http://review.gluster.com/549
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

libglusterfs/syncop: do not rely on synctask set in makecontext

2011-10-02T08:31:18+00:00

Across glibc implementations, interpretation of argc/argv passed
to makecontext() is different. This patch does away with dependence
on such arguments passed to makecontext(). Instead,synctask reference
is retrieved from pthread_getspecific().

Change-Id: Ie01feaa0b7d430f8782c2f6805ccdf8026e401f4
BUG: 3636
Reviewed-on: http://review.gluster.com/547
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi 
Reviewed-by: Vijay Bellur

statedump: do not print the inode number in the statedump

2011-10-01T12:55:22+00:00

    Since gfid is used to uniquely identify a inode, in the statedump
    printing inode number is not necessary. Its suffecient if the gfid
    of the inode is printed. And do not print the the inodelks, entrylks
    and posixlks if the lock count is 0.

Change-Id: Idac115fbce3a5684a0f02f8f5f20b194df8fb27f
BUG: 3476
Reviewed-on: http://review.gluster.com/530
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi

glusterd: cleanup unneeded volumes after peer detach

2011-10-01T12:54:56+00:00

Performs cleanup on the detached peer and in the cluster after a
peer detach, and also adds a new check before starting detach.

Cleanup -
 On the detached peer, cleanup removes the entries of those volumes
on the peer that do not have all their bricks on it. This prevents
these stale volumes from being added to a new cluster when peer is
attached to one.
 In the cluster, all those volumes which have all their bricks on the
detached peer are removed.

Checks-
 Checks if all the peers in the cluster are online and connected,
 except the peer being detached, before starting detach. Using force
 will bypass this check and do detach.

Change-Id: I4fef9ea3cc72ce8c4ce0a82b4ee8a1663a502061
BUG: 1926
Reviewed-on: http://review.gluster.com/431
Tested-by: Gluster Build System 
Reviewed-by: Krishnan Parthasarathi

glusterd, cli: adds 'force' for 'peer detach'

2011-10-01T12:54:42+00:00

Adds add a 'force' option to 'peer detach' to forcefully detach a peer from a
cluster, even when the cluster contains volumes with bricks on the peer.

Change-Id: I134df51c16a07345c8869b318141d427b572eba5
BUG: 3549
Reviewed-on: http://review.gluster.com/429
Tested-by: Gluster Build System 
Reviewed-by: Krishnan Parthasarathi

distribute rebalance: preserve proper mode in destination

2011-09-30T07:57:05+00:00

* don't set 'sticky' and 'sgid' bits to 0 without checking if the
  source had those bits prior to rebalance.

Change-Id: Ia826cb3cfb55312cdbf00d3421f2bd06b3103ce6
BUG: 3656
Reviewed-on: http://review.gluster.com/541
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

rebalance process: propagate proper errors to user

2011-09-30T07:55:20+00:00

* cluster/distribute: while rebalance, differentiate between valid
  errors, validation check failures (may not be migrate failure),
  and success.

* mgmt/glusterd: differentiate the errors based on errno. If a valid
  error has happened, mark the rebalance status as failure, and
  stop the rebalnace crawl.

Change-Id: I2d7bd7b73d2b79bfaf892ad4364bc89830a0d5bb
BUG: 3656
Reviewed-on: http://review.gluster.com/540
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

locks: dump client pid and time of blocking/granting.

2011-09-30T07:50:04+00:00

Change-Id: Icaa919f3009fb70f6af9b95fceaf800f3beca447
BUG: 3662
Reviewed-on: http://review.gluster.com/532
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

cluster/afr: Don't unlock sh_frame on failure in algo

2011-09-30T07:47:48+00:00

Change-Id: I0ef541c1f387c397c345e3f2bc9a57f1eff282a1
BUG: 3647
Reviewed-on: http://review.gluster.com/527
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur