| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
|\
| |
| |
| |
| |
| | |
* changes:
glusterd/snapshot: Added trace statements and handled snapshot create commit failure.
glusterd/mgmt: Adding synctasked flag to initiate multiple volume locks.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
failure.
Also handles empty string(not NULL) in gd_syncop_mgmt_brick_op()
and adds "Snapshot" in operation list used for printing op
during logging.
Change-Id: Icac9dce6bf1c087ab2aace9953e2af3a0fb81be6
Signed-off-by: Avra Sengupta <asengupt@redhat.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Setting 'is_synctasked' as gf_true for glusterd_mgmt_v3_initiate_snap_phases()
to initiate multiple volume locks.
Change-Id: Ib225fbac42b5e9cf9f3af0083d33ec49a1b87964
Signed-off-by: Avra Sengupta <asengupt@redhat.com>
|
|/
|
|
|
|
|
|
| |
Currently if the queue length is large, the response to glusterd
will get blocked
Change-Id: I713e8803a087b5131a35050ca027165562d7e1b7
Signed-off-by: shishir gowda <sgowda@redhat.com>
|
|\
| |
| |
| | |
development
|
| |
| |
| |
| |
| | |
Change-Id: I97a417eeebc7ac6193c2de7ad59eb8f7f4f79fe6
Signed-off-by: shishir gowda <sgowda@redhat.com>
|
|/
|
|
|
| |
Change-Id: Ib39b244fd29d837a0640dba505eeff42e0a22f9a
Signed-off-by: shishir gowda <sgowda@redhat.com>
|
|
|
|
| |
Signed-off-by: shishir gowda <sgowda@redhat.com>
|
|
|
|
|
|
|
|
| |
snapshot taken first should be displayed first in
the snapshot list output.
Change-Id: Idd1b2374f842b3b70edfb3024094d4d81fbb1163
Signed-off-by: Sachin Pandit <spandit@redhat.com>
|
|
|
|
|
| |
Change-Id: I0ba50ba2963edf8d890a2dc78d48d42db7f71ae2
Signed-off-by: shishir gowda <sgowda@redhat.com>
|
|
|
|
|
|
|
|
|
| |
If user tries to list the snap details of volumes
which does not exist, then corresponding error
message is displayed.
Change-Id: I205738be3dc632ccb074b639a2088cdd44aa35a7
Signed-off-by: Sachin Pandit <spandit@redhat.com>
|
|
|
|
|
|
|
| |
Also fixes snapshot config output
Change-Id: Ia50d94492009cf73dbb99ba20117b9fa4c41048a
Signed-off-by: Avra Sengupta <asengupt@redhat.com>
|
|
|
|
|
|
|
|
|
| |
GL-205: Gluster snapshot create crashing.
runner-arg should have NULL as the last argument.
Change-Id: I1bd0090160b53a04a8073c31d91fb77f96f625dc
Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
|
|
|
|
|
| |
Change-Id: I58a743c92bbd021c3a42c5184ba8acf4db48878a
Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
|
|
|
|
|
| |
Change-Id: Idafe3cdba149c2a66b89fb3fe0d4d3791d9d089c
Signed-off-by: Sachin Pandit <spandit@redhat.com>
|
|
|
|
|
|
|
| |
* op_errstr is allocated and set while returning if there is any error
Change-Id: I6e0de80d611aeeee3d25e8c20ab49b8ef42b0bf5
Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
|
|
|
|
|
| |
Change-Id: I3404106a7e4fa7d32b1d5824e079040d2ed8d76b
Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
GL-31: Ability to restore snapshot
Implemented snapshot restore for thin logical volume. As of now snapshot
restore for CG is not tested. Testing for snapshot restore of a volume
is done by changing the snapshot create process to create a thick snapshot.
This is done because --merge option to restore thin volume is not working in
the latest kernel.
Change-Id: Ia3ded7e6c4da5957a74e269a25ba3200e6fb2d8b
Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
|
|
|
|
|
| |
Change-Id: Ia755e5c4af84827cc9b8876054cc48cfdc598876
Signed-off-by: shishir gowda <sgowda@redhat.com>
|
|
|
|
|
| |
Change-Id: I16b17ca60b5f9b34b7d238d8a3424a3b7a1dc435
Signed-off-by: shishir gowda <sgowda@redhat.com>
|
|
|
|
|
|
|
|
| |
Also refactored code in glusterd for create command
Additionally, removed brick-op func from mgmt_iniate_all_phases
Change-Id: Iddcc332009c5716adee7f2b04c93b352fb983446
Signed-off-by: shishir gowda <sgowda@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Change in Naming convention:
"snap_details", "snap_count" and so on
is replaced by "snap-details", "snap-count" so on.
Total snapcount introduced.
Separate check is made for repeated Volume Name
Ex : "gluster snapshot list vol1 vol2 vol1 vol2"
is considered as "gluster snapshot list vol1 vol2"
*This is still a work in progress*
*have to test CG list once CG Store is ready*
Change-Id: I45e2904eb8bdbf78de8665f20ba9605c38320307
Signed-off-by: Sachin Pandit <spandit@redhat.com>
|
|
|
|
|
|
| |
Change-Id: I9d600b4d971b7fdcd54da50e4a069eab19648fa6
Original-author: Rajesh Joseph <rajeshatredhat@redhat.com>
Signed-off-by: shishir gowda <sgowda@redhat.com>
|
|
|
|
|
|
|
| |
Added new XDR types for all the snapshot command.
Change-Id: I46c02ea8e9c81c7967a773386c4b77b5eb6d5075
Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
|
|
|
|
|
|
|
|
| |
* Now, reply submission to the client is avoided even if the
fop is not barriered
Change-Id: I9d503935c4d851f5dd0e8e4be0fea9c92e636ff3
Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
|
|
|
|
|
| |
Change-Id: I8b88fe94d0f9ee1089cafdda037abcf2f7a180ca
Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
|
|
|
|
|
| |
Change-Id: I30cbbeb135c2d0a780e9e414ac0a96739e25647b
Signed-off-by: shishir gowda <sgowda@redhat.com>
|
|
|
|
|
| |
Change-Id: Iafbd0ec95de0c41455fb79953fb4bb07721334a5
Signed-off-by: shishir gowda <sgowda@redhat.com>
|
|
|
|
|
| |
Change-Id: I54db2fa67ebb6b57629f9536c296fbae07a1d159
Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
|
|
|
|
|
| |
Change-Id: I6ec888a5553ad29ded032c02c80dd940b2aae007
Signed-off-by: shishir gowda <sgowda@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is still a work in progress.
As of now, these things are done:
* Take the snapshot of the backend brick
* Create the new volume for the snapshot
* Create the brick and the client volfiles
* Store the snapshot related info in /var/lib/glusterd
* Create the snap object representing the snapshot
TODO:
Start the brick processes for the snapshot
Change-Id: I26fbb0f8e5cf004d4c1dbca51819bab1cd1bac15
Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
|
|
|
|
|
|
|
|
| |
Handles snapshot list command issued by cli. Details of all the snapshots
will be sent back to the caller in required format.
Change-Id: I01e512290548007c06e90b40a59cdde048fab954
Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Introduced a new store for storing snapshot list for a given volume.
$GLUSTERD_INSTALL_PATH/vols/<volname>/snap_list.info
$GLUSTERD_INSTALL_PATH/vols/<volname>/snaps/
$GLUSTERD_INSTALL_PATH/vols/<volname>/snaps/<snap-name>/info <-snapshot volume info
$GLUSTERD_INSTALL_PATH/vols/<volname>/snaps/<snap-name>/bricks <-snapshot volume brick dir
$GLUSTERD_INSTALL_PATH/vols/<volname>/snaps/<snap-name>/bricks/<infos>
<-snapshot volume brick info files
store delete options
TODO -
$GLUSTERD_INSTALL_PATH/CG/ <-place holder for all cg's
.../CG/<cg-name>/info <- per cg information placeholder
Change-Id: I1f9fd8ff7cc0682d05b33965736a43dca6adb3e9
Signed-off-by: shishir gowda <sgowda@redhat.com>
|
|
|
|
|
|
|
| |
Also linking snap create command to mgmt_v3
Change-Id: If2ed29be072e10d0b0bd271d53e48eeaa6501ed7
Signed-off-by: Avra Sengupta <asengupt@redhat.com>
|
|
|
|
|
|
|
|
|
| |
Defining separate interfaces for every phase to make use
of the rpcs and providing set of integrated interfaces for
commands to consume
Change-Id: I6d464326c5a8b5875a7c2539c9df072b23fe61a9
Signed-off-by: Avra Sengupta <asengupt@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
glusterd mgmt_v3 is nothing but a complete synctask approach
for glusterd to function. The commands making use of this
won't be using the op-state machine to inject events and
will be using the synctask framework to perform operations
across all nodes in the cluster. This patch defines the
program and the handlers used.
Change-Id: Ibff2c62b0187c40cdea7254c85786297bba60372
Signed-off-by: Avra Sengupta <asengupt@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
$ gluster snapshot help
snapshot help - display help for snapshot commands
snapshot create <volnames> [-n <snap-name/cg-name>] [-d <description>] - Snapshot Create.
$ gluster snapshot create vol1
snapshot create: ???: snap created successfully
$ gluster snapshot create vol1 vol2
snapshot create: ???: consistency group created successfully
(The ??? will be replaced by the glusterd snap create command with the
generated snap-name or cg-name)
$ gluster snapshot create vol1 vol2 -n CG1
snapshot create: CG1: consistency group created successfully
$ gluster snapshot create vol1 -n snap1 -d Description
snapshot create: snap1: snap created successfully
$ gluster snapshot create vol1 -n snap1 -d "Description can have -d within quotes"
snapshot create: snap1: snap created successfully
$ gluster snapshot create vol1 -n snap1 -d Description cant have -d without quotes
snapshot create: failed: Options(-n/-d) are not valid descriptions
Usage: snapshot create <volnames> [-n <snap-name/cg-name>] [-d <description>]
$ gluster snapshot create vol1 -n "Multi word snap name" -d Description
snapshot create: failed: Invalid snap name
Usage: snapshot create <volnames> [-n <snap-name/cg-name>] [-d <description>]
$ gluster snapshot create vol1 -d Description -n "-d"
snapshot create: failed: Options(-n/-d) are not valid snap names
Usage: snapshot create <volnames> [-n <snap-name/cg-name>] [-d <description>]
$ gluster snapshot create vol1 -d -n snap1
snapshot create: failed: No description provided
Usage: snapshot create <volnames> [-n <snap-name/cg-name>] [-d <description>]
Change-Id: I74b5a8406d72282fbb7ba7d07e0c7fe395148d38
Signed-off-by: Avra Sengupta <asengupt@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Barriering allows cbk's responses to be held back until either a
timeout or a un-barrier event is received.
The event is triggered by a brick-op.
barrier-timeout, barrier-queue-lenght, and barrier-fops are currently
exposed as a xlator-options only
Change-Id: Ifb62d5b2bd2fbb35aca3b537e534156c877ce3a6
Signed-off-by: shishir gowda <sgowda@redhat.com>
|
|
|
|
|
| |
Change-Id: I03ff9e8094e7e36b28b521380949c7e9044c2e4e
Signed-off-by: shishir gowda <sgowda@redhat.com>
|
|
|
|
|
|
|
|
| |
API's for creating, adding, finding, removing snapshots
and consistency groups are provided.
Change-Id: Ic28da69a075b062aefdf14754c68259ca58bd427
Signed-off-by: shishir gowda <sgowda@redhat.com>
|