| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
This changes includes snap-driven based list and info changes:
Change-Id: Ie82a2a3c785baa36892ca0cd97a958a2ae819d4c
Signed-off-by: Vijaikumar M <vmallika@redhat.com>
Signed-off-by: Sachin Pandit <spandit@redhat.com>
Reviewed-on: http://review.gluster.org/7139
Reviewed-by: Avra Sengupta <asengupt@redhat.com>
Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
Tested-by: Rajesh Joseph <rjoseph@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 <vmallika@redhat.com>
Reviewed-on: http://review.gluster.org/7123
Reviewed-by: Avra Sengupta <asengupt@redhat.com>
Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
Tested-by: Rajesh Joseph <rjoseph@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently snapshot volfiles are stored at:
<workdir>/vols/<volname>/snaps/<snapvol>
With snap driven approach we need to store the volfiles at:
<workdir>/snaps/<snapname>/<snapvol>
Change-Id: I8efdd5db29833b2b06b64a900cbb4c9b9a5d36b6
Signed-off-by: Vijaikumar M <vmallika@redhat.com>
Signed-off-by: Sachin Pandit <spandit@redhat.com>
Reviewed-on: http://review.gluster.org/7006
Reviewed-by: Avra Sengupta <asengupt@redhat.com>
Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
Tested-by: Rajesh Joseph <rjoseph@redhat.com>
|
|
|
|
|
|
|
|
|
|
| |
Change-Id: Ic988ffeb26a49b4c6ac0d4a8ca33124f2192744c
BUG: 1064768
Signed-off-by: Avra Sengupta <asengupt@redhat.com>
Reviewed-on: http://review.gluster.org/6997
Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
Tested-by: Rajesh Joseph <rjoseph@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 <josferna@redhat.com>
Signed-off-by: Joseph Fernandes <josferna@redhat.com>
Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
Reviewed-on: http://review.gluster.org/6981
Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
|
|
|
|
|
|
|
|
|
| |
Change-Id: I886a003c1bd9959105eab64a098b66a7303d4bba
Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
Reviewed-on: http://review.gluster.org/7001
Reviewed-by: Sachin Pandit <spandit@redhat.com>
Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
Tested-by: Rajesh Joseph <rjoseph@redhat.com>
|
|
|
|
|
|
|
|
| |
Change-Id: I60b635f275498b285aa34702ce6ca41bfb7e01a0
Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
Reviewed-on: http://review.gluster.org/6995
Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
Tested-by: Rajesh Joseph <rjoseph@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 <vmallika@redhat.com>
Reviewed-on: http://review.gluster.org/6709
Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
Tested-by: Rajesh Joseph <rjoseph@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
supported
To check if setactivationskip is supported or not, we run lvcreate --help
and look for the setactivationskip flag, and accordingly issue lvcreate
with or without the said flag.
Change-Id: Ief349674ea3f7ceff6b7051b1a5104257e547ce2
Signed-off-by: Avra Sengupta <asengupt@redhat.com>
Reviewed-on: http://review.gluster.org/6776
Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
Tested-by: Rajesh Joseph <rjoseph@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Basically loading the read-only translator on the server side,
during the snapshot create.
Change-Id: I88dcce85b5f3f00e438f08165a8177b064f004fe
BUG: 1040934
Signed-off-by: Sachin Pandit <spandit@redhat.com>
Reviewed-on: http://review.gluster.org/6694
Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
Tested-by: Rajesh Joseph <rjoseph@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
unmounting.
Change-Id: Idf0cf63429212142795e1aeb4fd4962b51620426
BUG: 1049353
Signed-off-by: Sachin Pandit <spandit@redhat.com>
Reviewed-on: http://review.gluster.org/6772
Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
Reviewed-by: Avra Sengupta <asengupt@redhat.com>
Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
Tested-by: Rajesh Joseph <rjoseph@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Instead performing store on all the snaps of the volume when a new snap
is created, store only the new snap's info. Otherwise with more and more
snapshots in the volume, time creation for new snapshot becomes very large
as glusterd has to store all the snapshots related info everytime (that too by
doing fsyncs)
Change-Id: I0e005d1d4c044b07a8abde8e6ba55e66a1bbd590
BUG: 1059146
Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
Reviewed-on: http://review.gluster.org/6841
Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
Tested-by: Rajesh Joseph <rjoseph@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Introducing a wrapper function glusterd_txn_opinfo_init(),
to initialize the opinfo to be set in the txn_id engine.
Removed glusterd_op_fini_ctx() as the txn opinfo should
only be cleared by glusterd_clear_txn_opinfo().
Change-Id: I17e85a162d6a3bca79941f8603d0c2b579f0d194
Signed-off-by: Avra Sengupta <asengupt@redhat.com>
|
|\
| |
| |
| | |
into development
|
| |
| |
| |
| |
| |
| |
| |
| | |
On receiving peer disconnect, release volume locks held
by the disconnected peer
Change-Id: I0e36ba2fba4761225092ce2fb7b9b3c2d2dca0ad
Signed-off-by: Avra Sengupta <asengupt@redhat.com>
|
|/
|
|
|
|
|
|
| |
Move the code part that need to executed at the origin glusterd to a
seperate function.
Change-Id: Ieb53fbd4fb12e3e4d5087db306be37616657ee04
Signed-off-by: Vijaikumar M <vmallika@redhat.com>
|
|
|
|
|
| |
Change-Id: I2d07717ee01751e481571ce420b0f84711ea9597
Signed-off-by: Sachin Pandit <spandit@redhat.com>
|
|
|
|
|
|
|
|
|
| |
Creating a separate list for snaps taken, as cluttering
snaps in the volume list does not look neat.
Change-Id: Ida4a183e95e8694b85ebb5a680d06b7d29a460a0
BUG: 1040947
Signed-off-by: Sachin Pandit <spandit@redhat.com>
|
|
|
|
|
|
| |
Change-Id: I9663342e49073a172667220d4839b2beb65ffc0e
BUG: 1040947
Signed-off-by: Sachin Pandit <spandit@redhat.com>
|
|
|
|
|
|
|
| |
Some changes were missed in resolving conflict in the restore patch.
Change-Id: Ie0cf01237bf975027056c10bb3681e122334f83e
Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
|
|\
| |
| |
| | |
of vol delete." into development
|
| |
| |
| |
| |
| |
| |
| | |
delete.
Change-Id: I5056c0e46015278bd8d0c39307e4671fd4259961
Signed-off-by: Avra Sengupta <asengupt@redhat.com>
|
|/
|
|
|
|
|
|
|
|
|
| |
Implemented gluster snapshot restore feature. The restore is done
by replacing the origin volume with the snap volume.
TODO: After the restore the snapshot volume should be deleted. As of
now the deletion work is pending.
Change-Id: Ib137fb6bb84a74030607ffa47f89cd705dc7e1ff
Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1)Write the CG Name in the "snap_list.info"
file, so that CG Name is not lost when we restart the
glusterd.
2)Fixes the issue where Description given for CG,
as a part of create command, was getting stored
as snap description rather than CG Description.
3)Fixes the problem with glusterd restart
when we have multiple words in Snap Descripition
Change-Id: I3129c53d1ec54dd170ca1300583f278f58c4e0e2
BUG: 1044476
Signed-off-by: Sachin Pandit <spandit@redhat.com>
|
|
|
|
|
|
|
|
| |
Also block operation on response aggregation errors.
Change-Id: I641ddc98d986fd44627d790ab84488a6b849f807
BUG: 1043792
Signed-off-by: Avra Sengupta <asengupt@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
volume locks
The synctasked volume lock function was locking every node with
it's own UUID, instead of received UUID, which resulted in deadlock
when multiple snapshot commands were executed.
Change-Id: Ida76da1a057eae04178c202d626f9c1e671c1fee
BUG: 1043862
Signed-off-by: Avra Sengupta <asengupt@redhat.com>
|
|
|
|
|
| |
Change-Id: Icdd20825f51a01f4186841639fb645cb56a2fd12
Signed-off-by: Avra Sengupta <asengupt@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
snap-max-hard-limit.
This patch also prohibits configuration of snap-max-hard-limit
and snap-max-soft-limit for snap volumes. Also displaying the
snapshot configs by reading data only from local node, as all
config data will be in sync across the cluster.
Change-Id: I635b925c02ed5b108cd10c7193b154ad82d5afad
BUG: 1043792
Signed-off-by: Avra Sengupta <asengupt@redhat.com>
|
|
|
|
|
|
|
|
|
| |
Note: Manually adding this patch again as this patch got missed in
git reset option done on remote development branch
Change-Id: I9e81c5ec003c1e1722d0fcb27dd87c365ee43ff4
Signed-off-by: Avra Sengupta <asengupt@redhat.com>
Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
CG ID was not getting initiated during snapshot create,
hence there was problem in listing the CG ID and CG Name.
Note: Manually adding this patch again as this patch got missed in
git reset option done on remote development branch
Change-Id: I81951b42292912c98bab5964fc732b630ff66d14
BUG: 1040435
Signed-off-by: Sachin Pandit <spandit@redhat.com>
Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Till now we were generation a new uuid for a snap, that uuid was
brick id, so the snap uuid was different for different nodes. Now
we are copying the snap volume id to snap uuid so that it is
unique across nodes.
Note: Manually adding this patch again as this patch got missed in
git reset option done on remote development branch
Change-Id: Icb80caca9672b82de1b2129af47540c651a034ec
Signed-off-by: Sachin Pandit <spandit@redhat.com>
Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
|
|
|
|
|
|
|
| |
snap volumes
Change-Id: I97f59fcf1e78ded35fd15996d587ecd043c7dc17
Signed-off-by: Avra Sengupta <asengupt@redhat.com>
|
|
|
|
|
|
|
| |
Also fixes peer rejects on glusterd restart
Change-Id: I1671416c1f3fd2afea450cc3b4c632de187351ca
Signed-off-by: Avra Sengupta <asengupt@redhat.com>
|
|
|
|
|
| |
Change-Id: Icdb66c89acdd043d0d6368c48ce2e01b1a40966f
Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
|
|
|
|
|
| |
Change-Id: I277a70f732666d047ba5dff7a7e6925e0679741b
Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
| |
in volume status
Added a parent_volname member in glusterd_volinfo_ structure
to help point the snap vol to the parent volname. Using this
to fetch the pidfile location during volume status.
Change-Id: I30a16646561394d0f7d16f66abff14c425f31f06
Signed-off-by: Avra Sengupta <asengupt@redhat.com>
|
|
|
|
|
| |
Change-Id: I9f53bd4d83794c69c54e4a03f59425a1ca6a4ac3
Signed-off-by: Avra Sengupta <asengupt@redhat.com>
|
|
|
|
|
| |
Change-Id: I37eb7ab12767fdd11aa2e58441d26e6d6d9dd245
Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
|
|
|
|
|
| |
Change-Id: I6137ecb0dbbd37af81433c415568dfede1d740a6
Signed-off-by: Avra Sengupta <asengupt@redhat.com>
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Instead of using mount api to mount the snap device, use runner apis
to execute the mount command which mounts the snap device.
Change-Id: I8cf1fd4ade44d35dcd48c93fab10f5bea7f96f73
Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fetching snap mount path per brick during pre-validate
and aggregating it before commit to generate all brick
volfiles and all client volfiles on all nodes.
Added changes to propagate the same cg-id by generating
it in pre-validate and sending the same to all the nodes
during commit
Also fixed volume-id mismatches caused in snap-volumes
leading to failures of volume status
Change-Id: I0b8ed81ac93077cd50313e6eeed00f71932cf2ac
Signed-off-by: Avra Sengupta <asengupt@redhat.com>
Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
|
|
|
|
|
| |
Change-Id: I98fcd25e80b1b39e0292eae059e2d624ca9094fb
Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
|
|
|
|
|
| |
Change-Id: I94b5f6e00be7d1ff0c454e291c779dae7b423748
Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
|
|\
| |
| |
| | |
development
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In RHEL ACTIVATION_SKIP flag is set by default. Using
'--setactivationskip n' during lvcreate activates the
logical volumes upon creation.
Change-Id: I5a17afdd5a01fd0354d977bc4e43b35660289db9
Signed-off-by: Avra Sengupta <asengupt@redhat.com>
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
This patch fixes the below mentioned issue.
Snapshot list : Listing number of snaps available.
Display proper message if snapshot not present.
Change-Id: Iabfc47430a9c89fb5114e33e9feb7ef21973fc6a
Signed-off-by: Sachin Pandit <spandit@redhat.com>
|
|/
|
|
|
| |
Change-Id: I8fafb19c2c13caac2a509c36f99d2dd782865b13
Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Suppose a volume's brick has the path /export/brick/vol/dir and lvm
of that brick is mounted at /export. Now snap of that brick is
taken, and is mounted on a path (say /run/gluster/snaps/<snapname>)
While creating the brick for the snap volume, /run/gluster/snaps/<snapname>
(i.e the mount point of the snap lvm) should not be used as the export
directory. The directory path remaining after the mount point of the
original lvm should be appended to the snap lvm mounted path and
should be used as the export directory
(ex: /run/gluster/snaps/<snapname>/brick/vol/dir in this case).
Its because the volume-id of the original volume and other extended
attributes wont be set on the root. It will be in the same path as the
original lvm.
Change-Id: I832dac8478eba1a318bdbcdf6cd8bf55b2a3261d
Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
|