I am running Fedora 17 in 64-bits mode.
Samba is configured and is working more or less correctly - at first look. I can access Samba from my Win7 computer and read/write some files and folders.
However reading large files from Samba to Win7 fails after a few seconds (transfer fails).
I checked the log, performed some tests and some investigations and here's the info, but I couldn't find an explanation/solution.
- opening/browsing through directories work fine ; copying smaller files works fine ; writing gigabytes of files works fine (although a bit slow)
- the problem is not caused by the filesystem I use (zfs-fuse) because it is reproduced the same way with files on the main filesystem
- there seem to be some "communication/protocol" problem with the Windows client because after trying several files Win7 eventually crashes (blue screen...) ! On the Fedora/Samba server, i seems to be ok, server seems to be running fine !
- I believe the network is ok because FTP works ok and the same network cable/setup works ok when I perform Windows-to-windows Samba (dual boot)[COLOR="Silver"]
- There was a <not enough disk space> error when doing start/stop smb.service whereas there was plenty of disk space. This warning was fixed by change of an entry in /etc/systcl.conf file from 8192 to 30000 but the file copy from SMB to Win7 problem remains (entry is fs.inotify.max_users_waaaaatches - see PS below...)
- log.smbd contains:
[2012/06/25 21:23:24.784078, 1] lib/serverid.c:197(serverid_deregister)
Deleting serverid.tdb record failed: NT_STATUS_NOT_FOUND
[2012/06/25 21:23:24.784255, 1] smbd/server.c:309(remove_child_pid)
Could not remove pid 9005 from serverid.tdb
[2012/06/25 21:23:24.784342, 1] smbd/server.c:323(remove_child_pid)
Could not find child 9005 -- ignoring
Any suggestions ? Where may I look for more informations ?
PS: I had to write 'fs.inotify.max_users_waaaaatches' with too many 'a' because this forum was always rejecting my post due to "forbidden keyword" !