[Bugs] [Bug 1285762] New: sharding - reads fail on sharded volume while running iozone
bugzilla at redhat.com
bugzilla at redhat.com
Thu Nov 26 12:03:25 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1285762
Bug ID: 1285762
Summary: sharding - reads fail on sharded volume while running
iozone
Product: GlusterFS
Version: 3.7.6
Component: sharding
Keywords: Triaged
Assignee: kdhananj at redhat.com
Reporter: kdhananj at redhat.com
QA Contact: bugs at gluster.org
CC: bugs at gluster.org
Depends On: 1285660
+++ This bug was initially created as a clone of Bug #1285660 +++
Description of problem:
While running iozone on a distributed-replicated volume with sharding enabled,
reads start to fail with EBADFD at some point. The issue is not seen when
md-cache is disabled. On loading trace above and below md-cache and rerunning
the test, figured shard_fsync_cbk() is not returning the aggregated size of the
file to the layers above - this md-cache would cache and serve incorrectly in
subsequent operations to the application, leading to failure.
[root at dhcp35-215 ~]# gluster volume info
Volume Name: dis-rep
Type: Distributed-Replicate
Volume ID: e2f66579-06c4-4e88-b825-003211f68d6b
Status: Started
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: kdhananjay:/bricks/1
Brick2: kdhananjay:/bricks/2
Brick3: kdhananjay:/bricks/3
Brick4: kdhananjay:/bricks/4
Options Reconfigured:
performance.strict-write-ordering: on
features.shard: on
performance.readdir-ahead: on
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 Vijay Bellur on 2015-11-26 03:31:51 EST ---
REVIEW: http://review.gluster.org/12759 (features/shard: Set ctime to 0 in
fsync callback) posted (#1) for review on master by Krutika Dhananjay
(kdhananj at redhat.com)
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1285660
[Bug 1285660] sharding - reads fail on sharded volume while running iozone
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
More information about the Bugs
mailing list