Re: [OMPI users] File locking in ADIO, OpenMPI 1.6.4

2014-09-19 Thread Edgar Gabriel
appens with a much faster MPI_File_write_at_all. We wrote this up in our 2005 shared memory for shared file pointers paper, even though this approach doesn't need RMA shared memory. ==rob Thanks, Beichuan -Original Message- From: users [mailto:users-boun...@open-mpi.org] On Behalf Of Rob

Re: [OMPI users] File locking in ADIO, OpenMPI 1.6.4

2014-09-18 Thread Rob Latham
-boun...@open-mpi.org] On Behalf Of Rob Latham Sent: Thursday, September 18, 2014 08:49 To: us...@open-mpi.org Subject: Re: [OMPI users] File locking in ADIO, OpenMPI 1.6.4 On 09/17/2014 05:46 PM, Beichuan Yan wrote: Hi Rob, As you pointed out in April that there are many cases that could arous

Re: [OMPI users] File locking in ADIO, OpenMPI 1.6.4

2014-09-18 Thread Beichuan Yan
and the actual I/O happens with a much faster MPI_File_write_at_all. We wrote this up in our 2005 shared memory for shared file pointers paper, even though this approach doesn't need RMA shared memory. ==rob > Thanks, > Beichuan > > -Original Message- > From: user

Re: [OMPI users] File locking in ADIO, OpenMPI 1.6.4

2014-09-18 Thread Rob Latham
h this approach doesn't need RMA shared memory. ==rob Thanks, Beichuan -Original Message- From: users [mailto:users-boun...@open-mpi.org] On Behalf Of Rob Latham Sent: Monday, April 14, 2014 14:24 To: Open MPI Users Subject: Re: [OMPI users] File locking in ADIO, OpenMPI 1.6.4

Re: [OMPI users] File locking in ADIO, OpenMPI 1.6.4

2014-09-17 Thread Beichuan Yan
-2 parallel IO? Thanks, Beichuan -Original Message- From: users [mailto:users-boun...@open-mpi.org] On Behalf Of Rob Latham Sent: Monday, April 14, 2014 14:24 To: Open MPI Users Subject: Re: [OMPI users] File locking in ADIO, OpenMPI 1.6.4 On 04/08/2014 05:49 PM, Daniel Milroy wrote: > He

Re: [OMPI users] File locking in ADIO, OpenMPI 1.6.4

2014-04-16 Thread Sasso, John (GE Power & Water, Non-GE)
: Open MPI Users Subject: Re: [OMPI users] File locking in ADIO, OpenMPI 1.6.4 Hi Rob, The applications of the two users in question are different; I haven¹t looked through much of either code. I can respond to your highlighted situations in sequence: >- everywhere in NFS. If you have a Lus

Re: [OMPI users] File locking in ADIO, OpenMPI 1.6.4

2014-04-15 Thread Daniel Milroy
Hi Rob, The applications of the two users in question are different; I haven¹t looked through much of either code. I can respond to your highlighted situations in sequence: >- everywhere in NFS. If you have a Lustre file system exported to some >clients as NFS, you'll get NFS (er, that might no

Re: [OMPI users] File locking in ADIO, OpenMPI 1.6.4

2014-04-14 Thread Rob Latham
On 04/08/2014 05:49 PM, Daniel Milroy wrote: Hello, The file system in question is indeed Lustre, and mounting with flock isn’t possible in our environment. I recommended the following changes to the users’ code: Hi. I'm the ROMIO guy, though I do rely on the community to help me keep the

Re: [OMPI users] File locking in ADIO, OpenMPI 1.6.4

2014-04-14 Thread Daniel Milroy
Subject: Re: [OMPI users] File locking in ADIO, OpenMPI 1.6.4 Sorry for the delay in replying. Can you try upgrading to Open MPI 1.8, which was released last week? We refreshed the version of ROMIO that is included in OMPI 1.8 vs. 1.6. On Apr 8, 2014, at 6:49 PM, Daniel Milroy wrote: > He

Re: [OMPI users] File locking in ADIO, OpenMPI 1.6.4

2014-04-11 Thread Jeff Squyres (jsquyres)
Sorry for the delay in replying. Can you try upgrading to Open MPI 1.8, which was released last week? We refreshed the version of ROMIO that is included in OMPI 1.8 vs. 1.6. On Apr 8, 2014, at 6:49 PM, Daniel Milroy wrote: > Hello, > > Recently a couple of our users have experienced diffic

[OMPI users] File locking in ADIO, OpenMPI 1.6.4

2014-04-08 Thread Daniel Milroy
Hello, Recently a couple of our users have experienced difficulties with compute jobs failing with OpenMPI 1.6.4 compiled against GCC 4.7.2, with the nodes running kernel 2.6.32-279.5.2.el6.x86_64. The error is: File locking failed in ADIOI_Set_lock(fd 7,cmd F_SETLKW/7,type F_WRLCK/1,whence 0