[Bugs] [Bug 1181977] New: gluster vol clear-locks vol-name path kind all inode return IO error in a disperse volume
bugzilla at redhat.com
bugzilla at redhat.com
Wed Jan 14 08:48:41 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1181977
Bug ID: 1181977
Summary: gluster vol clear-locks vol-name path kind all inode
return IO error in a disperse volume
Product: GlusterFS
Version: 3.6.1
Component: disperse
Keywords: Triaged
Severity: high
Assignee: bugs at gluster.org
Reporter: xhernandez at datalab.es
CC: bugs at gluster.org, gluster-bugs at redhat.com,
jiademing.dd at gmail.com, lidi at perabytes.com,
xhernandez at datalab.es
Depends On: 1179050
+++ This bug was initially created as a clone of Bug #1179050 +++
Description of problem:
I create a disperse 3 redundancy 1 volume, start, and mount. then I exec
"gluster vol clear-locks vol-name path kind all inode", return IO error, and
all bricks are down(core dump).
I test a dht volume, that's OK.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--- Additional comment from Anand Avati on 2015-01-13 11:00:57 CET ---
REVIEW: http://review.gluster.org/9440 (ec: Don't use inodelk on getxattr when
clearing locks) posted (#1) for review on master by Xavier Hernandez
(xhernandez at datalab.es)
--- Additional comment from Xavier Hernandez on 2015-01-13 11:03:06 CET ---
This patch should solve the problem. However the error shouldn't have caused a
crash in glusterfsd processes. I'll take a look to that.
--- Additional comment from Anand Avati on 2015-01-13 13:56:21 CET ---
REVIEW: http://review.gluster.org/9440 (ec: Don't use inodelk on getxattr when
clearing locks) posted (#2) for review on master by Xavier Hernandez
(xhernandez at datalab.es)
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1179050
[Bug 1179050] gluster vol clear-locks vol-name path kind all inode return
IO error in a disperse volume
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list