Hello!
Guest full access share on FreeNAS-11.3-U4.1, workgroup
General and share configs:
Browsing and opening files with Windows Explorer is fine (or at least there were no complaints). Yet when using Open... dialog in other software (mostly older stuff, but Chrome as well), quite often file listing halts when you open a folder within the share.
What I managed to replicate is:
restart smb service on FreeNAS (no smbd processes listed for my ip)
call a file open dialog (I get a smbd process for my ip with, guess due to network drive enumeration)
navigate to the network drive and try opening a folder (dialog halts for a while, proceeds as normal after, I get a new smdb process with different PID)
Log during the halt looks like this:
Not entirely sure if I accidentally caught someone else crashing here, but there is only one call of smbd_cleanupd_unlock which seems to be the timing halt ends.
And yeah, if I restart SMB and navigate to the folder using Explorer - it works fine, yet if I try creating an email attachment in Chrome right after from the same folder - the above symptoms happen.
Feeling quite puzzled. Anyone has a troubleshooting suggestion or if I should post some other config?
Guest full access share on FreeNAS-11.3-U4.1, workgroup
General and share configs:
[global]
aio max threads = 2
bind interfaces only = Yes
disable spoolss = Yes
dns proxy = No
enable core files = No
enable web service discovery = Yes
kernel change notify = No
load printers = No
logging = file
map to guest = Bad User
max log size = 51200
netbios aliases = pc-ubuntu
nsupdate command = /usr/local/bin/samba-nsupdate -g
server min protocol = NT1
server role = standalone server
server string = FreeNAS Server
username map = /usr/local/etc/smbusername.map
username map cache time = 60
idmap config *: range = 90000001-100000000
idmap config * : backend = tdb
allocation roundup size = 0
directory name cache size = 0
dos filemode = Yes
ea support = No
include = /usr/local/etc/smb4_share.conf
map archive = No
store dos attributes = No
[Шара]
aio write size = 0
guest ok = Yes
mangled names = illegal
path = /mnt/pool-main/share1
read only = No
vfs objects = streams_xattr shadow_copy_zfs zfs_space zfsacl
nfs4:acedup = merge
nfs4:chown = true
aio max threads = 2
bind interfaces only = Yes
disable spoolss = Yes
dns proxy = No
enable core files = No
enable web service discovery = Yes
kernel change notify = No
load printers = No
logging = file
map to guest = Bad User
max log size = 51200
netbios aliases = pc-ubuntu
nsupdate command = /usr/local/bin/samba-nsupdate -g
server min protocol = NT1
server role = standalone server
server string = FreeNAS Server
username map = /usr/local/etc/smbusername.map
username map cache time = 60
idmap config *: range = 90000001-100000000
idmap config * : backend = tdb
allocation roundup size = 0
directory name cache size = 0
dos filemode = Yes
ea support = No
include = /usr/local/etc/smb4_share.conf
map archive = No
store dos attributes = No
[Шара]
aio write size = 0
guest ok = Yes
mangled names = illegal
path = /mnt/pool-main/share1
read only = No
vfs objects = streams_xattr shadow_copy_zfs zfs_space zfsacl
nfs4:acedup = merge
nfs4:chown = true
Browsing and opening files with Windows Explorer is fine (or at least there were no complaints). Yet when using Open... dialog in other software (mostly older stuff, but Chrome as well), quite often file listing halts when you open a folder within the share.
What I managed to replicate is:
restart smb service on FreeNAS (no smbd processes listed for my ip)
call a file open dialog (I get a smbd process for my ip with, guess due to network drive enumeration)
navigate to the network drive and try opening a folder (dialog halts for a while, proceeds as normal after, I get a new smdb process with different PID)
Log during the halt looks like this:
[2020/10/05 11:43:37.160504, 0] ../../lib/util/fault.c:79(fault_report)
===============================================================
[2020/10/05 11:43:37.160538, 0] ../../lib/util/fault.c:80(fault_report)
INTERNAL ERROR: Signal 10 in pid 93189 (4.10.16)
If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
[2020/10/05 11:43:37.160554, 0] ../../lib/util/fault.c:86(fault_report)
===============================================================
[2020/10/05 11:43:37.160564, 0] ../../source3/lib/util.c:824(smb_panic_s3)
PANIC (pid 93189): internal error
[2020/10/05 11:43:37.161199, 0] ../../lib/util/fault.c:265(log_stack_trace)
BACKTRACE: 6 stack frames:
#0 0x801d4c0e7 <log_stack_trace+0x37> at /usr/local/lib/samba4/libsamba-util.so.0
#1 0x802d720cd <smb_panic_s3+0x4d> at /usr/local/lib/samba4/libsmbconf.so.0
#2 0x801d4bed7 <smb_panic+0x17> at /usr/local/lib/samba4/libsamba-util.so.0
#3 0x801d4c2be <log_stack_trace+0x20e> at /usr/local/lib/samba4/libsamba-util.so.0
#4 0x801d4beb9 <fault_setup+0x59> at /usr/local/lib/samba4/libsamba-util.so.0
#5 0x81164bcf0 <pthread_sigmask+0x530> at /lib/libthr.so.3
[2020/10/05 11:43:37.161243, 0] ../../source3/lib/dumpcore.c:283(dump_core)
Exiting on internal error (core file administratively disabled)
[2020/10/05 11:43:37.174121, 1] ../../source3/smbd/server.c:917(remove_child_pid)
Scheduled cleanup of brl and lock database after unclean shutdown
[2020/10/05 11:43:38.881773, 0] ../../lib/util/fault.c:79(fault_report)
===============================================================
[2020/10/05 11:43:38.881801, 0] ../../lib/util/fault.c:80(fault_report)
INTERNAL ERROR: Signal 10 in pid 93310 (4.10.16)
If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
[2020/10/05 11:43:38.881844, 0] ../../lib/util/fault.c:86(fault_report)
===============================================================
[2020/10/05 11:43:38.881853, 0] ../../source3/lib/util.c:824(smb_panic_s3)
PANIC (pid 93310): internal error
[2020/10/05 11:43:38.882611, 0] ../../lib/util/fault.c:265(log_stack_trace)
BACKTRACE: 6 stack frames:
#0 0x801d4c0e7 <log_stack_trace+0x37> at /usr/local/lib/samba4/libsamba-util.so.0
#1 0x802d720cd <smb_panic_s3+0x4d> at /usr/local/lib/samba4/libsmbconf.so.0
#2 0x801d4bed7 <smb_panic+0x17> at /usr/local/lib/samba4/libsamba-util.so.0
#3 0x801d4c2be <log_stack_trace+0x20e> at /usr/local/lib/samba4/libsamba-util.so.0
#4 0x801d4beb9 <fault_setup+0x59> at /usr/local/lib/samba4/libsamba-util.so.0
#5 0x81164bcf0 <pthread_sigmask+0x530> at /lib/libthr.so.3
[2020/10/05 11:43:38.882653, 0] ../../source3/lib/dumpcore.c:283(dump_core)
Exiting on internal error (core file administratively disabled)
[2020/10/05 11:43:40.585802, 0] ../../lib/util/fault.c:79(fault_report)
===============================================================
[2020/10/05 11:43:40.585828, 0] ../../lib/util/fault.c:80(fault_report)
INTERNAL ERROR: Signal 10 in pid 93311 (4.10.16)
If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
[2020/10/05 11:43:40.585870, 0] ../../lib/util/fault.c:86(fault_report)
===============================================================
[2020/10/05 11:43:40.585880, 0] ../../source3/lib/util.c:824(smb_panic_s3)
PANIC (pid 93311): internal error
[2020/10/05 11:43:40.586641, 0] ../../lib/util/fault.c:265(log_stack_trace)
BACKTRACE: 6 stack frames:
#0 0x801d4c0e7 <log_stack_trace+0x37> at /usr/local/lib/samba4/libsamba-util.so.0
#1 0x802d720cd <smb_panic_s3+0x4d> at /usr/local/lib/samba4/libsmbconf.so.0
#2 0x801d4bed7 <smb_panic+0x17> at /usr/local/lib/samba4/libsamba-util.so.0
#3 0x801d4c2be <log_stack_trace+0x20e> at /usr/local/lib/samba4/libsamba-util.so.0
#4 0x801d4beb9 <fault_setup+0x59> at /usr/local/lib/samba4/libsamba-util.so.0
#5 0x81164bcf0 <pthread_sigmask+0x530> at /lib/libthr.so.3
[2020/10/05 11:43:40.586681, 0] ../../source3/lib/dumpcore.c:283(dump_core)
Exiting on internal error (core file administratively disabled)
[2020/10/05 11:43:42.315391, 0] ../../lib/util/fault.c:79(fault_report)
===============================================================
[2020/10/05 11:43:42.315423, 0] ../../lib/util/fault.c:80(fault_report)
INTERNAL ERROR: Signal 10 in pid 93312 (4.10.16)
If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
[2020/10/05 11:43:42.315465, 0] ../../lib/util/fault.c:86(fault_report)
===============================================================
[2020/10/05 11:43:42.315474, 0] ../../source3/lib/util.c:824(smb_panic_s3)
PANIC (pid 93312): internal error
[2020/10/05 11:43:42.316228, 0] ../../lib/util/fault.c:265(log_stack_trace)
BACKTRACE: 6 stack frames:
#0 0x801d4c0e7 <log_stack_trace+0x37> at /usr/local/lib/samba4/libsamba-util.so.0
#1 0x802d720cd <smb_panic_s3+0x4d> at /usr/local/lib/samba4/libsmbconf.so.0
#2 0x801d4bed7 <smb_panic+0x17> at /usr/local/lib/samba4/libsamba-util.so.0
#3 0x801d4c2be <log_stack_trace+0x20e> at /usr/local/lib/samba4/libsamba-util.so.0
#4 0x801d4beb9 <fault_setup+0x59> at /usr/local/lib/samba4/libsamba-util.so.0
#5 0x81164bcf0 <pthread_sigmask+0x530> at /lib/libthr.so.3
[2020/10/05 11:43:42.316269, 0] ../../source3/lib/dumpcore.c:283(dump_core)
Exiting on internal error (core file administratively disabled)
[2020/10/05 11:43:44.038023, 0] ../../lib/util/fault.c:79(fault_report)
===============================================================
[2020/10/05 11:43:44.038051, 0] ../../lib/util/fault.c:80(fault_report)
INTERNAL ERROR: Signal 10 in pid 93313 (4.10.16)
If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
[2020/10/05 11:43:44.038093, 0] ../../lib/util/fault.c:86(fault_report)
===============================================================
[2020/10/05 11:43:44.038103, 0] ../../source3/lib/util.c:824(smb_panic_s3)
PANIC (pid 93313): internal error
[2020/10/05 11:43:44.038863, 0] ../../lib/util/fault.c:265(log_stack_trace)
BACKTRACE: 6 stack frames:
#0 0x801d4c0e7 <log_stack_trace+0x37> at /usr/local/lib/samba4/libsamba-util.so.0
#1 0x802d720cd <smb_panic_s3+0x4d> at /usr/local/lib/samba4/libsmbconf.so.0
#2 0x801d4bed7 <smb_panic+0x17> at /usr/local/lib/samba4/libsamba-util.so.0
#3 0x801d4c2be <log_stack_trace+0x20e> at /usr/local/lib/samba4/libsamba-util.so.0
#4 0x801d4beb9 <fault_setup+0x59> at /usr/local/lib/samba4/libsamba-util.so.0
#5 0x81164bcf0 <pthread_sigmask+0x530> at /lib/libthr.so.3
[2020/10/05 11:43:44.038904, 0] ../../source3/lib/dumpcore.c:283(dump_core)
Exiting on internal error (core file administratively disabled)
[2020/10/05 11:43:57.217004, 1] ../../source3/smbd/smbd_cleanupd.c:99(smbd_cleanupd_unlock)
smbd_cleanupd_unlock: Cleaning up brl and lock database after unclean shutdown
===============================================================
[2020/10/05 11:43:37.160538, 0] ../../lib/util/fault.c:80(fault_report)
INTERNAL ERROR: Signal 10 in pid 93189 (4.10.16)
If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
[2020/10/05 11:43:37.160554, 0] ../../lib/util/fault.c:86(fault_report)
===============================================================
[2020/10/05 11:43:37.160564, 0] ../../source3/lib/util.c:824(smb_panic_s3)
PANIC (pid 93189): internal error
[2020/10/05 11:43:37.161199, 0] ../../lib/util/fault.c:265(log_stack_trace)
BACKTRACE: 6 stack frames:
#0 0x801d4c0e7 <log_stack_trace+0x37> at /usr/local/lib/samba4/libsamba-util.so.0
#1 0x802d720cd <smb_panic_s3+0x4d> at /usr/local/lib/samba4/libsmbconf.so.0
#2 0x801d4bed7 <smb_panic+0x17> at /usr/local/lib/samba4/libsamba-util.so.0
#3 0x801d4c2be <log_stack_trace+0x20e> at /usr/local/lib/samba4/libsamba-util.so.0
#4 0x801d4beb9 <fault_setup+0x59> at /usr/local/lib/samba4/libsamba-util.so.0
#5 0x81164bcf0 <pthread_sigmask+0x530> at /lib/libthr.so.3
[2020/10/05 11:43:37.161243, 0] ../../source3/lib/dumpcore.c:283(dump_core)
Exiting on internal error (core file administratively disabled)
[2020/10/05 11:43:37.174121, 1] ../../source3/smbd/server.c:917(remove_child_pid)
Scheduled cleanup of brl and lock database after unclean shutdown
[2020/10/05 11:43:38.881773, 0] ../../lib/util/fault.c:79(fault_report)
===============================================================
[2020/10/05 11:43:38.881801, 0] ../../lib/util/fault.c:80(fault_report)
INTERNAL ERROR: Signal 10 in pid 93310 (4.10.16)
If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
[2020/10/05 11:43:38.881844, 0] ../../lib/util/fault.c:86(fault_report)
===============================================================
[2020/10/05 11:43:38.881853, 0] ../../source3/lib/util.c:824(smb_panic_s3)
PANIC (pid 93310): internal error
[2020/10/05 11:43:38.882611, 0] ../../lib/util/fault.c:265(log_stack_trace)
BACKTRACE: 6 stack frames:
#0 0x801d4c0e7 <log_stack_trace+0x37> at /usr/local/lib/samba4/libsamba-util.so.0
#1 0x802d720cd <smb_panic_s3+0x4d> at /usr/local/lib/samba4/libsmbconf.so.0
#2 0x801d4bed7 <smb_panic+0x17> at /usr/local/lib/samba4/libsamba-util.so.0
#3 0x801d4c2be <log_stack_trace+0x20e> at /usr/local/lib/samba4/libsamba-util.so.0
#4 0x801d4beb9 <fault_setup+0x59> at /usr/local/lib/samba4/libsamba-util.so.0
#5 0x81164bcf0 <pthread_sigmask+0x530> at /lib/libthr.so.3
[2020/10/05 11:43:38.882653, 0] ../../source3/lib/dumpcore.c:283(dump_core)
Exiting on internal error (core file administratively disabled)
[2020/10/05 11:43:40.585802, 0] ../../lib/util/fault.c:79(fault_report)
===============================================================
[2020/10/05 11:43:40.585828, 0] ../../lib/util/fault.c:80(fault_report)
INTERNAL ERROR: Signal 10 in pid 93311 (4.10.16)
If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
[2020/10/05 11:43:40.585870, 0] ../../lib/util/fault.c:86(fault_report)
===============================================================
[2020/10/05 11:43:40.585880, 0] ../../source3/lib/util.c:824(smb_panic_s3)
PANIC (pid 93311): internal error
[2020/10/05 11:43:40.586641, 0] ../../lib/util/fault.c:265(log_stack_trace)
BACKTRACE: 6 stack frames:
#0 0x801d4c0e7 <log_stack_trace+0x37> at /usr/local/lib/samba4/libsamba-util.so.0
#1 0x802d720cd <smb_panic_s3+0x4d> at /usr/local/lib/samba4/libsmbconf.so.0
#2 0x801d4bed7 <smb_panic+0x17> at /usr/local/lib/samba4/libsamba-util.so.0
#3 0x801d4c2be <log_stack_trace+0x20e> at /usr/local/lib/samba4/libsamba-util.so.0
#4 0x801d4beb9 <fault_setup+0x59> at /usr/local/lib/samba4/libsamba-util.so.0
#5 0x81164bcf0 <pthread_sigmask+0x530> at /lib/libthr.so.3
[2020/10/05 11:43:40.586681, 0] ../../source3/lib/dumpcore.c:283(dump_core)
Exiting on internal error (core file administratively disabled)
[2020/10/05 11:43:42.315391, 0] ../../lib/util/fault.c:79(fault_report)
===============================================================
[2020/10/05 11:43:42.315423, 0] ../../lib/util/fault.c:80(fault_report)
INTERNAL ERROR: Signal 10 in pid 93312 (4.10.16)
If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
[2020/10/05 11:43:42.315465, 0] ../../lib/util/fault.c:86(fault_report)
===============================================================
[2020/10/05 11:43:42.315474, 0] ../../source3/lib/util.c:824(smb_panic_s3)
PANIC (pid 93312): internal error
[2020/10/05 11:43:42.316228, 0] ../../lib/util/fault.c:265(log_stack_trace)
BACKTRACE: 6 stack frames:
#0 0x801d4c0e7 <log_stack_trace+0x37> at /usr/local/lib/samba4/libsamba-util.so.0
#1 0x802d720cd <smb_panic_s3+0x4d> at /usr/local/lib/samba4/libsmbconf.so.0
#2 0x801d4bed7 <smb_panic+0x17> at /usr/local/lib/samba4/libsamba-util.so.0
#3 0x801d4c2be <log_stack_trace+0x20e> at /usr/local/lib/samba4/libsamba-util.so.0
#4 0x801d4beb9 <fault_setup+0x59> at /usr/local/lib/samba4/libsamba-util.so.0
#5 0x81164bcf0 <pthread_sigmask+0x530> at /lib/libthr.so.3
[2020/10/05 11:43:42.316269, 0] ../../source3/lib/dumpcore.c:283(dump_core)
Exiting on internal error (core file administratively disabled)
[2020/10/05 11:43:44.038023, 0] ../../lib/util/fault.c:79(fault_report)
===============================================================
[2020/10/05 11:43:44.038051, 0] ../../lib/util/fault.c:80(fault_report)
INTERNAL ERROR: Signal 10 in pid 93313 (4.10.16)
If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
[2020/10/05 11:43:44.038093, 0] ../../lib/util/fault.c:86(fault_report)
===============================================================
[2020/10/05 11:43:44.038103, 0] ../../source3/lib/util.c:824(smb_panic_s3)
PANIC (pid 93313): internal error
[2020/10/05 11:43:44.038863, 0] ../../lib/util/fault.c:265(log_stack_trace)
BACKTRACE: 6 stack frames:
#0 0x801d4c0e7 <log_stack_trace+0x37> at /usr/local/lib/samba4/libsamba-util.so.0
#1 0x802d720cd <smb_panic_s3+0x4d> at /usr/local/lib/samba4/libsmbconf.so.0
#2 0x801d4bed7 <smb_panic+0x17> at /usr/local/lib/samba4/libsamba-util.so.0
#3 0x801d4c2be <log_stack_trace+0x20e> at /usr/local/lib/samba4/libsamba-util.so.0
#4 0x801d4beb9 <fault_setup+0x59> at /usr/local/lib/samba4/libsamba-util.so.0
#5 0x81164bcf0 <pthread_sigmask+0x530> at /lib/libthr.so.3
[2020/10/05 11:43:44.038904, 0] ../../source3/lib/dumpcore.c:283(dump_core)
Exiting on internal error (core file administratively disabled)
[2020/10/05 11:43:57.217004, 1] ../../source3/smbd/smbd_cleanupd.c:99(smbd_cleanupd_unlock)
smbd_cleanupd_unlock: Cleaning up brl and lock database after unclean shutdown
Not entirely sure if I accidentally caught someone else crashing here, but there is only one call of smbd_cleanupd_unlock which seems to be the timing halt ends.
And yeah, if I restart SMB and navigate to the folder using Explorer - it works fine, yet if I try creating an email attachment in Chrome right after from the same folder - the above symptoms happen.
Feeling quite puzzled. Anyone has a troubleshooting suggestion or if I should post some other config?
