tweezerAT
Cadet
- Joined
- Dec 20, 2020
- Messages
- 9
Hi everyone!
I'm using freeNAS/trueNAS about a year without any problems. It has been very stable and all the things I need have been working. A few days ago I installed the update 12 U1, since then it seems there are some troubles with the stability of the SMB daemon. For example TimeMachine from my Macs is not able to backup data, it's just copying a few amount of files and then TM can't reach the NAS and is cancelin. Same if I copy a large amount of data from or to the NAS. I get a read error and if I say retry, it's continuing the copy process.
the output of testparm -s is as follows:
The share timmachine has been created during my time with freenas 11.x, TM_iMac has been created with 12 U1. I thought there might has been an error with the migration to the newer version. But I still have the same issue. Lagerplatz is just a "normal" share for files, no TM enabled.
I had a look in the samba4 logs (log.smbd in /var/log/samba3/) too and found the following lines:
So might there be a problem with Samba? I'm afraid I'm not really an expert on SMB, so maybe it's not a big deal and I have to have a look on some other services.
Hope you can help me!
Thanks and greetings from Vienna!
Thomas
I'm using freeNAS/trueNAS about a year without any problems. It has been very stable and all the things I need have been working. A few days ago I installed the update 12 U1, since then it seems there are some troubles with the stability of the SMB daemon. For example TimeMachine from my Macs is not able to backup data, it's just copying a few amount of files and then TM can't reach the NAS and is cancelin. Same if I copy a large amount of data from or to the NAS. I get a read error and if I say retry, it's continuing the copy process.
the output of testparm -s is as follows:
Code:
root@freenas[/var/log/samba4]# testparm -s Load smb config files from /usr/local/etc/smb4.conf Loaded services file OK. Server role: ROLE_STANDALONE # Global parameters [global] aio max threads = 2 bind interfaces only = Yes disable spoolss = Yes dns proxy = No enable web service discovery = Yes kernel change notify = No load printers = No logging = file max log size = 51200 nsupdate command = /usr/local/bin/samba-nsupdate -g registry shares = Yes restrict anonymous = 2 server role = standalone server server string = FreeNAS Server unix extensions = No idmap config *: range = 90000001-100000000 fruit:nfs_aces = No idmap config * : backend = tdb directory name cache size = 0 dos filemode = Yes [Timemachine] ea support = No kernel share modes = No path = /mnt/Daten/Timemachine posix locking = No read only = No vfs objects = aio_fbsd fruit streams_xattr ixnas fruit:locking = none fruit:time machine = yes fruit:resource = stream fruit:metadata = stream nfs4:chown = true [Lageplatz] ea support = No kernel share modes = No path = /mnt/Daten/Lageplatz posix locking = No read only = No vfs objects = aio_fbsd fruit streams_xattr ixnas fruit:resource = stream fruit:metadata = stream nfs4:chown = true [TM_iMac] ea support = No kernel share modes = No path = /mnt/Daten/Timemachine/thomas_imac/%U posix locking = No read only = No vfs objects = aio_fbsd tmprotect fruit streams_xattr shadow_copy_zfs ixnas ixnas:default_user_quota
The share timmachine has been created during my time with freenas 11.x, TM_iMac has been created with 12 U1. I thought there might has been an error with the migration to the newer version. But I still have the same issue. Lagerplatz is just a "normal" share for files, no TM enabled.
I had a look in the samba4 logs (log.smbd in /var/log/samba3/) too and found the following lines:
Code:
[2020/12/21 03:24:15.405434, 0] ../../lib/util/fault.c:79(fault_report) =============================================================== [2020/12/21 03:24:15.405613, 0] ../../lib/util/fault.c:80(fault_report) INTERNAL ERROR: Signal 11 in pid 39839 (4.12.9) 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/12/21 03:24:15.405657, 0] ../../lib/util/fault.c:86(fault_report) =============================================================== [2020/12/21 03:24:15.405684, 0] ../../source3/lib/util.c:830(smb_panic_s3) PANIC (pid 39839): internal error [2020/12/21 03:24:15.408349, 0] ../../lib/util/fault.c:265(log_stack_trace) BACKTRACE: 6 stack frames: #0 0x801296217 <log_stack_trace+0x37> at /usr/local/lib/samba4/libsamba-util.so.0 #1 0x802f9b656 <smb_panic_s3+0x56> at /usr/local/lib/samba4/libsmbconf.so.0 #2 0x801296007 <smb_panic+0x17> at /usr/local/lib/samba4/libsamba-util.so.0 #3 0x8012963ee <log_stack_trace+0x20e> at /usr/local/lib/samba4/libsamba-util.so.0 #4 0x801295fe9 <fault_setup+0x59> at /usr/local/lib/samba4/libsamba-util.so.0 #5 0x8099dbc20 <_pthread_sigmask+0x530> at /lib/libthr.so.3 [2020/12/21 03:24:15.408516, 0] ../../source3/lib/dumpcore.c:315(dump_core) dumping core in /var/db/system/cores [2020/12/21 03:58:50.129700, 0] ../../lib/util/fault.c:79(fault_report) =============================================================== [2020/12/21 03:58:50.129789, 0] ../../lib/util/fault.c:80(fault_report) INTERNAL ERROR: Signal 11 in pid 41657 (4.12.9) 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/12/21 03:58:50.129832, 0] ../../lib/util/fault.c:86(fault_report) =============================================================== [2020/12/21 03:58:50.129859, 0] ../../source3/lib/util.c:830(smb_panic_s3) PANIC (pid 41657): internal error [2020/12/21 03:58:50.132529, 0] ../../lib/util/fault.c:265(log_stack_trace) BACKTRACE: 6 stack frames: #0 0x801296217 <log_stack_trace+0x37> at /usr/local/lib/samba4/libsamba-util.so.0 #1 0x802f9b656 <smb_panic_s3+0x56> at /usr/local/lib/samba4/libsmbconf.so.0 #2 0x801296007 <smb_panic+0x17> at /usr/local/lib/samba4/libsamba-util.so.0 #3 0x8012963ee <log_stack_trace+0x20e> at /usr/local/lib/samba4/libsamba-util.so.0 #4 0x801295fe9 <fault_setup+0x59> at /usr/local/lib/samba4/libsamba-util.so.0 #5 0x8099dbc20 <_pthread_sigmask+0x530> at /lib/libthr.so.3 [2020/12/21 03:58:50.132694, 0] ../../source3/lib/dumpcore.c:315(dump_core) dumping core in /var/db/system/cores [2020/12/21 03:59:31.009299, 0] ../../lib/util/fault.c:79(fault_report) =============================================================== [2020/12/21 03:59:31.009422, 0] ../../lib/util/fault.c:80(fault_report) INTERNAL ERROR: Signal 11 in pid 41668 (4.12.9) 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/12/21 03:59:31.009484, 0] ../../lib/util/fault.c:86(fault_report) =============================================================== [2020/12/21 03:59:31.009517, 0] ../../source3/lib/util.c:830(smb_panic_s3) PANIC (pid 41668): internal error [2020/12/21 03:59:31.012392, 0] ../../lib/util/fault.c:265(log_stack_trace) BACKTRACE: 6 stack frames: #0 0x801296217 <log_stack_trace+0x37> at /usr/local/lib/samba4/libsamba-util.so.0 #1 0x802f9b656 <smb_panic_s3+0x56> at /usr/local/lib/samba4/libsmbconf.so.0 #2 0x801296007 <smb_panic+0x17> at /usr/local/lib/samba4/libsamba-util.so.0 #3 0x8012963ee <log_stack_trace+0x20e> at /usr/local/lib/samba4/libsamba-util.so.0 #4 0x801295fe9 <fault_setup+0x59> at /usr/local/lib/samba4/libsamba-util.so.0 #5 0x8099dbc20 <_pthread_sigmask+0x530> at /lib/libthr.so.3 [2020/12/21 03:59:31.012619, 0] ../../source3/lib/dumpcore.c:315(dump_core) dumping core in /var/db/system/cores
So might there be a problem with Samba? I'm afraid I'm not really an expert on SMB, so maybe it's not a big deal and I have to have a look on some other services.
Hope you can help me!
Thanks and greetings from Vienna!
Thomas