Intel® MPI Library
Get help with building, analyzing, optimizing, and scaling high-performance computing (HPC) applications.

Error in Intel MPI 3.2.2 MPI I/O

bloewepanasas_com
997 Views
I've been testing the new Intel MPI 3.2.2 release which has support for Panasas' PanFS. I've checked out an evaluation copy of the library, but am running into what I believe is a bug with the use of layout hints to a shared file. For the case of more than 1 thread accessing a file, (N-to-1), this fails as each thread is trying to perform an ioctl call to the file and returning:

"ADIOI_PANFS_OPEN: I/O Error doing ioctl on parent directory to create PanFS file using ioctl: File exists."

I believe that the correct behavior is that one thread will call the CREATE_FILE ioctl on the directory to create the file. If all the threads call the ioctl, however, its a race and only one thread will succeed.

I believe the code should do something like:

If (rank == 0)
{
ioctl(CREATE_FILE);
}
MPI_Barrier()
Open()
Ioctl(QUERY_FILE)
Do work...
Close()

Instead, all threads attempt the ioctl(CREATE_FILE), with only one succeeding and the rest failing.

If it would help, I can provide a test case for this behavior.

Thanks!
0 Kudos
2 Replies
TimP
Honored Contributor III
997 Views
This probably merits a problem report. Register your license key at https:\registrationcenter.intel.com if you haven't already registered, which creates an account at https:\premier.intel.com where you can submit your test case against MPI. As most of the experts watching this page are in much earlier time zones, you should get more timely attention this late in the week by submitting on the site.
Note that Intel MPI requires correct use of the MPI_Init_thread() call when using threads along with MPI, where certain other MPI versions may allow MPI_Init().
0 Kudos
Dmitry_K_Intel2
Employee
997 Views
If it would help, I can provide a test case for this behavior.

Hi,
Thanks for the post!
Could you send me a test case and I'll talk to developers about this issue. My email in the signature - just change _at_ on @.

Best wishes,
Dmitry
dmitry.kuzmin_at_intel.com

0 Kudos
Reply