| Summary: | Crash in inode_link | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Raghavendra Bhat <rabhat> |
| Component: | stripe | Assignee: | Amar Tumballi <amarts> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | mainline | CC: | amarts, fharshav, gluster-bugs, pavan, vijay, vraman |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Raghavendra Bhat
2010-01-22 06:10:45 UTC
http://patches.gluster.com/patch/2767/ fixes this and has been accepted to the repo.
The bug is still there in 3.0.3rc1. Can be reproduced by just running system_light script. Failes in LTP tests. This is the backtrace of the core generated.
Reading symbols from /usr/lib64/libgcc_s.so.1...done.
Loaded symbols for /usr/lib64/libgcc_s.so.1
Core was generated by `/opt/glusterfs/3.0.3rc1/sbin/glusterfs -f str_clnt.vol /mnt/hd/ -l /tmp/str_cln'.
Program terminated with signal 11, Segmentation fault.
[New process 7982]
[New process 7983]
[New process 7988]
#0 0x00007fa3a1f05ef7 in inode_link (inode=0x0, parent=0x612a10, name=0x618f61 "run7999", stbuf=0x619388) at inode.c:734
734 table = inode->table;
(gdb) bt
#0 0x00007fa3a1f05ef7 in inode_link (inode=0x0, parent=0x612a10, name=0x618f61 "run7999", stbuf=0x619388) at inode.c:734
#1 0x00007fa3a08f2fa9 in fuse_entry_cbk (frame=0x6191e8, cookie=0x619250, this=0x60b550, op_ret=0, op_errno=17,
inode=0x0, buf=0x619388) at fuse-bridge.c:480
#2 0x00007fa3a08f34c2 in fuse_newentry_cbk (frame=0x6191e8, cookie=0x619250, this=0x60b550, op_ret=0, op_errno=17,
inode=0x0, buf=0x619388, preparent=0x619538, postparent=0x6195c8) at fuse-bridge.c:537
#3 0x00007fa3a0b0c455 in stripe_stack_unwind_inode_cbk (frame=0x619250, cookie=0x6198f0, this=0x611580, op_ret=-1,
op_errno=17, inode=0x618da0, buf=0x7fff401d2a60, preparent=0x7fff401d29d0, postparent=0x7fff401d2940) at stripe.c:507
#4 0x00007fa3a0d3ddc9 in client_mkdir_cbk (frame=0x6198f0, hdr=0x619c40, hdrlen=348, iobuf=0x0)
at client-protocol.c:4706
#5 0x00007fa3a0d43447 in protocol_client_interpret (this=0x610a60, trans=0x6144f0, hdr_p=0x619c40 "", hdrlen=348,
iobuf=0x0) at client-protocol.c:6529
#6 0x00007fa3a0d4410d in protocol_client_pollin (this=0x610a60, trans=0x6144f0) at client-protocol.c:6827
#7 0x00007fa3a0d44781 in notify (this=0x610a60, event=2, data=0x6144f0) at client-protocol.c:6946
#8 0x00007fa3a1ef524c in xlator_notify (xl=0x610a60, event=2, data=0x6144f0) at xlator.c:924
#9 0x00007fa39fee608f in socket_event_poll_in (this=0x6144f0) at socket.c:731
#10 0x00007fa39fee6389 in socket_event_handler (fd=13, idx=5, data=0x6144f0, poll_in=1, poll_out=0, poll_err=0)
at socket.c:831
#11 0x00007fa3a1f19f5b in event_dispatch_epoll_handler (event_pool=0x60a320, events=0x6174e0, i=0) at event.c:804
#12 0x00007fa3a1f1a12a in event_dispatch_epoll (event_pool=0x60a320) at event.c:867
#13 0x00007fa3a1f1a43b in event_dispatch (event_pool=0x60a320) at event.c:975
#14 0x000000000040631f in main (argc=6, argv=0x7fff401d3728) at glusterfsd.c:1413
(gdb)
In fuse_entry_cbk and fuse_newentry_cbk op_ret is 0 even though op_errno is set.
Hence reopening.
Recent patches sent regarding cleaning local->failed should fix this issue. |