[Bugs] [Bug 1773532] Gluster brick randomly segfaults

[bugzilla at redhat.com]

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

Yaniv Kaul <ykaul at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |godas at redhat.com
              Flags|                            |needinfo?(godas at redhat.com)



--- Comment #9 from Yaniv Kaul <ykaul at redhat.com> ---
I can see the crash:
2019-11-18 00:53:04.287021] E [MSGID: 113072]
[posix-inode-fd-ops.c:1898:posix_writev] 0-wiosna-vmstore-posix: write failed:
offset 0, [Invalid argument]
[2019-11-18 00:53:04.287072] E [MSGID: 115067]
[server-rpc-fops_v2.c:1373:server4_writev_cbk] 0-wiosna-vmstore-server:
26723901: WRITEV 5 (5bb969ab-4ed1-4afa-b136-78bf7ead800d), client:
CTX_ID:2cd653a2-1bae-4df7-adbe-9b8151275b15-GRAPH_ID:0-PID:14082-HOST:node03.wiosna.org.pl-PC_NAME:wiosna-vmstore-client-0-RECON_NO:-0,
error-xlator: wiosna-vmstore-posix [Invalid argument]
[2019-11-18 00:53:26.572901] E [socket.c:1303:socket_event_poll_err]
(-->/lib64/libglusterfs.so.0(+0x8b806) [0x7f6fd1543806]
-->/usr/lib64/glusterfs/6.5/rpc-transport/socket.so(+0xa48a) [0x7f6fc58a148a]
-->/usr/lib64/glusterfs/6.5/rpc-transport/socket.so(+0x81fc) [0x7f6fc589f1fc] )
0-socket: invalid argument: this->private [Invalid argument]
pending frames:
patchset: git://git.gluster.org/glusterfs.git
signal received: 11
time of crash: 
2019-11-18 00:53:27
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 6.5
/lib64/libglusterfs.so.0(+0x27130)[0x7f6fd14df130]
/lib64/libglusterfs.so.0(gf_print_trace+0x334)[0x7f6fd14e9b34]
/lib64/libc.so.6(+0x363b0)[0x7f6fcfb1c3b0]
/usr/lib64/glusterfs/6.5/rpc-transport/socket.so(+0xa4cc)[0x7f6fc58a14cc]
/lib64/libglusterfs.so.0(+0x8b806)[0x7f6fd1543806]
/lib64/libpthread.so.0(+0x7e65)[0x7f6fd031ee65]
/lib64/libc.so.6(clone+0x6d)[0x7f6fcfbe488d]
---------


But I'm certainly just as concerned on the write failures which the log is
flooded with:
[2019-11-17 02:20:47.554644] E [MSGID: 113072]
[posix-inode-fd-ops.c:1898:posix_writev] 0-wiosna-vmstore-posix: write failed:
offset 0, [Invalid argument]
[2019-11-17 02:20:47.554694] E [MSGID: 115067]
[server-rpc-fops_v2.c:1373:server4_writev_cbk] 0-wiosna-vmstore-server:
12021489: WRITEV 2 (82c44424-d251-42cf-ad23-13f0f9ea5ed7), client:
CTX_ID:c51b6193-1da1-4e46-9d30-637f419dcae1-GRAPH_ID:0-PID:15471-HOST:node01.wiosna.org.pl-PC_NAME:wiosna-vmstore-client-0-RECON_NO:-0,
error-xlator: wiosna-vmstore-posix [Invalid argument]


Gobinda, can you take a look?

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