Description of problem: We find that smbd cores are always truncated to 16M. It is already fixed in Samba master and we should get it in next downstream release.
Some more details about the bug: Although this has been taken from some other bug, we find a similar message on opening the core file. root@samba4-ad2:smbd# gdb core.27767 GNU gdb (GDB) Red Hat Enterprise Linux (7.2-75.el6) Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... BFD: Warning: /var/log/samba/cores/smbd/core.27767 is truncated: expected core file size >= 33017856, found: 16830464. BFD: Warning: /var/log/samba/cores/smbd/core.27767 is truncated: expected core file size >= 33017856, found: 16830464. Reading symbols from /usr/sbin/smbd...Reading symbols from /usr/lib/debug/usr/sbin/smbd.debug...done. Note found: 16830464. This is the 16M limit the core is truncated to.
Anoop C S has already RCA'ed the bug. We are working on changes required in init files and systemd unit files to fix in RHEL6 and RHEL7. We will have fix merged for this by end of this week.
[RHEL7] : I am able to crash smbd and produce core dump file of 160MB without getting truncated to 16MB. So rhel7 seemed fine. [RHEL6] : Even after vdsm work around the core file is not getting dumped in any of the below locations i.e /var/log/core & /var/log/samba/cores/smbd. version ======== samba-client-4.4.3-2.el6rhs.x86_64 Verification on RHEL6 failed.
Verified in RHEL6 & RHEL7 over version samba-client-4.4.3-3.el7rhgs.x86_64 and smbd core dumps are not getting truncated. Marking it as verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1248