Bug 762044 (GLUSTER-312) - iozone crash in Distribute-Replicate
Summary: iozone crash in Distribute-Replicate
Keywords:
Status: CLOSED NOTABUG
Alias: GLUSTER-312
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Vikas Gorur
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-13 04:39 UTC by Anush Shetty
Modified: 2009-10-14 07:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Anush Shetty 2009-10-13 01:43:53 UTC
Another instance of iozone was running on the same mount point. So marking this bug as invalid.

Comment 1 Anush Shetty 2009-10-13 04:39:44 UTC
In a Distribute-Replicate setup in 2.0.8rc5, when iozone is run, it crashes with a "No such file or directory" error.

Client log:

[2009-10-13 00:31:28] W [fuse-bridge.c:513:fuse_attr_cbk] glusterfs-fuse: 222752: TRUNCATE() /iozone.tmp => -1 (No such file or directory)
[2009-10-13 00:33:11] W [fuse-bridge.c:639:fuse_fd_cbk] glusterfs-fuse: 226970: OPEN() /iozone.tmp => -1 (No such file or directory)
[2009-10-13 00:33:47] W [fuse-bridge.c:639:fuse_fd_cbk] glusterfs-fuse: 228344: OPEN() /iozone.tmp => -1 (No such file or directory)
[2009-10-13 00:34:36] W [fuse-bridge.c:639:fuse_fd_cbk] glusterfs-fuse: 229950: OPEN() /iozone.tmp => -1 (No such file or directory)
[2009-10-13 00:34:48] W [fuse-bridge.c:639:fuse_fd_cbk] glusterfs-fuse: 230515: OPEN() /iozone.tmp => -1 (No such file or directory)
[2009-10-13 00:35:15] W [fuse-bridge.c:639:fuse_fd_cbk] glusterfs-fuse: 231778: OPEN() /iozone.tmp => -1 (No such file or directory)
[2009-10-13 00:36:07] W [fuse-bridge.c:639:fuse_fd_cbk] glusterfs-fuse: 233675: OPEN() /iozone.tmp => -1 (No such file or directory)

Comment 2 Anand Avati 2009-10-14 04:47:43 UTC
PATCH: http://patches.gluster.com/patch/1882 in master (performance/write-behind: return from wb_open after STACK_WIND)


Note You need to log in before you can comment on or make changes to this bug.