<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Indeed, I confirmed your in Intel® MPI Library</title>
    <link>https://community.intel.com/t5/Intel-MPI-Library/MPI-File-write-shared-problem/m-p/1081548#M4894</link>
    <description>&lt;P&gt;Indeed, I confirmed your findings with our engineering team. They&amp;nbsp;might be looking to implement a&amp;nbsp;more portable solution in future releases and your input was very valuable.&lt;/P&gt;</description>
    <pubDate>Tue, 18 Apr 2017 00:10:21 GMT</pubDate>
    <dc:creator>Mark_L_Intel</dc:creator>
    <dc:date>2017-04-18T00:10:21Z</dc:date>
    <item>
      <title>MPI_File_write_shared problem</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/MPI-File-write-shared-problem/m-p/1081546#M4892</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;there seems to be a problem with some versions of intelmpi and file access with mpi shared file pointers. The files are not written correctly. We are using intelmpi 2017 on a cluster with gpfs filesystem. The linux kernel version is 3.10.0-327.36.3.el7.x86_64&lt;/P&gt;

&lt;P&gt;Here is a code that reproduce the problem.&lt;/P&gt;

&lt;PRE class="brush:cpp;"&gt;#include &amp;lt;stdio.h&amp;gt;
#include &amp;lt;stdlib.h&amp;gt;
#include &amp;lt;mpi.h&amp;gt;

int main(int argc, char *argv[])
{
  char string[256];
  char file_name[] = "output";
  int count, slength;
  int open_error;
  int rank;
  MPI_File fh;
  MPI_Status status;

  MPI_Init(&amp;amp;argc, &amp;amp;argv);
  MPI_Comm_rank(MPI_COMM_WORLD, &amp;amp;rank);

  sprintf(string,"Rank : %d\n",rank);
  slength=strlen(string);

  open_error = MPI_File_open(MPI_COMM_WORLD, file_name, MPI_MODE_CREATE | MPI_MODE_WRONLY, MPI_INFO_NULL, &amp;amp;fh);
  if(open_error!=MPI_SUCCESS)
  {
    fprintf(stderr,"Error opening file\n");
    MPI_Abort(MPI_COMM_WORLD,open_error);
  }
  MPI_File_write_shared(fh, string, slength, MPI_CHAR, &amp;amp;status);
  MPI_Get_count(&amp;amp;status,MPI_CHAR,&amp;amp;count);
  if(slength!=count)
  {
    fprintf(stderr,"rank %d: slength=%d , count=%d \n", rank, slength, count);
  }

  MPI_File_close(&amp;amp;fh);
  MPI_Finalize();
  return 0;
}&lt;/PRE&gt;

&lt;P&gt;One example of output is:&lt;/P&gt;

&lt;PRE class="brush:bash;"&gt;$ mpirun -np 10 ./mpi_shared ; cat output | sort -n -k 3
Rank : 2
Rank : 8
Rank : 9&lt;/PRE&gt;

&lt;P&gt;i.e files are truncated.&lt;/P&gt;

&lt;P&gt;Instead with the options:&lt;/P&gt;

&lt;PRE class="brush:bash;"&gt;I_MPI_EXTRA_FILESYSTEM=on
I_MPI_EXTRA_FILESYSTEM_LIST=gpfs
&lt;/PRE&gt;

&lt;P&gt;the mpi api seems to work, at least with this use case.&lt;/P&gt;

&lt;P&gt;I also tested this issue with intelmpi 5.0.3, 5.1.1 and 5.1.3 obtaining the same results as of intel 2017.&lt;/P&gt;

&lt;P&gt;It seems that, if the filesystem is not explicitly specified by means of the I_MPI_EXTRA_FILESYSTEM variables the semantic of MPI_File_write_shared is not compliant with the mpi standard.&lt;/P&gt;

&lt;P&gt;Is it correct for you ?&lt;/P&gt;

&lt;P&gt;Thanks.&lt;/P&gt;

&lt;P&gt;Stefano&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Apr 2017 22:41:50 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/MPI-File-write-shared-problem/m-p/1081546#M4892</guid>
      <dc:creator>stefano_t_</dc:creator>
      <dc:date>2017-04-12T22:41:50Z</dc:date>
    </item>
    <item>
      <title>So what you are reporting is</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/MPI-File-write-shared-problem/m-p/1081547#M4893</link>
      <description>&lt;P&gt;So what you are reporting is that &amp;nbsp;the portable mechanism for synchronizing access to a shared file pointer is not implemented. And&amp;nbsp;the shared file pointer access&amp;nbsp;only works properly&amp;nbsp;if one loads GPFS drivers. I would need to check on this.&lt;/P&gt;</description>
      <pubDate>Sat, 15 Apr 2017 00:21:17 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/MPI-File-write-shared-problem/m-p/1081547#M4893</guid>
      <dc:creator>Mark_L_Intel</dc:creator>
      <dc:date>2017-04-15T00:21:17Z</dc:date>
    </item>
    <item>
      <title>Indeed, I confirmed your</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/MPI-File-write-shared-problem/m-p/1081548#M4894</link>
      <description>&lt;P&gt;Indeed, I confirmed your findings with our engineering team. They&amp;nbsp;might be looking to implement a&amp;nbsp;more portable solution in future releases and your input was very valuable.&lt;/P&gt;</description>
      <pubDate>Tue, 18 Apr 2017 00:10:21 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/MPI-File-write-shared-problem/m-p/1081548#M4894</guid>
      <dc:creator>Mark_L_Intel</dc:creator>
      <dc:date>2017-04-18T00:10:21Z</dc:date>
    </item>
    <item>
      <title>Hi Mark,</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/MPI-File-write-shared-problem/m-p/1081549#M4895</link>
      <description>&lt;P&gt;Hi Mark,&lt;/P&gt;

