PANIC internal error: samba 4.12.5 CTDB cluster
David Rivera
rivera.david87 at gmail.com
Mon Aug 3 18:55:18 UTC 2020
I've just received another panic while trying to access a directory. The
directory is not accessible on any of the cluster members.
Aug 3 11:13:49 samba1 smbd[3054477]: [2020/08/03 11:13:49.764380, 0]
../../source3/locking/share_mode_lock.c:448(share_mode_data_store)
Aug 3 11:13:49 samba1 smbd[3054477]: PANIC: assert failed at
../../source3/locking/share_mode_lock.c(448): !share_entries_exist
Aug 3 11:13:49 samba1 smbd[3054477]: [2020/08/03 11:13:49.764458, 0]
../../source3/lib/util.c:830(smb_panic_s3)
Aug 3 11:13:49 samba1 smbd[3054477]: PANIC (pid 3054477): assert failed:
!share_entries_exist
Aug 3 11:13:49 samba1 smbd[3054477]: [2020/08/03 11:13:49.765098, 0]
../../lib/util/fault.c:265(log_stack_trace)
Aug 3 11:13:49 samba1 smbd[3054477]: BACKTRACE: 40 stack frames:
Aug 3 11:13:49 samba1 smbd[3054477]: #0
/usr/local/samba/lib/libsamba-util.so.0(log_stack_trace+0x1f)
[0x7f802f1b2f48]
Aug 3 11:13:49 samba1 smbd[3054477]: #1
/usr/local/samba/lib/libsmbconf.so.0(smb_panic_s3+0x74) [0x7f802d713571]
Aug 3 11:13:49 samba1 smbd[3054477]: #2
/usr/local/samba/lib/libsamba-util.so.0(smb_panic+0x28) [0x7f802f1b2f13]
Aug 3 11:13:49 samba1 smbd[3054477]: #3
/usr/local/samba/lib/private/libsmbd-base-samba4.so(+0x92041)
[0x7f802ec2e041]
Aug 3 11:13:49 samba1 smbd[3054477]: #4
/usr/local/samba/lib/private/libsmbd-base-samba4.so(+0x92afe)
[0x7f802ec2eafe]
Aug 3 11:13:49 samba1 smbd[3054477]: #5
/usr/local/samba/lib/private/libtalloc.so.2(+0x383c) [0x7f802dd6883c]
Aug 3 11:13:49 samba1 smbd[3054477]: #6
/usr/local/samba/lib/private/libtalloc.so.2(+0x3bb8) [0x7f802dd68bb8]
Aug 3 11:13:49 samba1 smbd[3054477]: #7
/usr/local/samba/lib/private/libtalloc.so.2(_talloc_free+0x105)
[0x7f802dd69e80]
Aug 3 11:13:49 samba1 smbd[3054477]: #8
/usr/local/samba/lib/private/libsmbd-base-samba4.so(+0x2162fa)
[0x7f802edb22fa]
Aug 3 11:13:49 samba1 smbd[3054477]: #9
/usr/local/samba/lib/private/libsmbd-base-samba4.so(+0x2188a6)
[0x7f802edb48a6]
Aug 3 11:13:49 samba1 smbd[3054477]: #10
/usr/local/samba/lib/private/libsmbd-base-samba4.so(create_file_default+0x303)
[0x7f802edb5530]
Aug 3 11:13:49 samba1 smbd[3054477]: #11
/usr/local/samba/lib/private/libsmbd-base-samba4.so(+0x192904)
[0x7f802ed2e904]
Aug 3 11:13:49 samba1 smbd[3054477]: #12
/usr/local/samba/lib/private/libsmbd-base-samba4.so(smb_vfs_call_create_file+0xa9)
[0x7f802edbfe57]
Aug 3 11:13:49 samba1 smbd[3054477]: #13
/usr/local/samba/lib/private/libsmbd-base-samba4.so(+0x2679c6)
[0x7f802ee039c6]
Aug 3 11:13:49 samba1 smbd[3054477]: #14
/usr/local/samba/lib/private/libsmbd-base-samba4.so(smbd_smb2_request_process_create+0x702)
[0x7f802ee01791]
Aug 3 11:13:49 samba1 smbd[3054477]: #15
/usr/local/samba/lib/private/libsmbd-base-samba4.so(smbd_smb2_request_dispatch+0x11a1)
[0x7f802edf50c2]
Aug 3 11:13:49 samba1 smbd[3054477]: #16
/usr/local/samba/lib/private/libsmbd-base-samba4.so(+0x25d22c)
[0x7f802edf922c]
Aug 3 11:13:49 samba1 smbd[3054477]: #17
/usr/local/samba/lib/private/libsmbd-base-samba4.so(+0x25d332)
[0x7f802edf9332]
Aug 3 11:13:49 samba1 smbd[3054477]: #18
/usr/local/samba/lib/private/libtevent.so.0(tevent_common_invoke_fd_handler+0x101)
[0x7f802e382faf]
Aug 3 11:13:49 samba1 smbd[3054477]: #19
/usr/local/samba/lib/private/libtevent.so.0(+0x1160e) [0x7f802e38d60e]
Aug 3 11:13:49 samba1 smbd[3054477]: #20
/usr/local/samba/lib/private/libtevent.so.0(+0x11c55) [0x7f802e38dc55]
Aug 3 11:13:49 samba1 smbd[3054477]: #21
/usr/local/samba/lib/private/libtevent.so.0(+0xe5c0) [0x7f802e38a5c0]
Aug 3 11:13:49 samba1 smbd[3054477]: #22
/usr/local/samba/lib/private/libtevent.so.0(_tevent_loop_once+0x10f)
[0x7f802e382274]
Aug 3 11:13:49 samba1 smbd[3054477]: #23
/usr/local/samba/lib/private/libtevent.so.0(tevent_common_loop_wait+0x25)
[0x7f802e38258f]
Aug 3 11:13:49 samba1 smbd[3054477]: #24
/usr/local/samba/lib/private/libtevent.so.0(+0xe662) [0x7f802e38a662]
Aug 3 11:13:49 samba1 smbd[3054477]: #25
/usr/local/samba/lib/private/libtevent.so.0(_tevent_loop_wait+0x2b)
[0x7f802e382632]
Aug 3 11:13:49 samba1 smbd[3054477]: #26
/usr/local/samba/lib/private/libsmbd-base-samba4.so(smbd_process+0xbd1)
[0x7f802eddd5ca]
Aug 3 11:13:49 samba1 smbd[3054477]: #27
/usr/local/samba/sbin/smbd(+0xd381) [0x55b264979381]
Aug 3 11:13:49 samba1 smbd[3054477]: #28
/usr/local/samba/lib/private/libtevent.so.0(tevent_common_invoke_fd_handler+0x101)
[0x7f802e382faf]
Aug 3 11:13:49 samba1 smbd[3054477]: #29
/usr/local/samba/lib/private/libtevent.so.0(+0x1160e) [0x7f802e38d60e]
Aug 3 11:13:49 samba1 smbd[3054477]: #30
/usr/local/samba/lib/private/libtevent.so.0(+0x11c55) [0x7f802e38dc55]
Aug 3 11:13:49 samba1 smbd[3054477]: #31
/usr/local/samba/lib/private/libtevent.so.0(+0xe5c0) [0x7f802e38a5c0]
Aug 3 11:13:49 samba1 smbd[3054477]: #32
/usr/local/samba/lib/private/libtevent.so.0(_tevent_loop_once+0x10f)
[0x7f802e382274]
Aug 3 11:13:49 samba1 smbd[3054477]: #33
/usr/local/samba/lib/private/libtevent.so.0(tevent_common_loop_wait+0x25)
[0x7f802e38258f]
Aug 3 11:13:49 samba1 smbd[3054477]: #34
/usr/local/samba/lib/private/libtevent.so.0(+0xe662) [0x7f802e38a662]
Aug 3 11:13:49 samba1 smbd[3054477]: #35
/usr/local/samba/lib/private/libtevent.so.0(_tevent_loop_wait+0x2b)
[0x7f802e382632]
Aug 3 11:13:49 samba1 smbd[3054477]: #36
/usr/local/samba/sbin/smbd(+0xdf84) [0x55b264979f84]
Aug 3 11:13:49 samba1 smbd[3054477]: #37
/usr/local/samba/sbin/smbd(main+0x182a) [0x55b26497c0ce]
Aug 3 11:13:49 samba1 smbd[3054477]: #38
/lib64/libc.so.6(__libc_start_main+0xf3) [0x7f802acc06a3]
Aug 3 11:13:49 samba1 smbd[3054477]: #39
/usr/local/samba/sbin/smbd(_start+0x2e) [0x55b26497252e]
Aug 3 11:13:49 samba1 smbd[3054477]: [2020/08/03 11:13:49.765444, 0]
../../source3/lib/dumpcore.c:318(dump_core)
Aug 3 11:13:49 samba1 smbd[3054477]: coredump is handled by helper binary
specified at /proc/sys/kernel/core_pattern
Aug 3 11:15:14 samba1 smbd[3053253]: close_directory: Could not get share
mode lock for Directory
Any help to fix this problem would be appreciated.
Thank you,
David
On Fri, Jul 24, 2020 at 1:13 PM David Rivera <rivera.david87 at gmail.com>
wrote:
> Hi,
>
> We've recently moved to using samba as our file server (about 2 weeks
> ago). Today we experienced a panic on all 3 CTDB cluster members that made
> all shares unavailable (samba-ctdb-node0-panic-backtrace-internal-error.log
> attached). I've included two additional panics I've found in the smbd log.
>
> We are using samba 12.4.5 built from source and have a 3 node CTDB cluster
> with ceph as the storage backend mounted using the ceph kernel client
> (Linux kernel 5.7.7). Our SMB clients are Windows XP, Windows 7 & Windows
> 10 connecting through Microsoft DFS (Windows DCs) and storing a number of
> file types including Microsoft Office documents and shared Microsoft Access
> databases. We have been running into issues with Windows XP client sessions
> hanging and making the locked files inaccessible but we've been able to get
> around this issue for the meantime by killing the associated smbd process.
>
> We've compiled samba on CentOS 8 [CentOS Linux release 8.2.2004 (Core)]
> using the following commands on all 3 nodes:
>
> # PKG_CONFIG_PATH="/usr/lib/pkgconfig/:${PKG_CONFIG_PATH}" ./configure
> --with-cluster-support --enable-ceph-reclock
> --with-shared-modules=idmap_rid,idmap_tdb2,idmap_ad --without-ad-dc
> # make -j 4
> # make install
>
> Our configuration is as follows.
>
> [global]
> client min protocol = NT1
> clustering = Yes
> dedicated keytab file = /etc/krb5.keytab
> kerberos method = secrets and keytab
> netbios name = CTDB
> realm = DOMAIN1.COM <http://domain1.com/>
> reset on zero vc = Yes
> security = ADS
> server min protocol = NT1
> template shell = /bin/bash
> username map = /usr/local/samba/etc/user.map
> winbind nss info = rfc2307
> winbind refresh tickets = Yes
> workgroup = DOMAIN1
> idmap config domain5:unix_primary_group = yes
> idmap config domain5:unix_nss_info = no
> idmap config domain5:range = 50000-59999
> idmap config domain5:schema_mode = rfc2307
> idmap config domain5:backend = ad
> idmap config domain4:unix_primary_group = yes
> idmap config domain4:unix_nss_info = no
> idmap config domain4:range = 40000-49999
> idmap config domain4:schema_mode = rfc2307
> idmap config domain4:backend = ad
> idmap config domain3:unix_primary_group = yes
> idmap config domain3:unix_nss_info = no
> idmap config domain3:range = 30000-39999
> idmap config domain3:schema_mode = rfc2307
> idmap config domain3:backend = ad
> idmap config domain2:unix_primary_group = yes
> idmap config domain2:unix_nss_info = no
> idmap config domain2:range = 20000-29999
> idmap config domain2:schema_mode = rfc2307
> idmap config domain2:backend = ad
> idmap config domain1:unix_primary_group = yes
> idmap config domain1:unix_nss_info = no
> idmap config domain1:range = 10000-99999
> idmap config domain1:schema_mode = rfc2307
> idmap config domain1:backend = ad
> idmap config * : range = 3000-7999
> idmap config * : backend = tdb
> kernel share modes = No
> map acl inherit = Yes
> posix locking = No
> vfs objects = acl_xattr
> ## Used during testing, turned off for production
> #server multi channel support = yes
> #interfaces = "10.20.10.224;capability=RSS"
> "10.20.10.225;capability=RSS" "10.20.10.226;capability=RSS"
>
> # Multiple shares defined this way
> [share1]
> allocation roundup size = 4096
> comment = Share1
> # CephFS mount on /srv/samba
> path = /srv/samba/shares/share1
> read only = No
> vfs objects = acl_xattr ceph_snapshots io_uring
>
> # Test share
> [test]
> allocation roundup size = 4096
> comment = Test Share
> path = /srv/samba/shares/test
> smb encrypt = desired
> vfs objects = acl_xattr recycle ceph_snapshots io_uring
> recycle:exclude = thumbs.db,*.ldb,~$*
> recycle:touch = Yes
> recycle:versions = Yes
> recycle:keeptree = Yes
> recycle:repository = ../recycle/test
>
> Here is our CTDB configuration file:
>
> [logging]
> location = syslog
> log level = NOTICE
>
> [cluster]
> recovery lock =
> !/usr/local/samba/libexec/ctdb/ctdb_mutex_ceph_rados_helper ceph
> client.samba rados.samba.conf ctdb.lock
>
> Please let me know how I could help figure out the cause of this panic(s).
>
> Thank you,
> David
>
More information about the samba-technical
mailing list