Bug 1089531 - DHT + Snapshot :- Snapshot creation should fail when brick is down
Summary: DHT + Snapshot :- Snapshot creation should fail when brick is down
Keywords:
Status: CLOSED DUPLICATE of bug 1089527
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: snapshot
Version: rhgs-3.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: ---
Assignee: rjoseph
QA Contact: amainkar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-20 12:24 UTC by Rachana Patel
Modified: 2016-09-17 12:56 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-14 10:58:58 UTC
Embargoed:


Attachments (Terms of Use)

Description Rachana Patel 2014-04-20 12:24:12 UTC
Description of problem:
-------------------------

As per the design doc [ https://forge.gluster.org/snapshot/pages/Home ]

"If any of the brick is down while taking snapshot then snapshot creation will fail. If force option is provided and quorum at server is met then snapshot creation will succeed if any bricks are down.."

But able to create Snap of Distributed volume when one brick was down.




Version-Release number of selected component (if applicable):
-------------------------------------------------------------
3.5qa2-0.340.gitc193996.el6_5.x86_64

How reproducible:
always

Steps to Reproduce:
1. created distributed volume having four brick. Start that volume and mount it
2. bring one brick down by killing brick process
3. take snap of that volume and its successful.

[root@OVM3 ~]# gluster v status dht1
Status of volume: dht1
Gluster process						Port	Online	Pid
------------------------------------------------------------------------------
Brick 10.70.35.13:/brick1				49152	Y	18048
Brick 10.70.35.54:/brick1				49152	Y	17629
Brick 10.70.35.71:/brick1				49152	Y	18199
Brick 10.70.35.159:/brick1				49152	Y	17610
NFS Server on localhost					2049	Y	18306
NFS Server on 10.70.35.159				2049	Y	18256
NFS Server on 10.70.35.71				2049	Y	18212
NFS Server on 10.70.35.54				2049	Y	18258
 
Task Status of Volume dht1
------------------------------------------------------------------------------
There are no active volume tasks
 
[root@OVM3 ~]# kill -9 18048
[root@OVM3 ~]# gluster v status dht1
Status of volume: dht1
Gluster process						Port	Online	Pid
------------------------------------------------------------------------------
Brick 10.70.35.13:/brick1				N/A	N	18048
Brick 10.70.35.54:/brick1				49152	Y	17629
Brick 10.70.35.71:/brick1				49152	Y	18199
Brick 10.70.35.159:/brick1				49152	Y	17610
NFS Server on localhost					2049	Y	18306
NFS Server on 10.70.35.159				2049	Y	18256
NFS Server on 10.70.35.54				2049	Y	18258
NFS Server on 10.70.35.71				2049	Y	18212
 
Task Status of Volume dht1
------------------------------------------------------------------------------
There are no active volume tasks
 
[root@OVM3 ~]# gluster snapshot create snap1 dht1
snapshot create: snap1: snap created successfully


Actual results:
Able to create Snap event hough brick is down


Expected results:
As per design doc, Snap creation should fail in case of brick down (for Distributed Volume)

Additional info:

Comment 2 rjoseph 2014-05-14 10:55:46 UTC
When the bug was raised the feature was still under development. The quorum patch went in recently.

Comment 3 rjoseph 2014-05-14 10:58:58 UTC

*** This bug has been marked as a duplicate of bug 1089527 ***


Note You need to log in before you can comment on or make changes to this bug.