Date: Mon, 28 Nov 2016 22:13:54 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 214917] Samba 4.3.11 (SMB2 or SMB3) on FreeBSD 10.3-RELEASE-p12 crashes with PANIC invalid lock_order because of lock gave errno 9 (Bad file descriptor) Message-ID: <bug-214917-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214917 Bug ID: 214917 Summary: Samba 4.3.11 (SMB2 or SMB3) on FreeBSD 10.3-RELEASE-p12 crashes with PANIC invalid lock_order because of lock gave errno 9 (Bad file descriptor) Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: freebsd@e-schuett.de Created attachment 177496 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D177496&action= =3Dedit logfile smbd Samba 4.3.11 (SMB2 or SMB3) on FreeBSD 10.3-RELEASE-p12 crashes with PANIC invalid lock_order because of lock gave errno 9 (Bad file descriptor) Process: create a backup in an asterisk appliance and store the file= on a windows share. Result: Samba crashes on the destination server with an panic error invalid lock_order & errno 9 (Bad file descriptor) Expected: create & store backup file to NAS Testing: In smb4.conf tested all combinations of "oplock" and "stri= ct locking=E2=80=9C =E2=80=94> nothing changed Separate the backup file (see attachments) and copied this = from source server with smbclient =E2=80=A6=E2=80=99put =E2=80=9C=E2=80=A6=E2=80= =9C* to destination server =E2=80=94> without problems (same with MS Explorer or = Path Finder) Using the build-in function of the Starface appliance to cr= eate and store the backup=20 =E2=80=94> Samba crashes allways on the destination se= rver (see attached logs); file size on dest. disc =3D 0 KB Tried to change target to other disc on NAS =E2=80=94> Samba crashes, see above Traceability: Always Additions: No trouble with SMB access from MS Windows, Apple OSX or ot= her Linux Machines (Ubuntu 14.04). Access with smbclient from Starface appliance to NAS without issues. Source: Phone System/Asterisk Running as VM: VMware vSphere 6 Essential v. 6.0.0. Appliance: Starface (see www.starface.de) OS: CentOS 6/7/8 2.6.32-642.3.1.e16.x86_64 Darwin Kernel Version 15.6.0: Samba: v. 3.6.23-35.el6_8 Java: Server version: Apache Tomcat/6.0.24 Server built: November 13 2015 1656 Server number: 6.0.24.0 OS Name: Linux OS Version: 2.6.32-573.7.1.el6.x86_64 Architecture: amd64w JVM Version: 1.6.0_45-b06 JVM Vendor: Sun Microsystems Inc. Build-In: Create SMB Mount (/mnt/....) (1) =3D=3D> mount /mnt/=E2=80=A6=20 (2) =E2=80=94> if error then stop backup = and display error message else (3) =3D=3D> create temporary ba= ckup file (local disk)=20 (4) if complete then co= py the local temp backup file to the SMB share via mount point /mnt/.. (in this case the function =E2=80=9EFileUtils.copyFile=E2=80=9C will taken (5) =3D=3D> unmount SMB= folder Destination: NAS Appliance Hardware 1x Intel Sunrise Point AHCI SATA controller 1x Seagate ST3000VX000-1CU166, 3 GB, UFS formatted, no issu= es S.M.A.R.T, fsck without results 1x Seagate ST8000AS0002-1NA17Z, 8 GB UFS formatted, no issu= es S.M.A.R.T, fsck without results Appliance: NAS4FREE (see www.nas4free.org) OS: FreeBSD 10.3-RELEASE-p12 Samba: v. 4.3.11 =E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94 shares: BackupSysSMB: /mnt/backupdir (ufs, NFS exported, local, journaled soft-updates, acls) BackupNewSMB: /mnt/BackupNew (ufs, NFS exported, local, soft-updates, acl= s) logs: /mnt/backupdir/BackupHomeServer/logs locks: /mnt/backupdir/samba4/ =E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94 attached files (set debug level to 10): logs: samba_28-11-2016.log samba-daemon_28-11-2016.log samba-system_28-11-2016.log config smb4.conf data backup-MyDOMAIN-1480162653896.sar --=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-214917-13>