&lt;P&gt;many thanks you for your attention.&lt;/P&gt;

&lt;P&gt;Stefano&lt;/P&gt;</description>
      <pubDate>Tue, 18 Apr 2017 08:24:33 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/MPI-File-write-shared-problem/m-p/1081549#M4895</guid>
      <dc:creator>stefano_t_</dc:creator>
      <dc:date>2017-04-18T08:24:33Z</dc:date>
    </item>
    <item>
      <title>Hi Stefano,</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/MPI-File-write-shared-problem/m-p/1081550#M4896</link>
      <description>&lt;P&gt;Hi Stefano,&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&amp;nbsp; I filed internal ticket to track this issue.&lt;/P&gt;

&lt;P&gt;Thanks,&lt;/P&gt;

&lt;P&gt;Mark&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Apr 2017 06:23:42 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/MPI-File-write-shared-problem/m-p/1081550#M4896</guid>
      <dc:creator>Mark_L_Intel</dc:creator>
      <dc:date>2017-04-19T06:23:42Z</dc:date>
    </item>
    <item>
      <title>Hi, @Mark L.</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/MPI-File-write-shared-problem/m-p/1081551#M4897</link>
      <description>&lt;P&gt;Hi, @Mark L.&lt;/P&gt;

&lt;P&gt;I also encounterred the same problem on the HPC with GPFS and intel MPI. I tried to use&amp;nbsp;&lt;/P&gt;

&lt;PRE class="brush:bash;"&gt;I_MPI_EXTRA_FILESYSTEM=on
I_MPI_EXTRA_FILESYSTEM_LIST=gpfs
&lt;/PRE&gt;

&lt;P&gt;It shows the following error:&lt;/P&gt;

&lt;PRE class="brush:plain;"&gt;[dic17007@cn03 utils]$ srun -n 24 -p debug -t 30 python utils_di.py
srun: job 1443052 queued and waiting for resources

