Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 05 Feb 2016 14:24:05 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 206953] smbd spikes CPU then process dies
Message-ID:  <bug-206953-13@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206953

            Bug ID: 206953
           Summary: smbd spikes CPU then process dies
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs@FreeBSD.org
          Reporter: snackmasterx@gmail.com

I'm seeing high CPU utilization when performing file copy operations from my
samba share to my windows server, and they always seem to hang at 322kb cop=
ied
from my samba share to my local system. When the copy hangs I can use top a=
nd
watch CPU utilization for smbd climb to 100% where it will just sit for a
while. If I wait long enough, then I will receive an error from Windows sta=
ting
there "an unexpected network error has occurred" and smbd will no longer be=
 at
100%. Alternately, if I cancel the copy operation from the windows side the=
n I
will watch smbd stay at 100% for some time before eventually returning to
disappearing. I'm unsure if the process crashes entirely or is just returni=
ng
to a normal state.

That said, I don't seem to have any issues copying data to the samba share =
from
my Windows Server. I can also access data on the zpool from FreeBSD. I have
tried restarting the samba server and even the entire FreeBSD system, but t=
he
behavior seems to remain unchanged.

Environment:
FreeBSD 10.2-p9 (only functions are ZFS and SMB/NFS)
Samba 4.3.3
Windows Server 2012 R2 (fully updated)

I've configured samba for AD user authentication which seems to be working
flawlessly. I am using a domain user to perform my testing

I used google and a lot of web sites until I finally managed to get this
working, so it wouldn't surprise me if this behavior was somehow due to a
poorly configured smb4.conf so please let me know if this seems like it cou=
ld
be contributing to the issue:

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DBEGIN SMB4.CONF=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

[global]

  case sensitive =3D yes
  unix extensions =3D no
  nt acl support =3D yes
  inherit acls =3D no
  map acl inherit =3D yes

       netbios name =3D HOSTNAME
       security =3D ADS
       workgroup =3D REALM
       realm =3D REALM.LOCAL
       socket options =3D TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=3D131072
SO_SNDBUF=3D131072
       use sendfile =3D true

       log file =3D /var/log/samba43/log.%m
       log level =3D 1
       max log size =3D 50

       dedicated keytab file =3D /etc/krb5.keytab
       kerberos method =3D secrets and keytab

       idmap config * : backend =3D tdb
       idmap config * : range =3D 100000-299999
       idmap config REALM : backend =3D rid
       idmap config REALM : range =3D 10000-99999

       winbind separator =3D +
       winbind use default domain =3D yes
       winbind enum users  =3D yes
       winbind enum groups =3D yes
       winbind use default domain =3D yes
       winbind refresh tickets =3D yes



[storage]
   comment =3D Storage Share
   path =3D /transition/storage
   available =3D yes
   browsable =3D yes
   read only =3D no
   public =3D no
   guest ok =3D no
   writable =3D yes
   force group =3D "Domain Users"
   directory mask =3D 0770
   force directory mode =3D 0770
   create mask =3D 0660
   force create mode =3D 0660

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DEND OF FILE=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


So all of the above stated, any ideas on what I could do next to understand=
 why
smbd is spiking the CPU utilization when performing copy operations from the
samba share to my windows server?

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-206953-13>