glusterfs-snapshot.git/tests/bugs, branch development

glusterd/snapshot: Snapshot create and delete changes

2014-03-06T09:31:23+00:00

With the snap driven approach, While creating the snapshot, We have to
mention the snap-name first and then the volumes to be associated with
that. Corresponding changes has been made in glusterd.

While deleting the snapshot, we have to mention only the snapname.
Corresponding changes has been made in glusterd.

CLI changes for the same can be found here:
http://review.gluster.org/#/c/6947/

Change-Id: I8bd8f471da5b728165da5f331faad3dde3486823
Signed-off-by: Vijaikumar M 
Reviewed-on: http://review.gluster.org/7123
Reviewed-by: Avra Sengupta 
Reviewed-by: Rajesh Joseph 
Tested-by: Rajesh Joseph

cli/snapshot : snapshot delete CLI changes.

2014-03-05T10:13:25+00:00

Syntax:
        gluster snapshot delete 

Change-Id: I5de7b9a79eeba12e4f0b8abfbe96a2db738f25c0
Signed-off-by: Sachin Pandit 
Reviewed-on: http://review.gluster.org/7144
Reviewed-by: Rajesh Joseph 
Tested-by: Rajesh Joseph

glusterd/snapshot: store location for snap driven changes

2014-03-04T06:58:23+00:00

Currently snapshot volfiles are stored at:
/vols//snaps/

With snap driven approach we need to store the volfiles at:
/snaps//

Change-Id: I8efdd5db29833b2b06b64a900cbb4c9b9a5d36b6
Signed-off-by: Vijaikumar M 
Signed-off-by: Sachin Pandit 
Reviewed-on: http://review.gluster.org/7006
Reviewed-by: Avra Sengupta 
Reviewed-by: Rajesh Joseph 
Tested-by: Rajesh Joseph

glusterd/Volume Lock: Corrupted Txn Id Fix

2014-03-04T06:23:10+00:00

Change-Id: Ic988ffeb26a49b4c6ac0d4a8ca33124f2192744c
BUG: 1064768
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/6997
Reviewed-by: Krishnan Parthasarathi 
Reviewed-by: Rajesh Joseph 
Tested-by: Rajesh Joseph

Snapshot: snap-max-limit implemented

2014-02-18T08:56:54+00:00

Added the check on snap-max-limit in snapshot_create_prevalidate. Now snapshot
creation will fail if snap count reaches max limit.

Change-Id: I5b1cf8441f02c32085d2f6f5fd8902cb61031af5
BUG: 1049834
Author:    Joseph Fernandes 
Signed-off-by: Joseph Fernandes 
Signed-off-by: Rajesh Joseph 
Reviewed-on: http://review.gluster.org/6981
Reviewed-by: Raghavendra Bhat

glusterd/snapshot: Use snap uuid to create lvm snapshot

2014-02-13T14:18:15+00:00

Using snap uuid to create lvm snapshot will solve the problem of having
'-' in the snap name or snap name is too long.

Change-Id: If204f02a8f5de599fb409d06c7893ef3542a6300
BUG: 1045333
Signed-off-by: Vijaikumar M 
Reviewed-on: http://review.gluster.org/6709
Reviewed-by: Rajesh Joseph 
Tested-by: Rajesh Joseph

glusterd/snapshot : Making the snap mount read-only.

2014-02-05T11:54:11+00:00

Basically loading the read-only translator on the server side,
during the snapshot create.

Change-Id: I88dcce85b5f3f00e438f08165a8177b064f004fe
BUG: 1040934
Signed-off-by: Sachin Pandit 
Reviewed-on: http://review.gluster.org/6694
Reviewed-by: Rajesh Joseph 
Tested-by: Rajesh Joseph

fuse: Check the return status from state->resolve_now

2013-11-15T01:47:59+00:00

Change-Id: I85fc6dd393449d365bb908b38c2827b58cb08171
BUG: 1030208
Signed-off-by: Vijaykumar M 
Reviewed-on: http://review.gluster.org/6262
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

glusterd: Release big-lock after log-rotate handler returns

2013-10-31T05:19:13+00:00

... so that subsequent volume commands don't block waiting forever,
for the lock to be released.

Change-Id: I24b5ec47f6982900ab74ff1b492d523f31ecfb7f
BUG: 1022055
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/6122
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

glusterd : Improved quota volume reset command

2013-10-28T18:39:21+00:00

Quota volume reset command without "force"
option fixed, doesn't fail anymore. It resets
unprotected fields and not the protected ones.

Also, an appropriate message is provided to the user
for the following cases :
1. only unprotected fields are reset, "force" option
should be used to reset protected fields.
2. Both protected and unprotected fields are reset.
3. No field was reset, "force" option required.

Test case for the same also added.

Change-Id: I24e8f1be87b79ccd81bf6f933e00608b861c7a16
BUG: 1022905
Signed-off-by: Anuradha 
Reviewed-on: http://review.gluster.org/6135
Tested-by: Gluster Build System 
Reviewed-by: Krishnan Parthasarathi 
Reviewed-by: Vijay Bellur