srun: job 1443052 has been allocated resources
[2] ERROR - ADIO_Init(): Can't load libmpi_gpfs.so library: /apps2/intelics/2017/compilers_and_libraries_2017.0.098/linux/mpi/intel64/lib/libmpi_gpfs.so: undefined symbol: ADIOI_IO_Thread_Func
[7] ERROR - ADIO_Init(): Can't load libmpi_gpfs.so library: /apps2/intelics/2017/compilers_and_libraries_2017.0.098/linux/mpi/intel64/lib/libmpi_gpfs.so: undefined symbol: ADIOI_IO_Thread_Func
[8] ERROR - ADIO_Init(): Can't load libmpi_gpfs.so library: /apps2/intelics/2017/compilers_and_libraries_2017.0.098/linux/mpi/intel64/lib/libmpi_gpfs.so: undefined symbol: ADIOI_IO_Thread_Func
[3] ERROR - ADIO_Init(): Can't load libmpi_gpfs.so library: /apps2/intelics/2017/compilers_and_libraries_2017.0.098/linux/mpi/intel64/lib/libmpi_gpfs.so: undefined symbol: ADIOI_IO_Thread_Func
[14] ERROR - ADIO_Init(): Can't load libmpi_gpfs.so library: /apps2/intelics/2017/compilers_and_libraries_2017.0.098/linux/mpi/intel64/lib/libmpi_gpfs.so: undefined symbol: ADIOI_IO_Thread_Func
[22] ERROR - ADIO_Init(): Can't load libmpi_gpfs.so library: /apps2/intelics/2017/compilers_and_libraries_2017.0.098/linux/mpi/intel64/lib/libmpi_gpfs.so: undefined symbol: ADIOI_IO_Thread_Func
[15] ERROR - ADIO_Init(): Can't load libmpi_gpfs.so library: /apps2/intelics/2017/compilers_and_libraries_2017.0.098/linux/mpi/intel64/lib/libmpi_gpfs.so: undefined symbol: ADIOI_IO_Thread_Func
[10] ERROR - ADIO_Init(): Can't load libmpi_gpfs.so library: /apps2/intelics/2017/compilers_and_libraries_2017.0.098/linux/mpi/intel64/lib/libmpi_gpfs.so: undefined symbol: ADIOI_IO_Thread_Func
[12] ERROR - ADIO_Init(): Can't load libmpi_gpfs.so library: /apps2/intelics/2017/compilers_and_libraries_2017.0.098/linux/mpi/intel64/lib/libmpi_gpfs.so: undefined symbol: ADIOI_IO_Thread_Func
[16] ERROR - ADIO_Init(): Can't load libmpi_gpfs.so library: /apps2/intelics/2017/compilers_and_libraries_2017.0.098/linux/mpi/intel64/lib/libmpi_gpfs.so: undefined symbol: ADIOI_IO_Thread_Func
[17] ERROR - ADIO_Init(): Can't load libmpi_gpfs.so library: /apps2/intelics/2017/compilers_and_libraries_2017.0.098/linux/mpi/intel64/lib/libmpi_gpfs.so: undefined symbol: ADIOI_IO_Thread_Func
[6] ERROR - ADIO_Init(): Can't load libmpi_gpfs.so library: /apps2/intelics/2017/compilers_and_libraries_2017.0.098/linux/mpi/intel64/lib/libmpi_gpfs.so: undefined symbol: ADIOI_IO_Thread_Func
[5] ERROR - ADIO_Init(): Can't load libmpi_gpfs.so library: /apps2/intelics/2017/compilers_and_libraries_2017.0.098/linux/mpi/intel64/lib/libmpi_gpfs.so: undefined symbol: ADIOI_IO_Thread_Func
[13] ERROR - ADIO_Init(): Can't load libmpi_gpfs.so library: /apps2/intelics/2017/compilers_and_libraries_2017.0.098/linux/mpi/intel64/lib/libmpi_gpfs.so: undefined symbol: ADIOI_IO_Thread_Func
[23] ERROR - ADIO_Init(): Can't load libmpi_gpfs.so library: /apps2/intelics/2017/compilers_and_libraries_2017.0.098/linux/mpi/intel64/lib/libmpi_gpfs.so: undefined symbol: ADIOI_IO_Thread_Func
[1] ERROR - ADIO_Init(): Can't load libmpi_gpfs.so library: /apps2/intelics/2017/compilers_and_libraries_2017.0.098/linux/mpi/intel64/lib/libmpi_gpfs.so: undefined symbol: ADIOI_IO_Thread_Func
[4] ERROR - ADIO_Init(): Can't load libmpi_gpfs.so library: /apps2/intelics/2017/compilers_and_libraries_2017.0.098/linux/mpi/intel64/lib/libmpi_gpfs.so: undefined symbol: ADIOI_IO_Thread_Func
[0] ERROR - ADIO_Init(): Can't load libmpi_gpfs.so library: /apps2/intelics/2017/compilers_and_libraries_2017.0.098/linux/mpi/intel64/lib/libmpi_gpfs.so: undefined symbol: ADIOI_IO_Thread_Func
[20] ERROR - ADIO_Init(): Can't load libmpi_gpfs.so library: /apps2/intelics/2017/compilers_and_libraries_2017.0.098/linux/mpi/intel64/lib/libmpi_gpfs.so: undefined symbol: ADIOI_IO_Thread_Func
[19] ERROR - ADIO_Init(): Can't load libmpi_gpfs.so library: /apps2/intelics/2017/compilers_and_libraries_2017.0.098/linux/mpi/intel64/lib/libmpi_gpfs.so: undefined symbol: ADIOI_IO_Thread_Func
[11] ERROR - ADIO_Init(): Can't load libmpi_gpfs.so library: /apps2/intelics/2017/compilers_and_libraries_2017.0.098/linux/mpi/intel64/lib/libmpi_gpfs.so: undefined symbol: ADIOI_IO_Thread_Func
[18] ERROR - ADIO_Init(): Can't load libmpi_gpfs.so library: /apps2/intelics/2017/compilers_and_libraries_2017.0.098/linux/mpi/intel64/lib/libmpi_gpfs.so: undefined symbol: ADIOI_IO_Thread_Func
[21] ERROR - ADIO_Init(): Can't load libmpi_gpfs.so library: /apps2/intelics/2017/compilers_and_libraries_2017.0.098/linux/mpi/intel64/lib/libmpi_gpfs.so: undefined symbol: ADIOI_IO_Thread_Func
[9] ERROR - ADIO_Init(): Can't load libmpi_gpfs.so library: /apps2/intelics/2017/compilers_and_libraries_2017.0.098/linux/mpi/intel64/lib/libmpi_gpfs.so: undefined symbol: ADIOI_IO_Thread_Func&lt;/PRE&gt;

&lt;P&gt;Do you have any suggestions to circumvent this problem?&lt;/P&gt;</description>
      <pubDate>Wed, 21 Feb 2018 16:31:54 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/MPI-File-write-shared-problem/m-p/1081551#M4897</guid>
      <dc:creator>Cheng__Di</dc:creator>
      <dc:date>2018-02-21T16:31:54Z</dc:date>
    </item>
  </channel>
</rss>

