Bug 786146
Summary: | stat on a directory fails with ENOENT when rebalance is issued. | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | M S Vishwanath Bhat <vbhat> |
Component: | access-control | Assignee: | shishir gowda <sgowda> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | M S Vishwanath Bhat <vbhat> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | pre-release | CC: | amarts, gluster-bugs, mzywusko, nsathyan, rfortier |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.4.0 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-07-24 18:02:42 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 817967 |
Description
M S Vishwanath Bhat
2012-01-31 15:31:00 UTC
profiling was enabled and stripe-block-size was set to 64MB. Output from volume info. [root@RHEL6 /]# gluster v i Volume Name: hosdu Type: Distributed-Striped-Replicate Volume ID: 34b3f3bd-53d0-4795-bcf0-e5fb81bddeea Status: Started Number of Bricks: 2 x 2 x 2 = 8 Transport-type: tcp Bricks: Brick1: 10.1.11.113:/data/brick/hosdu_brick1 Brick2: 10.1.11.114:/data/brick/hosdu_brick2 Brick3: 10.1.11.136:/data/brick/hosdu_brick3 Brick4: 10.1.11.137:/data/brick/hosdu_brick4 Brick5: 10.1.11.113:/data/brick/hosdu_brick5 Brick6: 10.1.11.114:/data/brick/hosdu_brick6 Brick7: 10.1.11.136:/data/brick/hosdu_brick7 Brick8: 10.1.11.137:/data/brick/hosdu_brick8 Options Reconfigured: cluster.stripe-block-size: 64MB diagnostics.count-fop-hits: on diagnostics.latency-measurement: on last entries in the log file when stat is issued on 'hosa_dir' tail /usr/local/var/log/glusterfs/mnt-.log [2012-01-31 10:17:05.670415] E [fuse-resolve.c:192:fuse_resolve_gfid] 0-glusterfs-fuse: xl is NULL [2012-01-31 10:20:45.825349] E [fuse-resolve.c:192:fuse_resolve_gfid] 0-glusterfs-fuse: xl is NULL [2012-01-31 10:24:43.926470] E [fuse-resolve.c:192:fuse_resolve_gfid] 0-glusterfs-fuse: xl is NULL [2012-02-01 04:08:22.649230] E [fuse-resolve.c:192:fuse_resolve_gfid] 0-glusterfs-fuse: xl is NULL [2012-02-01 04:08:24.843136] E [fuse-resolve.c:192:fuse_resolve_gfid] 0-glusterfs-fuse: xl is NULL [2012-02-01 04:08:32.447879] E [fuse-resolve.c:192:fuse_resolve_gfid] 0-glusterfs-fuse: xl is NULL [2012-02-01 04:08:33.219337] E [fuse-resolve.c:192:fuse_resolve_gfid] 0-glusterfs-fuse: xl is NULL [2012-02-01 04:09:31.144304] E [fuse-resolve.c:192:fuse_resolve_gfid] 0-glusterfs-fuse: xl is NULL [2012-02-01 04:09:32.049503] E [fuse-resolve.c:192:fuse_resolve_gfid] 0-glusterfs-fuse: xl is NULL [2012-02-01 04:10:30.911489] E [fuse-resolve.c:192:fuse_resolve_gfid] 0-glusterfs-fuse: xl is NULL looks like the patch to implement proper resolve in fuse fixes this. (http://review.gluster.com/2703) Can't verify the bug as it's verification is blocked by bug https://bugzilla.redhat.com/show_bug.cgi?id=820355 Because of the above bug I can't go beyond step 2 while verifying. Followed the setps and issue is not happening. Moving to verified. |