Bug 1062122 - [SNAPSHOT] : Delete of a particular snapshot command fails in first attempt, But succeeds in second attempt.
Summary: [SNAPSHOT] : Delete of a particular snapshot command fails in first attempt, ...
Keywords:
Status: CLOSED DUPLICATE of bug 1049353
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: snapshot
Version: rhgs-3.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: rjoseph
QA Contact: Rahul Hinduja
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-06 08:56 UTC by Sachin Pandit
Modified: 2016-09-17 12:59 UTC (History)
6 users (show)

Fixed In Version: 3.4.1.6.snap.mar25.2014
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-14 12:15:06 UTC
Embargoed:

Attachments (Terms of Use)

Description Sachin Pandit 2014-02-06 08:56:21 UTC 
Description of problem:
Delete of a particular snapshot command fails in first attempt, But succeeds in second attempt.

Version-Release number of selected component (if applicable):
glusterfs-3.4.1.snap.jan15.2014

How reproducible:
Very often.

Steps to Reproduce:
1. Create a Distribute-replicate volume 
2. Create some snapshots of this volume
3. Try snapshot delete

Actual results:
Fails in first attempt, But succeeds in second attempt.


Expected results:
Snapshot delete should not fail.


Additional info:
Comment 1 Sachin Pandit 2014-02-06 08:57:57 UTC 
The delete was failing because of the race condition between process kill and snap volume unmount. unmount was tried even before the brick process was killed.

This issue is fixed in patch : http://review.gluster.org/#/c/6772/
Comment 3 Sachin Pandit 2014-03-11 07:29:36 UTC 
This Bug is dependent on Bug 1049353. So moving this bug to assigned state, until Bug 1049353 is resolved.
Comment 4 Sachin Pandit 2014-03-26 05:25:03 UTC 
This bug is dependent on Bug 1049353. Same patch fixes both the issue.
http://review.gluster.org/#/c/7123/
Comment 5 Sachin Pandit 2014-03-27 05:23:46 UTC 
Bug 1049353 got opened again because of recent changes. Have to investigate the issue. Moving this bug to assigned until the Bug 1049353 is resolved.
Comment 6 rjoseph 2014-05-14 12:15:06 UTC 

*** This bug has been marked as a duplicate of bug 1049353 ***
Note You need to log in before you can comment on or make changes to this bug.