[Bugs] [Bug 1710744] New: [FUSE] Endpoint is not connected after "Found anomalies" error

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1710744

            Bug ID: 1710744
           Summary: [FUSE] Endpoint is not connected after "Found
                    anomalies" error
           Product: GlusterFS
           Version: 5
                OS: Linux
            Status: NEW
         Component: fuse
          Severity: urgent
          Assignee: bugs at gluster.org
          Reporter: kompastver at gmail.com
                CC: bugs at gluster.org
  Target Milestone: ---
    Classification: Community



Description of problem:
Fuse client crashed after it found anomalies. Or probably it's just a
coincidence.

Version-Release number of selected component (if applicable):
v5.5

How reproducible:
I've observed it only once after two months of uptime on a production cluster

Steps to Reproduce:

Actually, there were usual workload, and nothing special was done

1. setup replicated volume with two bricks
2. mount it via fuse client
3. use it till it crashes
¯\_(ツ)_/¯

Actual results:
Fuse mount crashed

Expected results:
Fuse mount works

Additional info:

Volume info:

Volume Name: st
Type: Replicate
Volume ID: adfd1585-1f5c-42af-a195-af57889d951d
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: srv1:/vol3/
Brick2: srv2:/vol3/
Options Reconfigured:
performance.read-ahead: off
cluster.readdir-optimize: on
client.event-threads: 2
server.event-threads: 16
network.ping-timeout: 20
cluster.data-self-heal-algorithm: full
performance.io-thread-count: 16
performance.io-cache: on
performance.cache-size: 1GB
performance.quick-read: off
transport.address-family: inet6
performance.readdir-ahead: off
nfs.disable: on

Fuse client log:
[2019-05-15 01:46:03.521974] W [fuse-bridge.c:582:fuse_entry_cbk]
0-glusterfs-fuse: 179361305: MKDIR() /assets_cache/26B/280 => -1 (File exists)
[2019-05-16 05:29:44.172704] W [fuse-bridge.c:582:fuse_entry_cbk]
0-glusterfs-fuse: 186813586: MKDIR() /assets_cache/320/0C0 => -1 (File exists)
[2019-05-16 05:29:44.175393] I [MSGID: 109063]
[dht-layout.c:659:dht_layout_normalize] 6-st3-dht: Found anomalies in
/assets_cache/320/0C0 (gfid = 00000000-0000-0000-0000-000000000000). Holes=1
overlaps=0
pending frames:
pending frames:
frame : type(1) op(UNLINK)
frame : type(1) op(OPEN)
frame : type(0) op(0)
patchset: git://git.gluster.org/glusterfs.git
signal received: 11
frame : type(1) op(UNLINK)
frame : type(1) op(OPEN)
frame : type(0) op(0)
patchset: git://git.gluster.org/glusterfs.git
signal received: 11
time of crash: 
2019-05-16 05:58:43
configuration details:
argp 1
backtrace 1
dlfcn 1
libpthread 1
llistxattr 1
setfsid 1
spinlock 1
epoll.h 1
xattr.h 1
st_atim.tv_nsec 1
package-string: glusterfs 5.5
time of crash: 
2019-05-16 05:58:43
configuration details:
argp 1
backtrace 1
dlfcn 1
libpthread 1
llistxattr 1
setfsid 1
spinlock 1
epoll.h 1
xattr.h 1
st_atim.tv_nsec 1
package-string: glusterfs 5.5
/lib64/libglusterfs.so.0(+0x26620)[0x7f4b559a4620]
/lib64/libglusterfs.so.0(gf_print_trace+0x334)[0x7f4b559aebd4]
/lib64/libc.so.6(+0x36280)[0x7f4b53dd7280]
/lib64/libpthread.so.0(pthread_mutex_lock+0x0)[0x7f4b545d9c30]
/lib64/libglusterfs.so.0(fd_unref+0x37)[0x7f4b559cd1e7]
/usr/lib64/glusterfs/5.5/xlator/protocol/client.so(+0x17038)[0x7f4b47beb038]
/usr/lib64/glusterfs/5.5/xlator/protocol/client.so(+0x721ed)[0x7f4b47c461ed]
/lib64/libgfrpc.so.0(+0xf030)[0x7f4b55771030]
/lib64/libgfrpc.so.0(+0xf403)[0x7f4b55771403]
/lib64/libgfrpc.so.0(rpc_transport_notify+0x23)[0x7f4b5576d2f3]
/usr/lib64/glusterfs/5.5/rpc-transport/socket.so(+0xa106)[0x7f4b48d04106]
/lib64/libglusterfs.so.0(+0x8aa89)[0x7f4b55a08a89]
/lib64/libpthread.so.0(+0x7dd5)[0x7f4b545d7dd5]
/lib64/libc.so.6(clone+0x6d)[0x7f4b53e9eead]
---------

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