[Bugs] [Bug 1747414] New: EIO error on check_and_dump_fuse_W call

bugzilla at redhat.com bugzilla at redhat.com
Fri Aug 30 11:25:33 UTC 2019


            Bug ID: 1747414
           Summary: EIO error on check_and_dump_fuse_W call
           Product: GlusterFS
           Version: 5
          Hardware: x86_64
                OS: Linux
            Status: NEW
         Component: libglusterfsclient
          Assignee: bugs at gluster.org
          Reporter: stam.bardis at gmail.com
                CC: bugs at gluster.org
  Target Milestone: ---
    Classification: Community

Created attachment 1609823
  --> https://bugzilla.redhat.com/attachment.cgi?id=1609823&action=edit
Fuse client logs

Description of problem:
After massively create/rename/delete file operations on a volume  we are
getting EIO failure (fuse-bridge.c:219:check_and_dump_fuse_W).

Version-Release number of selected component (if applicable):
gluster --version
glusterfs 5.6

cat /proc/version 
Linux version 4.4.179-1.el7.elrepo.x86_64 (mockbuild at Build64R7) (gcc version
4.8.5 20150623 (Red Hat 4.8.5-36) (GCC) ) #1 SMP Sat Apr 27 08:29:04 EDT 2019

Volume Name: oam
Type: Replicate
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Options Reconfigured:
cluster.consistent-metadata: on
performance.lazy-open: on
performance.strict-o-direct: off
performance.open-behind: on
performance.quick-read: on
performance.io-cache: on
performance.readdir-ahead: on
performance.write-behind: on
performance.read-ahead: on
performance.stat-prefetch: on
diagnostics.brick-log-level: INFO
diagnostics.client-log-level: ERROR
diagnostics.brick-sys-log-level: INFO
cluster.server-quorum-type: server
cluster.quorum-type: auto
transport.address-family: inet
nfs.disable: on
performance.client-io-threads: off
cluster.server-quorum-ratio: 51%

How reproducible:
Script that does the following operations in a massive way: 
create-rename-delete a file on a single thread.

Actual results:
Debug logs from FUSE client attached

You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

More information about the Bugs mailing list