[Bugs] [Bug 1145911] New: [SNAPSHOT]: Deletion of a snapshot in a volume or system fails if some operation which acquires the volume lock comes in between.
bugzilla at redhat.com
bugzilla at redhat.com
Wed Sep 24 06:15:32 UTC 2014
https://bugzilla.redhat.com/show_bug.cgi?id=1145911
Bug ID: 1145911
Summary: [SNAPSHOT]: Deletion of a snapshot in a volume or
system fails if some operation which acquires the
volume lock comes in between.
Product: GlusterFS
Version: 3.6.0
Component: glusterd
Severity: high
Priority: high
Assignee: gluster-bugs at redhat.com
Reporter: spandit at redhat.com
CC: bugs at gluster.org, gluster-bugs at redhat.com
Depends On: 1126289
+++ 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 at redhat.com)
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1126289
[Bug 1126289] [SNAPSHOT]: Deletion of a snapshot in a volume or system
fails if some operation which acquires the volume lock comes in between.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=NmwofGE6EZ&a=cc_unsubscribe
More information about the Bugs
mailing list