当我从
@L_301_0@ 10 Pro 64计算机上运行位于Samba共享上的Windows程序时,我得到重复的nobody:nogroup PID条目出现在smbstatus输出中.在smbd进程终止之前,这些条目不会消失.我注意到在我的生产服务器上,Windows 7用户创建的文件可能需要几分钟才能被其他Windows 7用户看到.当我从网络中删除Windows 10计算机时,问题就消失了.
我在Ubuntu 14.04.1 LTS上运行Samba版本4.1.6-Ubuntu.我尝试过Ubuntu 14.04.3 LTS和Ubuntu 15.10服务器并出现同样的问题.我使用的电脑如下:
> 192.1.1.38 – CONSULTING5 – Windows 8.1 Pro
> 192.1.1.41 – CONSULTING7 – Windows 10 Pro
> 192.1.1.42 – CONSULTING8 – Ubuntu Server 14.04.1
下面的smbstatus输出是通过从samba网络共享运行Windows记事本三次产生的.这是从Windows 8.1计算机和Windows 10计算机完成的.在Windows 10计算机上使用一整天后,输出通常会增加到1000行.
- Samba version 4.1.6-Ubuntu
- PID Username Group Machine
- -------------------------------------------------------------------
- 1444 nobody nogroup 192.1.1.41 (ipv4:192.1.1.41:53486)
- 1444 nobody nogroup 192.1.1.41 (ipv4:192.1.1.41:53486)
- 1444 nobody nogroup 192.1.1.41 (ipv4:192.1.1.41:53486)
- 1444 nobody nogroup 192.1.1.41 (ipv4:192.1.1.41:53486)
- 1444 nobody nogroup 192.1.1.41 (ipv4:192.1.1.41:53486)
- 1444 nobody nogroup 192.1.1.41 (ipv4:192.1.1.41:53486)
- 1444 nobody nogroup 192.1.1.41 (ipv4:192.1.1.41:53486)
- 1444 nobody nogroup 192.1.1.41 (ipv4:192.1.1.41:53486)
- 1444 nobody nogroup 192.1.1.41 (ipv4:192.1.1.41:53486)
- 1444 nobody nogroup 192.1.1.41 (ipv4:192.1.1.41:53486)
- 1444 nobody nogroup 192.1.1.41 (ipv4:192.1.1.41:53486)
- 1444 nobody nogroup 192.1.1.41 (ipv4:192.1.1.41:53486)
- 1445 win81user win81user 192.1.1.38 (ipv4:192.1.1.38:50422)
- 1444 win10user win10user 192.1.1.41 (ipv4:192.1.1.41:53486)
- 1444 nobody nogroup 192.1.1.41 (ipv4:192.1.1.41:53486)
- 1444 nobody nogroup 192.1.1.41 (ipv4:192.1.1.41:53486)
- 1444 nobody nogroup 192.1.1.41 (ipv4:192.1.1.41:53486)
- Service pid machine Connected at
- -------------------------------------------------------
- aaa 1444 192.1.1.41 Thu Jan 7 12:29:31 2016
- aaa 1445 192.1.1.38 Thu Jan 7 12:29:53 2016
- Locked files:
- Pid Uid DenyMode Access R/W Oplock SharePath Name Time
- --------------------------------------------------------------------------------------------------
- 1444 1003 DENY_NONE 0x100081 RDONLY NONE /mnt/aaa . Thu Jan 7 12:29:31 2016
- 1445 1002 DENY_NONE 0x100081 RDONLY NONE /mnt/aaa . Thu Jan 7 12:29:52 2016
我尝试了许多不同的samba配置选项,但问题仍然存在.我已经恢复到默认的ubuntu smb.conf,如下所示,添加了单个共享定义.客人ok =是和客人ok =没有选项不解决这个问题.
- [global]
- server string = %h server (Samba,Ubuntu)
- server role = standalone server
- map to guest = Bad User
- obey pam restrictions = Yes
- pam password change = Yes
- passwd program = /usr/bin/passwd %u
- passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
- unix password sync = Yes
- syslog = 0
- log file = /var/log/samba/log.%m
- max log size = 1000
- dns proxy = No
- usershare allow guests = Yes
- panic action = /usr/share/samba/panic-action %d
- idmap config * : backend = tdb
- [printers]
- comment = All Printers
- path = /var/spool/samba
- create mask = 0700
- printable = Yes
- print ok = Yes
- browseable = No
- [print$]
- comment = Printer Drivers
- path = /var/lib/samba/printers
- [aaa]
- comment = aaa test share
- path = /mnt/aaa
- read only = No
我提前道歉但由于我在这个网站上没有声誉,我无法发布两个以上的链接.请在下面的日志级别3中找到共享安装和记事本执行的Samba日志文件的链接.我还为Windows 8.1 smbd进程和Windows 10 smbd进程提供了lsof输出.
- http://pastebin.com/L8HdZAA1 - log.nmbd
- http://pastebin.com/TEbWaB7n - log.smbd
- http://pastebin.com/UAmk0tZG - log.192.1.1.38 (Windows 8.1)
- http://pastebin.com/wtfB5udx - log.consulting5 (Windows 8.1)
- http://pastebin.com/0bAhNqum - log.192.1.1.41 (Windows 10)
- http://pastebin.com/zCKsASR0 - log.consulting7 (Windows 10)
- http://pastebin.com/1wmFVAjC - lsof-win81process.txt
- http://pastebin.com/DyzUF3LS - lsof-win10process.txt
任何帮助解决这个问题将不胜感激.谢谢.
这似乎是SambaV2 / V3的一个问题,可以避免强制Windows 10使用SambaV1
- sc config lanmanworkstation depend= bowser/mrxsmb10/nsi
- sc config mrxsmb20 start= disabled
看到:
https://groups.google.com/forum/#!topic/spline.eisfair/vtxTbxKVy1Q
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1392647