python file does not exist_python – os.path.exists()的谎言

File Handle Caching

Directories cache file names to file handles mapping. The most common problems with this are:

?You have an opened file, and you need to check if the file has been replaced by a newer file. You have to flush the parent directory’s file handle cache before stat() returns the new file’s information and not the opened file’s.

?Actually this case has another problem: The old file may have been deleted and replaced by a new file, but both of the files may have the same inode. You can check this case by flushing the open file’s attribute cache and then seeing if fstat() fails with ESTALE.

?You need to check if a file exists. For example a lock file. Kernel may have cached that the file does not exist, even if in reality it does. You have to flush the parent directory’s negative file handle cache to to see if the file really exists.

A few ways to flush the file handle cache:

?If the parent directory’s mtime changed, the file handle cache gets flushed by flushing its attribute cache. This should work quite well if the NFS server supports nanosecond or microsecond resolution.

?Linux: chown() the directory to its current owner. The file handle cache is flushed if the call returns successfully.

?Solaris 9, 10: The only way is to try to rmdir() the parent directory. ENOTEMPTY means the cache is flushed. Trying to rmdir() the current directory fails with EINVAL and doesn’t flush the cache.

?FreeBSD 6.2: The only way is to try to rmdir() either the parent directory or the file under it. ENOTEMPTY, ENOTDIR and EACCES failures mean the cache is flushed, but ENOENT did not flush it. FreeBSD does not cache negative entries, so they do not have to be flushed.