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

I have a Windows 2008 R2 server where I do a lot of processing and store huge data sets. I have several computers all doing local processing, fetching and returning data to the server.

I have noticed that sometimes when I create a file from machine A on the server, it can take up to several minutes before machine X can see it. It is like that the file is only available to the machine that created it (and perhaps the server).

This means that when machine X tries to determine if machine A has begun its processing or delivered the results, it might get a wrong answer, since it cannot see the files created by machine A.

What I know:

  • Windows 2008 R2
  • No DFS
  • Shadow copying each hour
  • N x 146GB SAS disks in Raid-5
  • Gbit networking
  • Clients are Windows 7 x64

I would like some advice to help me narrow down the problem. Is it Windows, is it the file system cache, is it network related or maybe something completely different?

share|improve this question

I would take a look at the SMB cache values and how frequently its set to fetch metadata. This would only be relevant if both machines in each setup were Windows 2008/utilizing SMB2.

The part on troubleshooting the impact of these caches may be useful, since a minute or two delay is far beyond the defined times.

share|improve this answer
The local computers are all running Windows 7 x64. – Chau Mar 20 '13 at 15:16
Ah that works too. SMB2 will run as long as both ends of the connection are running the Vista/7/2008 core. – Univ426 Mar 20 '13 at 15:27

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.