If you’ve a distributed application that has to read, write, update and remove many very large (hundreds of megabytes each) files from a set of a file servers. You may intermittently encounter “file not found” error on certain files; even when the files in the same destination directory on that server. As a temporary workaround is to wait a few minutes and try accessing the file again, which would then succeed. So what do you do in this situation? Network captures’re always a good idea in order to get a thorough understanding of what’s happening in the client to server communication. There’re disk bottlenecks to look out for but rarely do you see “not found” type messages as the result of them, but here’s an instance where you can. Split IO can result in this behavior when a large number of hefty files’re accessed simultaneously, ultimately leading the server side redirector (a victim as much as the client in this case) to pass along a STATUS_OBJECT_NAME_NOT_FOUND error since it truly couldn’t find that file-though it was there.
Full Article: AD blog