glusterfs.git/xlators/mgmt/glusterd/src/glusterd-brick-ops.c, branch v3.3.2qa2

glusterd: Set errstr for duplicate add-brick

2012-08-02T03:39:18+00:00

Sets op_errstr when add-brick is given a duplicate brick.

BUG: 832293
Change-Id: I2d6d13b2ca29615678902b56e6b394ea05f37923
Signed-off-by: Kaushal M 
Reviewed-on: http://review.gluster.com/3585
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

glusterd: Fixed glusterd_brick_create_path algo.

2012-05-19T10:27:20+00:00

- check if any prefix of the brick path has "trusted.gfid"
  or "trusted.glusterfs.volume-id" set.
- set trusted.glusterfs.volume-id on the bricks as soon as
  its induction into the volume is settled. Earlier, the setting of
  "volume-id" used to happen during the first run of the brick process,
  leaving of window for bricks part of one volume to be (ab)used by another
  volume inadvertently.
- removed creation of brick directory (if missing), during start volume force.
  This is to avoid directory creation as part 'force'ful starting of volume
  and leave the responsibility with the user, who understands the
  'availability' of the export directory (brick) better.

Change-Id: I4237ec4ea7a4e38a7501027e7de7112edd67de8c
BUG: 812214
Signed-off-by: Krishnan Parthasarathi 
Reviewed-on: http://review.gluster.com/3280
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur 
Reviewed-on: http://review.gluster.com/3313

glusterd: remove-brick: add more error handling

2012-05-08T09:40:58+00:00

with this, we can make sure, all wrong patterns in CLI can be
reported with proper message back to user, instead of resulting
in an wrong volume type.

Change-Id: Ib461956dd7d51f7f81c19c27112d44c2adb3a66d
Signed-off-by: Amar Tumballi 
BUG: 803711
Reviewed-on: http://review.gluster.com/3278
Tested-by: Gluster Build System 
Reviewed-by: Kaushal M 
Reviewed-by: Vijay Bellur

glusterd (remove-brick): fix data-loss issue

2012-04-18T13:25:39+00:00

* when more than one brick (more than one distribute subvolume)
  was removed using single command, rebalance process used to
  get started only on one node, causing data-loss when 'commit'
  was done, because the brick's data was not migrated at all.
  Fixed the logic of validating rebalance required in remove-
  brick case.

Change-Id: I3a90ff9f9593e5215110a3a0974bb97e7271f910
Signed-off-by: Amar Tumballi 
BUG: 812770
Reviewed-on: http://review.gluster.com/3173
Tested-by: Gluster Build System 
Reviewed-by: Jeff Darcy 
Reviewed-by: Shishir Gowda

glusterd/remove-brick: Replace ABORT with STOP

2012-04-13T07:46:59+00:00

Remove-brick stop now invokes rebalance stop. This leads
to a graceful stop of decommissioning.
The volfile is also updated (removal of decommission)

Change-Id: I5a8f725c0f54439b810ce32d988c21c02229c703
BUG: 811513
Signed-off-by: shishir gowda 
Reviewed-on: http://review.gluster.com/3126
Reviewed-by: Amar Tumballi 
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

glusterd/remove-brick: Remove support for pause option

2012-04-13T07:26:33+00:00

Decommissioning through rebalance has no pause option.

Change-Id: I90f165cdb2eccfaefc99365ae4b48d81320fb753
BUG: 811459
Signed-off-by: shishir gowda 
Reviewed-on: http://review.gluster.com/3123
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi

glusterd: Added volume-id to 'op' dictionary

2012-04-13T06:07:08+00:00

Volume-id passed in op dictionary would help detect possible split brains
among peers in a cluster. The idea is to check if the volume's id and
the vol-id that was passed are equal.
ie, same volume name, but different volume id indicate that glusterd
'metadata' of one of the participating peers is stale or there is
a split brain.

This is over and above the existing checksum based validation of peer
supplied cluster 'metadata' (ie, volume info file).

Change-Id: I1049ef249e417e540ccb4243e450f92fcd0f46f9
BUG: 797734
Signed-off-by: Krishnan Parthasarathi 
Reviewed-on: http://review.gluster.com/3083
Tested-by: Gluster Build System 
Reviewed-by: Jeff Darcy 
Reviewed-by: Vijay Bellur

remove-brick: Abort should revert volume changes

2012-04-06T10:38:49+00:00

Also, enhanced gluster cli output.

Signed-off-by: shishir gowda 
Change-Id: I520ccfb63b3568a2e6654d8a5fbf265b9b903af1
BUG: 788524
Reviewed-on: http://review.gluster.com/3082
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

glusterd: remove-brick validation behavior fix

2012-03-31T14:39:00+00:00

earlier one of the major validation case was missed if user provided
a 'replica N' option for remove-brick where N is already existing
replica count of the volume. This would have left the volume in
inconsistent state, eventually crashing glusterd. Now fixed.

Change-Id: I418f3bbb983d36aa51214c616a887e5a3ee98e74
Signed-off-by: Amar Tumballi 
BUG: 803711
Reviewed-on: http://review.gluster.com/3050
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

glusterd: add-brick: give proper reason in few error cases

2012-03-29T15:00:33+00:00

had missed few 'else' cases, which were needed to send the right
error message to the user regarding the reason for failure.

Change-Id: I42d92782f4dec6f6bdffd42df254b7f38a715e36
Signed-off-by: Amar Tumballi 
BUG: 772544
Reviewed-on: http://review.gluster.com/3032
Tested-by: Gluster Build System 
Reviewed-by: Jeff Darcy 
Reviewed-by: Vijay Bellur