CIFS :: user lost lock on file after time

[jenoptik]

Hello Forum,

Sometimes we notice a strange problem with accessing files, keeping locks and user access to files.

Our users got mapped network drive that points to a filer. They open a file (for example an excel sheet) and kept it open.

After a while (for example 3 hours) another user tries to open that file and DOESN'T get a message that this file is in use by the first one.

If the person tries this after a shorter amount of time (for example 10 minutes) it does get a message.

Why?

I thought that it should have to do with loosing locks, so I think that the protocol (CIFS) forum is the right place for this question.

Do you have any idea why users can loose there locks after a while?

Maybe, there is an option for that timeout?

How to troubleshoot this issue?

Best regards,

jenoptik

[hariprak · Accepted solution]

Hi,

Refer this KB article How to break Common Internet File System Protocol (CIFS) locks from a Windows host,
https://kb.netapp.com/support/s/article/how-to-break-common-internet-file-system-protocol-cifs-locks-from-a-windows-host

Thanks

[JaydenYoo]

I have the same issue you were facing before. 

The fist user opened a file (DOC), the secound user can open the same file without seeing a message " file in use for editing" 

Have you solved this issue ? then how to resolve this issue??

Thank you for your help in advance

[maffo]

This is a known behavior of softwares like Word and Excel (but also some UNIX editors like VI).

When a user opens a document in Word, a temporary file will be created and the user will in fact be working on the temporary copy of the file.
For further info on this please see https://support.microsoft.com/en-us/help/211632/description-of-how-word-creates-temporary-files

[JaydenYoo]

HI, 

I have the same issue you were facing. I dont have any idea about that. 

this is really randomly. user a opend a file then user b also opend the same file after a few hours without a warning message.

I want to know how to resolve this strange issue.