https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-1478 Lustre <p>Running a MPI-IO task requiring concurrent read locks fail using 1.8.6 clients on a 2.1.1 server. The issue is not present in 2.1.1 clients.</p> <p>Easily duplicated by running a test mpi-io job on a 1.8.6 client. I used this benchmark.<br/> <a href="http://public.lanl.gov/jnunez/benchmarks/mpiiotest.htm" class="external-link" target="_blank" rel="nofollow noopener">http://public.lanl.gov/jnunez/benchmarks/mpiiotest.htm</a> </p> Clients: Lustre-1.8.6<br/> Server: Lustre 2.1.1 LU-1478

1.8.6.81 client with 2.1.1 server MPIIO file locking issue

Bug Minor Resolved Cannot Reproduce Zhenyu Xu Mahmoud Hanafi Tue, 5 Jun 2012 12:13:16 +0000 Thu, 14 Nov 2013 20:59:17 +0000 Thu, 14 Nov 2013 20:59:17 +0000 Lustre 2.1.1 Lustre 1.8.6 0 4 <p>Bobijam</p> <p>Could you please look into this one?</p> <p>Thanks</p> <p>Peter</p> <p>from the log uploaded, the client is requesting to protected read flock (mode=4, PR SETFLK) on inode 144501415241318403, flags=0x40000(LDLM_FL_BLOCK_NOWAIT, SETFLK will return error if other process has protected the file with another flock)</p> <blockquote> <p>00000080:00010000:1:1338846492.143361:0:76798:0:(file.c:3260:ll_file_flock()) inode=144501415241318403, pid=76798, flags=0x40000, mode=4, start=0, end=1048575 </p></blockquote> <p>and other process already flock protected the file, so that later requesting client failed. It's a normal operation.</p> <p>Oleg, does this relates to <a href="https://jira.whamcloud.com/browse/LU-104" title="Lustre grants flock exclusive locks on two file descriptors for the same file" class="issue-link" data-issue-key="LU-104"><del>LU-104</del></a>? Its comment said that the <a href="https://jira.whamcloud.com/browse/LU-104" title="Lustre grants flock exclusive locks on two file descriptors for the same file" class="issue-link" data-issue-key="LU-104"><del>LU-104</del></a> patch has already landed on 1.8, but I didn't find that code in b1_8 branch.</p> <p>We can close this one</p> <p>ok - thanks Mahmoud</p> Development Rank 1|hzvken: Rank (Obsolete) 7035 Severity