SMB1 Locked file for roaming clients
realrichardsharpe at gmail.com
Thu Jun 18 08:46:45 MDT 2015
On Thu, Jun 18, 2015 at 5:08 AM, Volker Lendecke <Volker.Lendecke at sernet.de>
> On Thu, Jun 18, 2015 at 02:22:25PM +0300, Uri Simchoni wrote:
> > Thanks! This does not seem applicable to my case as the roaming client
> > gets a different IP address. However I think it validates the analysis
> > that it's an smb1 issue, best solved by moving to smb2.
> You might also try playing with socket options to lower the
> timeouts until smbd detects a client is dead. Look for
> TCP_KEEP* in "man tcp".
There was a bug in 3.6.xx up until 16 or so where Samba was not detecting
that the socket had disappeared when a write to the socket failed (it was
not passing the info back up the stack) ... and smbds were hanging around
far longer than they should have and thus holding a record in locking.tdb.
More information about the samba-technical