[Bugs] [Bug 1214247] New: sharding - Implement remaining fops
bugzilla at redhat.com
bugzilla at redhat.com
Wed Apr 22 09:56:43 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1214247
Bug ID: 1214247
Summary: sharding - Implement remaining fops
Product: GlusterFS
Version: 3.7.0
Component: sharding
Keywords: Triaged
Assignee: bugs at gluster.org
Reporter: kdhananj at redhat.com
QA Contact: bugs at gluster.org
CC: bugs at gluster.org
Depends On: 1207615
Blocks: 1199352 (glusterfs-3.7.0)
+++ This bug was initially created as a clone of Bug #1207615 +++
Description of problem:
This bug is for tracking the completion of the following fops in sharding:
READV
OPEN
[F]TRUNCATE
DISCARD
FALLOCATE
ZEROFILL
RENAME
UNLINK
[F]SETATTR
FSYNC
FLUSH
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-04-15 04:27:25 EDT ---
REVIEW: http://review.gluster.org/10249 (features/shard: Implement unlink fop)
posted (#1) for review on master by Krutika Dhananjay (kdhananj at redhat.com)
--- Additional comment from Anand Avati on 2015-04-15 05:49:29 EDT ---
REVIEW: http://review.gluster.org/10249 (features/shard: Implement unlink fop)
posted (#2) for review on master by Krutika Dhananjay (kdhananj at redhat.com)
--- Additional comment from Anand Avati on 2015-04-17 05:10:38 EDT ---
REVIEW: http://review.gluster.org/10249 (features/shard: Implement unlink fop)
posted (#3) for review on master by Krutika Dhananjay (kdhananj at redhat.com)
--- Additional comment from Anand Avati on 2015-04-22 01:38:43 EDT ---
REVIEW: http://review.gluster.org/10249 (features/shard: Implement unlink fop)
posted (#4) for review on master by Vijay Bellur (vbellur at redhat.com)
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1199352
[Bug 1199352] GlusterFS 3.7.0 tracker
https://bugzilla.redhat.com/show_bug.cgi?id=1207615
[Bug 1207615] sharding - Implement remaining fops
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list