diff options
author | Sunny Kumar <sunkumar@redhat.com> | 2017-08-16 14:04:45 +0530 |
---|---|---|
committer | Amar Tumballi <amarts@redhat.com> | 2017-10-23 10:05:02 +0000 |
commit | 2b3b3edee2d849b4aee314048987dc995d9679a1 (patch) | |
tree | 9523ebf6ad226735b9a2eac40c2701653be307bf /glusterfs.spec.in | |
parent | 87bd25b64ae34cce95e87e724acfeab4c13d60a4 (diff) |
snapshot: Issue with other processes accessing the mounted brick
Added code for unmount of activated snapshot brick during snapshot
deactivation process which make sense as mount point for deactivated
bricks should not exist.
Removed code for mounting newly created snapshot, as newly created
snapshots should not mount until it is activated.
Added code for mount point creation and snapshot mount during snapshot
activation.
Added validation during glusterd init for mounting only those snapshot
whose status is either STARTED or RESTORED.
During snapshot restore, mount point for stopped snap should exist as
it is required to set extended attribute.
During handshake, after getting updates from friend mount point for
activated snapshot should exist and should not for deactivated
snapshot.
While getting snap status we should show relevent information for
deactivated snapshots, after this pathch 'gluster snap status' command
will show output like-
Snap Name : snap1
Snap UUID : snap-uuid
Brick Path : server1:/run/gluster/snaps/snap-vol-name/brick
Volume Group : N/A (Deactivated Snapshot)
Brick Running : No
Brick PID : N/A
Data Percentage : N/A
LV Size : N/A
Fixes: #276
Change-Id: I65783488e35fac43632615ce1b8ff7b8e84834dc
BUG: 1482023
Signed-off-by: Sunny Kumar <sunkumar@redhat.com>
Diffstat (limited to 'glusterfs.spec.in')
0 files changed, 0 insertions, 0 deletions