[Samba] Abysmal performance with Samba 4 and Windows Explorer
Chan Min Wai
dcmwai at gmail.com
Thu Mar 6 00:36:52 MST 2014
Dear Simon,
According to some thread...
AD DC function do impact on Files Server performance. (Not too sure if this
is the case)
And normally, we would advise to use another server for Share...
Another server which join AD as a member (you can run AD DC as a vm)
Also your base OS (linux or etc) wouldn't have any idea on your users/group
in AD are ... and caused all that NT_STATUS_NOT_FOUND
So pick one use winbind or nslcd or sssd to let your Base OS understand who
is access them and their right....
On Thu, Mar 6, 2014 at 3:01 PM, Simon Schneider <schneida.simon at gmail.com>wrote:
> Hi,
>
> No I don't have any of these configured, they are never mentioned in the
> Samba HowTo and as I don't want to have any of my users working on anything
> else than windows, I thought it is optional? Do you think that might cause
> my issues?
>
> Thanks a lot for your input!
> Am 06.03.2014 05:23 schrieb "Chan Min Wai" <dcmwai at gmail.com>:
>
> Dear Simon,
>>
>> Looking at your config.
>>
>> Do you have winbind/nslcd/sssd that work on the local unix for users
>> authentication?
>> Or basically can getent password and group show your AD users?
>>
>> Also I see some panic and also some issue in your samba log...
>>
>>
>>
>>
>>
>> On Thu, Mar 6, 2014 at 12:15 AM, Simon Schneider <
>> schneida.simon at gmail.com> wrote:
>>
>>> One more thing, I tried mapping the drive again and using "xcopy /e" to
>>> transfer a folder and while the copying itself was very fast (same
>>> performance as xcopy) the initial mapping took ages (like 3 minutes) and
>>> also each "dir" command blocked after being initially fast at displaying
>>> each folder (like 30 or so) but then got blocked for like one minute
>>> before
>>> writing the last two lines (number of files + space available).
>>>
>>> This makes me think that samba is slow at reading file sizes,
>>> permissions,
>>> users / groups or something like that of all the files. Is it a problem
>>> that my share is on a LVM drive?
>>> Output from mount command:
>>>
>>> /dev/mapper/abcserver-samba on /srv/samba type ext4
>>> (rw,noatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>>
>>> Thanks!
>>>
>>>
>>> 2014-03-05 16:24 GMT+01:00 Simon Schneider <schneida.simon at gmail.com>:
>>>
>>> > Sorry forgot about logs. I set log level = 0 in the smb.conf because I
>>> > read some suggestions on the internet that logging may cause issues,
>>> but
>>> > that didn't help either. What is a decent log level to get just enough
>>> > debug to analyse this problem?
>>> >
>>> > I found this error message in log.smbd:
>>> > [2014/03/05 09:27:39.052897, 0]
>>> > ../source3/smbd/smbXsrv_open.c:1035(smbXsrv_open_close)
>>> > smbXsrv_open_close(0x64966b36): failed to delete global key
>>> '64966B36':
>>> > NT_STATUS_NOT_FOUND
>>> > [2014/03/05 09:27:39.052949, 0]
>>> > ../source3/smbd/smbXsrv_open.c:759(smbXsrv_open_destructor)
>>> > smbXsrv_open_destructor: smbXsrv_open_close() failed -
>>> > NT_STATUS_NOT_FOUND
>>> > [2014/03/05 09:27:39.053009, 0]
>>> > ../source3/smbd/close.c:268(close_remove_share_mode)
>>> > close_remove_share_mode: Could not get share mode lock for file
>>> > Facebook-Seite/Präsentation1.gif
>>> > [2014/03/05 09:27:39.053082, 0]
>>> > ../source3/smbd/smbXsrv_open.c:1035(smbXsrv_open_close)
>>> > smbXsrv_open_close(0xfbd9df83): failed to delete global key
>>> 'FBD9DF83':
>>> > NT_STATUS_NOT_FOUND
>>> > [2014/03/05 09:27:39.053629, 0]
>>> > ../source3/smbd/smbXsrv_open.c:759(smbXsrv_open_destructor)
>>> > smbXsrv_open_destructor: smbXsrv_open_close() failed -
>>> > NT_STATUS_NOT_FOUND
>>> > [2014/03/05 09:27:39.053708, 0]
>>> > ../source3/smbd/close.c:268(close_remove_share_mode)
>>> > close_remove_share_mode: Could not get share mode lock for file
>>> > Facebook-Seite/Thumbs.db
>>> > [2014/03/05 09:27:39.053833, 0]
>>> > ../source3/smbd/smbXsrv_open.c:1035(smbXsrv_open_close)
>>> > smbXsrv_open_close(0x04caead4): failed to delete global key
>>> '04CAEAD4':
>>> > NT_STATUS_NOT_FOUND
>>> > [2014/03/05 09:27:39.053895, 0]
>>> > ../source3/smbd/smbXsrv_open.c:759(smbXsrv_open_destructor)
>>> > smbXsrv_open_destructor: smbXsrv_open_close() failed -
>>> > NT_STATUS_NOT_FOUND
>>> > [2014/03/05 09:27:39.053945, 0]
>>> > ../source3/smbd/close.c:1062(close_directory)
>>> > close_directory: Could not get share mode lock for .
>>> > [2014/03/05 09:27:39.053992, 1]
>>> ../source3/smbd/service.c:1122(close_cnum)
>>> > 10.10.20.25 (ipv4:10.10.20.25:61595) closed connection to service
>>> Fotos
>>> > [2014/03/05 09:27:39.054152, 0]
>>> > ../source3/smbd/smbXsrv_tcon.c:1021(smbXsrv_tcon_disconnect_all)
>>> > smbXsrv_tcon_disconnect_all: count[1] errors[1]
>>> > first[NT_STATUS_NOT_FOUND]
>>> > [2014/03/05 09:27:39.054467, 0]
>>> > ../source3/smbd/server_exit.c:121(exit_server_common)
>>> > Server exit (termination signal)
>>> > [2014/03/05 09:27:39.054566, 0]
>>> > ../source3/smbd/server_exit.c:124(exit_server_common)
>>> > exit_server_common: smb1srv_tcon_disconnect_all() failed
>>> > (NT_STATUS_NOT_FOUND) - triggering cleanup
>>> > [2014/03/05 09:27:39.054679, 0]
>>> > ../source3/smbd/smbXsrv_session.c:1336(smbXsrv_session_logoff)
>>> > smbXsrv_session_logoff(0xae36cf4a): failed to delete global key
>>> > 'AE36CF4A': NT_STATUS_NOT_FOUND
>>> > [2014/03/05 09:27:39.054801, 0] ../lib/util/fault.c:72(fault_report)
>>> > ===============================================================
>>> > [2014/03/05 09:27:39.054900, 0] ../lib/util/fault.c:73(fault_report)
>>> > INTERNAL ERROR: Signal 11 in pid 6477 (4.1.5-SerNet-Debian-7.wheezy)
>>> > Please read the Trouble-Shooting section of the Samba HOWTO
>>> > [2014/03/05 09:27:39.055068, 0] ../lib/util/fault.c:75(fault_report)
>>> > ===============================================================
>>> > [2014/03/05 09:27:39.055166, 0]
>>> ../source3/lib/util.c:785(smb_panic_s3)
>>> > PANIC (pid 6477): internal error
>>> > [2014/03/05 09:27:39.056113, 0]
>>> ../source3/lib/util.c:896(log_stack_trace)
>>> > BACKTRACE: 29 stack frames:
>>> > #0
>>> /usr/lib/i386-linux-gnu/samba/libsmbconf.so.0(log_stack_trace+0x29)
>>> > [0xb71bc4f4]
>>> > #1 /usr/lib/i386-linux-gnu/samba/libsmbconf.so.0(smb_panic_s3+0x76)
>>> > [0xb71bc61b]
>>> > #2 /usr/lib/i386-linux-gnu/samba/libsamba-util.so.0(smb_panic+0x3a)
>>> > [0xb77016c0]
>>> > #3
>>> >
>>> /usr/lib/i386-linux-gnu/samba/libsamba-util.so.0(base64_decode_data_blob_talloc+0)
>>> > [0xb7701a50]
>>> > #4 [0xb7746400]
>>> > #5 /usr/lib/i386-linux-gnu/samba/libsmbd_base.so(close_file+0x40)
>>> > [0xb74cb2fe]
>>> > #6
>>> /usr/lib/i386-linux-gnu/samba/libsmbd_base.so(file_close_user+0x55)
>>> > [0xb7468248]
>>> > #7
>>> >
>>> /usr/lib/i386-linux-gnu/samba/libsmbd_base.so(smbXsrv_session_logoff+0x3fa)
>>> > [0xb751c6d0]
>>> > #8 /usr/lib/i386-linux-gnu/samba/libsmbd_base.so(+0x14d853)
>>> [0xb751c853]
>>> > #9 /usr/lib/i386-linux-gnu/samba/libdbwrap.so(+0x5483) [0xb6aa1483]
>>> > #10 /usr/lib/i386-linux-gnu/samba/libdbwrap.so(+0x55c0) [0xb6aa15c0]
>>> > #11 /usr/lib/i386-linux-gnu/samba/libdbwrap.so(dbwrap_traverse+0x2d)
>>> > [0xb6a9f375]
>>> > #12
>>> >
>>> /usr/lib/i386-linux-gnu/samba/libsmbd_base.so(smbXsrv_session_logoff_all+0xbf)
>>> > [0xb751c9fa]
>>> > #13 /usr/lib/i386-linux-gnu/samba/libsmbd_base.so(+0x153fe5)
>>> > [0xb7522fe5]
>>> > #14 /usr/lib/i386-linux-gnu/samba/libsmbd_base.so(+0x154494)
>>> > [0xb7523494]
>>> > #15
>>> > /usr/lib/i386-linux-gnu/samba/libsmbd_shim.so(exit_server_cleanly+0x22)
>>> > [0xb71119c9]
>>> > #16 /usr/lib/i386-linux-gnu/samba/libsmbd_base.so(+0x1132c7)
>>> > [0xb74e22c7]
>>> > #17
>>> >
>>> /usr/lib/i386-linux-gnu/samba/libtevent.so.0(tevent_common_check_signal+0x18b)
>>> > [0xb73c86b9]
>>> > #18
>>> /usr/lib/i386-linux-gnu/samba/libsmbconf.so.0(run_events_poll+0x24)
>>> > [0xb71ddfed]
>>> > #19 /usr/lib/i386-linux-gnu/samba/libsmbconf.so.0(+0x40349)
>>> [0xb71de349]
>>> > #20
>>> > /usr/lib/i386-linux-gnu/samba/libtevent.so.0(_tevent_loop_once+0xb1)
>>> > [0xb73c52f5]
>>> > #21
>>> /usr/lib/i386-linux-gnu/samba/libsmbd_base.so(smbd_process+0x1182)
>>> > [0xb74e97e6]
>>> > #22 /usr/sbin/smbd(+0x8111) [0xb776d111]
>>> > #23
>>> > /usr/lib/i386-linux-gnu/samba/libsmbconf.so.0(run_events_poll+0x2ce)
>>> > [0xb71de297]
>>> > #24 /usr/lib/i386-linux-gnu/samba/libsmbconf.so.0(+0x4043b)
>>> [0xb71de43b]
>>> > #25
>>> > /usr/lib/i386-linux-gnu/samba/libtevent.so.0(_tevent_loop_once+0xb1)
>>> > [0xb73c52f5]
>>> > #26 /usr/sbin/smbd(main+0x1cf9) [0xb776f5ae]
>>> > #27 /lib/i386-linux-gnu/i686/cmov/libc.so.6(__libc_start_main+0xe6)
>>> > [0xb6c47e46]
>>> > #28 /usr/sbin/smbd(+0x4751) [0xb7769751]
>>> > [2014/03/05 09:27:39.058493, 0]
>>> ../source3/lib/dumpcore.c:317(dump_core)
>>> > dumping core in /var/log/samba/cores/smbd
>>> > [2014/03/05 09:39:16.276046, 1]
>>> > ../source3/smbd/service.c:1122(close_cnum)
>>> > 10.10.20.149 (ipv4:10.10.20.149:57653) closed connection to service
>>> > sysvol
>>> > [2014/03/05 09:41:36.306911, 1]
>>> ../source3/smbd/service.c:1122(close_cnum)
>>> > 10.10.20.109 (ipv4:10.10.20.109:49178) closed connection to service
>>> > AnotherShare
>>> > [2014/03/05 09:41:36.308606, 1]
>>> > ../source3/smbd/service.c:1122(close_cnum)
>>> > 10.10.20.109 (ipv4:10.10.20.109:49178) closed connection to service
>>> C203
>>> > [2014/03/05 09:41:36.313183, 1]
>>> > ../source3/smbd/service.c:1122(close_cnum)
>>> > 10.10.20.109 (ipv4:10.10.20.109:49178) closed connection to service
>>> > sysvol
>>> > [2014/03/05 09:41:36.314940, 1]
>>> > ../source3/smbd/service.c:1122(close_cnum)
>>> > 10.10.20.109 (ipv4:10.10.20.109:49178) closed connection to service
>>> > SomeShare
>>> > [2014/03/05 09:41:36.316339, 1]
>>> ../source3/smbd/service.c:1122(close_cnum)
>>> > 10.10.20.109 (ipv4:10.10.20.109:49178) closed connection to service
>>> > Profiles
>>> > [2014/03/05 09:41:36.317337, 1]
>>> > ../source3/smbd/service.c:1122(close_cnum)
>>> > 10.10.20.109 (ipv4:10.10.20.109:49178) closed connection to service
>>> > netlogon
>>> > [2014/03/05 09:41:36.318201, 1]
>>> > ../source3/smbd/service.c:1122(close_cnum)
>>> > 10.10.20.109 (ipv4:10.10.20.109:49178) closed connection to service
>>> home
>>> > [2014/03/05 09:41:36.320192, 1]
>>> ../source3/smbd/service.c:1122(close_cnum)
>>> > 10.10.20.109 (ipv4:10.10.20.109:49178) closed connection to service
>>> > GemeinsameDateien
>>> > [2014/03/05 09:46:05.055771, 1]
>>> > ../source3/smbd/service.c:1122(close_cnum)
>>> > 10.10.20.25 (ipv4:10.10.20.25:61596) closed connection to service
>>> Fotos
>>> > [2014/03/05 09:46:05.056703, 1]
>>> > ../source3/smbd/service.c:1122(close_cnum)
>>> > 10.10.20.133 (ipv4:10.10.20.133:52612) closed connection to service
>>> > GemeinsameDateien
>>> > [2014/03/05 09:46:05.060982, 1]
>>> > ../source3/smbd/service.c:1122(close_cnum)
>>> > 10.10.20.109 (ipv4:10.10.20.109:49178) closed connection to service
>>> > Fotos
>>> > [2014/03/05 09:46:07, 0] ../source3/smbd/server.c:1198(main)
>>> > smbd version 4.1.5-SerNet-Debian-7.wheezy started.
>>> > Copyright Andrew Tridgell and the Samba Team 1992-2013
>>> >
>>> > At that time I did a restart of the server (if I'm not mistaken I was
>>> > trying the max_protocol directive at that time...). There are also
>>> files in
>>> > the core directory which appear to be binary though...
>>> >
>>> > Thanks!
>>> >
>>> >
>>> >
>>> >
>>> > 2014-03-05 16:14 GMT+01:00 Simon Schneider <schneida.simon at gmail.com>:
>>> >
>>> > Thanks for your reply.
>>> >>
>>> >> Here is my smb.conf:
>>> >>
>>> >> [global]
>>> >> workgroup = ABC-ABCDEF
>>> >> realm = ABC-ABCDEF.LAN
>>> >> netbios name = ABCSERVER
>>> >> server role = active directory domain controller
>>> >> dns forwarder = 10.10.20.20
>>> >> idmap_ldb:use rfc2307 = yes
>>> >> load printers = yes
>>> >> log level = 0
>>> >>
>>> >> [netlogon]
>>> >> path = /var/lib/samba/sysvol/asb-alkoven.lan/scripts
>>> >> read only = No
>>> >>
>>> >> [sysvol]
>>> >> path = /var/lib/samba/sysvol
>>> >> read only = No
>>> >>
>>> >> [printers]
>>> >> path = /var/spool/samba
>>> >> printable = yes
>>> >> printing = CUPS
>>> >>
>>> >> [print$]
>>> >> path = /srv/samba/PrinterDrivers
>>> >> comment = Printer Drivers
>>> >> writeable = yes
>>> >>
>>> >> [Profiles]
>>> >> path = /srv/samba/Profiles
>>> >> read only = no
>>> >>
>>> >> [home]
>>> >> path = /srv/samba/home
>>> >> read only = no
>>> >>
>>> >> [GemeinsameDateien]
>>> >> path = /srv/samba/GemeinsameDateien
>>> >> read only = no
>>> >>
>>> >> [... 3 more shares following exactly the same pattern as
>>> >> "GemeinsameDateien"..]
>>> >>
>>> >>
>>> >> I'm running samba version 4.1.5-SerNet-Debian-7.wheezy on debian i686.
>>> >> The machine has 4GB RAM and an Intel Core 2 Duo, so performance of the
>>> >> server itself should not matter (there are at max 5-8 users accessing
>>> files
>>> >> but mostly docs, some pictures).
>>> >>
>>> >> The problem happens on our existing windows 7 clients as well as one
>>> that
>>> >> a did a fresh install on, installed alle MS updates and is not yet
>>> joined
>>> >> to the domain, so my applied GPOs should not change anything either.
>>> Also
>>> >> clients access the server via IP, so no DNS problem either.
>>> >>
>>> >> Thanks again for your input!
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> 2014-03-05 15:53 GMT+01:00 Marty Sweet <msweet.dev at gmail.com>:
>>> >>
>>> >> Hi,
>>> >>>
>>> >>> Could you post your smb.conf? Our production Samba 4 servers work a
>>> >>> treat but our older Samba 3 servers had this issue occasionally.
>>> >>> Is there also any error messages in your logging directory?
>>> >>>
>>> >>> Thanks,
>>> >>> Marty Sweet
>>> >>>
>>> >>> On 5 March 2014 09:26, Simon Schneider <schneida.simon at gmail.com>
>>> wrote:
>>> >>> > I'm experiencing extremely slow performance when trying to copy
>>> files
>>> >>> from
>>> >>> > and to a samba 4 share. I'm using Debian and the Samba 4 SerNet
>>> >>> packages
>>> >>> > and everything is up to date on the client as well as on the
>>> server.
>>> >>> The
>>> >>> > connection is made through 100Mbp/s ethernet, but the problem also
>>> >>> exists
>>> >>> > on a local virtual machine that runs on the Debian server.
>>> >>> >
>>> >>> > By extremely I mean really abysmal:
>>> >>> >
>>> >>> > * Copying a folder with 50 files total size 10 MB to Win7: ~ 20
>>> >>> minutes at
>>> >>> > 3-4 Kb/s
>>> >>> > * Copying the same folder to Windows Server 2003: ~ 3 seconds
>>> >>> > * Copying the same folder with ROBOCOPY to Win 7: ~3 seconds
>>> >>> > * Copying a large random file 500 MB to Win 7: Takes ages to start
>>> copy
>>> >>> > progress than up to 10 MB/s
>>> >>> > * Copying the same large file to Windows Server 2003: Starts
>>> >>> immediately to
>>> >>> > copy and takes a few seconds
>>> >>> > * Copying the same large file with ROBOCOPY using Win7: also decent
>>> >>> > performance, no delays
>>> >>> >
>>> >>> > I already googled for days and found a lot of suggestions to:
>>> >>> >
>>> >>> > * Changes switches: one of the test machines runs as VM on host, so
>>> >>> this is
>>> >>> > not the issue
>>> >>> > * Update network drivers: same thing, using different machines and
>>> a
>>> >>> VM the
>>> >>> > problem exists on all of them
>>> >>> > * Turn off Remote Differential compression on the client: Didn't
>>> help
>>> >>> at all
>>> >>> > * Disable autotuning on the client with netsh: Didn't help at all
>>> >>> > * Make sure not to use mapped drives but UNC paths instead: Did
>>> help
>>> >>> when
>>> >>> > logging in but has no effect on file transfer
>>> >>> > * Try switching max protocol on the samba server to something like
>>> >>> NT1: did
>>> >>> > not help
>>> >>> > * Do not use any other custom smb.conf options like socket etc.
>>> >>> >
>>> >>> > What is the big difference between using Windows File Explorer and
>>> >>> > Robocopy? I mean, I cant force my users to copy files with robocopy
>>> >>> from
>>> >>> > now on.... grml...
>>> >>> >
>>> >>> > Thanks for help!
>>> >>> > --
>>> >>> > To unsubscribe from this list go to the following URL and read the
>>> >>> > instructions: https://lists.samba.org/mailman/options/samba
>>> >>>
>>> >>
>>> >>
>>> >
>>> --
>>> To unsubscribe from this list go to the following URL and read the
>>> instructions: https://lists.samba.org/mailman/options/samba
>>>
>>
>>
More information about the samba
mailing list