Bug 762732 (GLUSTER-1000) - ENTOCONN error while running iozone in a loop
Summary: ENTOCONN error while running iozone in a loop
Keywords:
Status: CLOSED WORKSFORME
Alias: GLUSTER-1000
Product: GlusterFS
Classification: Community
Component: replicate
Version: 3.0.4
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: shishir gowda
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-12 16:56 UTC by Anush Shetty
Modified: 2015-12-01 16:45 UTC (History)
4 users (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 2010-06-12 16:56:48 UTC
While running iozone in a loop, after a few runs it hits the ENTOCONN error failing to open the tmp file. This was hit on an Distribute+Replicate setup.


 Auto Mode
        Command line used: /opt/qa/tools/iozone -a
        Output is in Kbytes/sec
        Time Resolution = 0.000001 seconds.
        Processor cache size set to 1024 Kbytes.
        Processor cache line size set to 32 bytes.
        File stride size set to 17 * record size.
                                                            random  random    bkwd   record   stride
              KB  reclen   write rewrite    read    reread    read   write    read  rewrite     read   fwrite frewrite   fread  freread
              64       4
Can not open temp file: iozone.tmp
open: Transport endpoint is not connected

Comment 1 Vijay Bellur 2010-06-16 04:28:39 UTC
Can you please attach the client and server log files?

Comment 2 Tejas Bhise 2010-07-29 03:15:42 UTC
Anush - can you reproduce+provide volume files ?

Comment 3 Anush Shetty 2010-08-06 10:47:35 UTC
Observed this in 3.1 . Client has crashed.

Comment 4 Vijay Bellur 2010-08-31 10:33:39 UTC
Can you please reproduce this now?

Comment 5 Vijay Bellur 2010-09-04 06:41:25 UTC
As this doesn't happen always, downgrading severity.

Comment 6 shishir gowda 2010-10-07 02:50:43 UTC
Not seen anymore in the latest git


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