Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have a large number of processes that are business specific that have been piling up over the years on a particular server. The developers of these processes have not left much documentation and therefore we have to track down which processes are using what files.

My question is, how can I identify which process on a particular server is reaching out to a remote server share and locking a file on another system?

Here's what I know: I know the server that's connecting I know the file name it's locking

That's about it.

I know this is a very messy config and we're moving away from this but please bare with me on this.

share|improve this question
up vote 1 down vote accepted

You have probably mounted the Samba share. So it should not matter that the files are remote. fuser / lsof should do.

share|improve this answer
Thanks for your suggestion, we were able to trace it down using a script that ultimately uses this command. – Gombly Feb 28 '13 at 18:43

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.