Bug 1145911 - [SNAPSHOT]: Deletion of a snapshot in a volume or system fails if some operation which acquires the volume lock comes in between.
Summary: [SNAPSHOT]: Deletion of a snapshot in a volume or system fails if some operat...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard: SNAPSHOT
Depends On: 1126289
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-24 06:15 UTC by Sachin Pandit
Modified: 2016-08-01 04:43 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1126289
Environment:
Last Closed: 2016-08-01 04:42:40 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Sachin Pandit 2014-09-24 06:15:32 UTC
+++ This bug was initially created as a clone of Bug #1126289 +++

Description of problem:
gluster snapshot delete volume <volname>
          (or)
gluster snapshot delete all

The above two commands might fail if some operation which acquires the
lock comes in between.

Explanation :
snapshot delete volume <volname> does a multiple RPC when tried to
do deletion of multiple snapshots in a volume. If some other operation
which acquires the lock comes in between, then snapshot delete will fail
with "another transaction in progress" error.


Version-Release number of selected component (if applicable):


How reproducible:
1/1


Steps to Reproduce:
1. issue a snapshot delete volume <volname> (say volname is vol1)
2. when step (1) is in progress, issue another command which takes a lock on volume vol1

Actual results:
snapshot delete fails with another transaction in progress.

Expected results:
command should not fail. 


Additional info:
Its better to give certain retries before failing.

--- Additional comment from Anand Avati on 2014-08-11 05:47:23 EDT ---

REVIEW: http://review.gluster.org/8454 (glusterd/snapshot : Differentiating between various error scenario.) posted (#1) for review on master by Sachin Pandit (spandit)

Comment 2 Atin Mukherjee 2016-08-01 04:42:40 UTC
This is not a security bug, not going to fix this in 3.6.x because of
http://www.gluster.org/pipermail/gluster-users/2016-July/027682.html

Comment 3 Atin Mukherjee 2016-08-01 04:43:59 UTC
If the issue persists in the latest releases, please feel free to clone them


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