[Bugs] [Bug 1314202] An operation will make "Transport endpoint is not connected" error.

bugzilla at redhat.com bugzilla at redhat.com
Wed Mar 9 05:30:12 UTC 2016


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

Niels de Vos <ndevos at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |Triaged
          Component|fuse                        |stripe



--- Comment #4 from Niels de Vos <ndevos at redhat.com> ---
The log contains a segmentation fault, this would have caused the "Transport
endpoint is not connected" error on the client.

Filtered stack:

libglusterfs.so.0(_gf_msg_backtrace_nomem)
libglusterfs.so.0(gf_print_trace)
libc.so.6()
glusterfs/3.7.8/xlator/cluster/stripe.so(stripe_readv_fstat_cbk)
glusterfs/3.7.8/xlator/cluster/replicate.so(afr_fstat_wind)
glusterfs/3.7.8/xlator/cluster/replicate.so(afr_read_txn_refresh_done)
glusterfs/3.7.8/xlator/cluster/replicate.so(afr_inode_refresh_done)
glusterfs/3.7.8/xlator/cluster/replicate.so(afr_inode_refresh_subvol_cbk)
glusterfs/3.7.8/xlator/cluster/replicate.so(afr_inode_refresh_subvol_with_fstat_cbk)
glusterfs/3.7.8/xlator/protocol/client.so(client3_3_fstat_cbk)
libgfrpc.so.0(rpc_clnt_handle_reply)
libgfrpc.so.0(rpc_clnt_notify)
libgfrpc.so.0(rpc_transport_notify)
glusterfs/3.7.8/rpc-transport/socket.so()
glusterfs/3.7.8/rpc-transport/socket.so()
libglusterfs.so.0()
libpthread.so.0()
libc.so.6(clone)


My strong recommendation is to re-create the volume and remove the stripe
layer. Stripe is surely *not* what you want in any case.

  http://joejulian.name/blog/should-i-use-stripe-on-glusterfs/

If you have big files that would benefit from being split into smaller piecees
to get distributed, you should enable sharding instead. Sharding is much more
tested than stripe, and is actively maintained. Stripe will most likely be
removed in an upcoming release, we are not spending much time on fixing its
bugs. More information on sharding can be find on the blog of the main
developer:

  http://blog.gluster.org/2015/12/introducing-shard-translator/

-- 
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