On Wed, Sep 4, 2019 at 9:42 PM Andras Pataki <apataki@xxxxxxxxxxxxxxxxxxxxx> wrote: > > Dear ceph users, > > After upgrading our ceph-fuse clients to 14.2.2, we've been seeing sporadic segfaults with not super revealing stack traces: > > in thread 7fff5a7fc700 thread_name:ceph-fuse > > ceph version 14.2.2 (4f8fa0a0024755aae7d95567c63f11d6862d55be) nautilus (stable) > 1: (()+0xf5d0) [0x7ffff60b85d0] > 2: (()+0x255a0c) [0x5555557a9a0c] > 3: (()+0x16b6b) [0x7ffff7bb3b6b] > 4: (()+0x13401) [0x7ffff7bb0401] > 5: (()+0x7dd5) [0x7ffff60b0dd5] > 6: (clone()+0x6d) [0x7ffff4b5cead] > NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this. if you install the appropriate debuginfo package (this would depend on your OS) you may get a more enlightening stack. > > > Prior to 14.2.2, we've run 12.2.11 and 13.2.5 and have not seen this issue. Has anyone encountered this? If it isn't known - I can file a bug tracker for it. Please do and maybe try to capture a core dump if you can't get a better backtrace? > > Andras > > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com -- Cheers, Brad _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com