This repository was archived by the owner on Feb 24, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 49
When IOR deletes an MPI-IO file, it might not delete it #17
Comments
Here's a patch:
|
I should have added it was poor Florin Isaila [email protected] who encountered this and came up with the fix. I just updated the patch to apply onto master and to match IOR's coding conventions. |
I found a problem with the patch. See the pull request I'm just about to generate. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
ROMIO allows you to prefix a file with something to specify a file system driver and override ROMIO's automatic detection. We might do this if, for example, PVFS is available, but the kernel module is not installed (
pvfs:/path/to/pvfs/testfile
), or if we simply wish to avoid the overhead of stat (ufs:/regular/unix/file_system
)When IOR attempts to remove a file with such a prefix, it makes a call to the POSIX routine
access()
, but does not remove the prefix before doing so.access()
does not returnF_OK
, naturally, and so does not attempt to remove the file. IOR doesn't complain about this, so we ended up thinking we were running tests of "create a new file" when actually we were "reusing existing file."The text was updated successfully, but these errors were encountered: