Samba status locked files

I was running into a similar problem, a client crashed while copying a large file and the file was locked after the reboot.

Luckily this does not happen very often, but still it's quite annoying having to kill the samba process. It won't help much anyway, as the man page now says, that it only works with SMB1 which shouldn't be used any more and does nothing on SMB2 and SMB3 connections, the only way left to handle this is mentioned in the thread linked by Micheal.

I don't know the rationale behind the removal and what's so bad about reset on zero vc , I would consider using tcp timeout for this purpose more like a hack. Anyway something reasonable could be e. Note that this increases the load on your network, but I doubt that it's even noticeable even with a lot of clients.

The default oplock type is Level1. Level2 oplocks are enabled on a per-share basis in the smb. Alternately, you could disable oplocks on a per-file basis within the share:. If you are experiencing problems with oplocks, as apparent from Samba's log entries, you may want to play it safe and disable oplocks and Level2 oplocks.

Disabling Kernel Oplocks Kernel oplocks is an smb. This parameter addresses sharing files between UNIX and Windows with oplocks enabled on the Samba server: the UNIX process can open the file that is Oplocked cached by the Windows client and the smbd process will not send an oplock break, which exposes the file to the risk of data corruption. If the UNIX kernel has the ability to send an oplock break, then the kernel oplocks parameter enables Samba to send the oplock break.

Kernel oplocks are enabled on a per-server basis in the smb. While googling my error, I crossed this page a lot. Maybe some one had the same problem and stranded also here:. Sign up to join this community.

The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. How to prevent samba from holding a file lock after a client disconnects? Ask Question.

Asked 11 years, 1 month ago. Active 3 months ago. Viewed 49k times. Here I have a Samba server Debian 5. Is there any way to work around this situation or am I missing something? Improve this question. Jean-Francois Chevrette Jean-Francois Chevrette 2 2 gold badges 6 6 silver badges 8 8 bronze badges.

Add a comment. Active Oldest Votes. Run a "smbstatus". Find the pid of the process that has the lock on the file in the third section of the output. The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day-to-day running - it generates a small amount of information about operations carried out.

Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic.

Note that specifying this parameter here will override the log level parameter in the smb. The file specified contains the configuration details required by the client. Whilst the quickest way to unlock all files is to restart samba, it will result in all users temporarily disconnecting from the server, potentially resulting in data loss. The better option is to find which user has the file open and either get them to close it or kill their Samba process which is locking the file.

First run: smbstatus and find the locked file. Note PID number first column. If list is very long and you are struggling to find the file run: smbstatus grep -i filename.