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-16966 Lustre <p>We have had multiple servers get dead lock with this stack trace.</p> <p>(attached longer console output)</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> Jul 15 05:46:28 nbp11-srv3 kernel: INFO: task ll_ost07_000:9230 blocked <span class="code-keyword">for</span> more than 120 seconds. Jul 15 05:46:28 nbp11-srv3 kernel: Tainted: G OE --------- - - 4.18.0-425.3.1.el8_lustre.x86_64 #1 Jul 15 05:46:28 nbp11-srv3 kernel: <span class="code-quote">"echo 0 &gt; /proc/sys/kernel/hung_task_timeout_secs"</span> disables <span class="code-keyword">this</span> message. Jul 15 05:46:28 nbp11-srv3 kernel: task:ll_ost07_000 state:D stack: 0 pid: 9230 ppid: 2 flags:0x80004080 Jul 15 05:46:28 nbp11-srv3 kernel: Call Trace: Jul 15 05:46:28 nbp11-srv3 kernel: __schedule+0x2d1/0x860 Jul 15 05:46:28 nbp11-srv3 kernel: schedule+0x35/0xa0 Jul 15 05:46:28 nbp11-srv3 kernel: wait_transaction_locked+0x89/0xd0 [jbd2] Jul 15 05:46:28 nbp11-srv3 kernel: ? finish_wait+0x80/0x80 Jul 15 05:46:28 nbp11-srv3 kernel: add_transaction_credits+0xd4/0x290 [jbd2] Jul 15 05:46:28 nbp11-srv3 kernel: ? ldiskfs_do_update_inode+0x604/0x800 [ldiskfs] Jul 15 05:46:28 nbp11-srv3 kernel: start_this_handle+0x10a/0x520 [jbd2] Jul 15 05:46:28 nbp11-srv3 kernel: ? osd_fallocate_preallocate.isra.38+0x275/0x760 [osd_ldiskfs] Jul 15 05:46:28 nbp11-srv3 kernel: ? ldiskfs_mark_iloc_dirty+0x32/0x90 [ldiskfs] Jul 15 05:46:28 nbp11-srv3 kernel: jbd2__journal_restart+0xb4/0x160 [jbd2] Jul 15 05:46:28 nbp11-srv3 kernel: osd_fallocate_preallocate.isra.38+0x5a6/0x760 [osd_ldiskfs] Jul 15 05:46:28 nbp11-srv3 kernel: osd_fallocate+0xfd/0x370 [osd_ldiskfs] Jul 15 05:46:28 nbp11-srv3 kernel: ofd_object_fallocate+0x5dd/0xa30 [ofd] Jul 15 05:46:28 nbp11-srv3 kernel: ofd_fallocate_hdl+0x467/0x730 [ofd] Jul 15 05:46:28 nbp11-srv3 kernel: tgt_request_handle+0xc97/0x1a40 [ptlrpc] Jul 15 05:46:28 nbp11-srv3 kernel: ? ptlrpc_nrs_req_get_nolock0+0xff/0x1f0 [ptlrpc] Jul 15 05:46:28 nbp11-srv3 kernel: ptlrpc_server_handle_request+0x323/0xbe0 [ptlrpc] Jul 15 05:46:28 nbp11-srv3 kernel: ptlrpc_main+0xc0f/0x1570 [ptlrpc] Jul 15 05:46:28 nbp11-srv3 kernel: ? ptlrpc_wait_event+0x590/0x590 [ptlrpc] Jul 15 05:46:28 nbp11-srv3 kernel: kthread+0x10a/0x120 Jul 15 05:46:28 nbp11-srv3 kernel: ? set_kthread_struct+0x50/0x50 Jul 15 05:46:28 nbp11-srv3 kernel: ret_from_fork+0x1f/0x40 </pre> </div></div> Lustre version: <br/> lustre-iokit-2.15.2-1nas_mofed496el8_lustre_20230111v1.x86_64 <br/> kmod-lustre-2.15.2-1nas_mofed496el8_lustre_20230111v1.x86_64 <br/> pcp-lustre-0.4.16-2.noarch <br/> lustre-devel-2.15.2-1nas_mofed496el8_lustre_20230111v1.x86_64 <br/> lustre-osd-ldiskfs-mount-2.15.2-1nas_mofed496el8_lustre_20230111v1.x86_64 <br/> lustre-2.15.2-1nas_mofed496el8_lustre_20230111v1.x86_64 <br/> lustre-tests-2.15.2-1nas_mofed496el8_lustre_20230111v1.x86_64 <br/> kmod-lustre-osd-ldiskfs-2.15.2-1nas_mofed496el8_lustre_20230111v1.x86_64 <br/> kmod-lustre-tests-2.15.2-1nas_mofed496el8_lustre_20230111v1.x86_64 <br/> <br/> kernel: 4.18.0-425.3.1.el8_lustre.x86_64 <br/> mofed: mlnx-ofa_kernel-4.9-mofed496.x86_64 LU-16966

ofd_object_fallocate dead lock?

Bug Critical Resolved Fixed Alex Zhuravlev Mahmoud Hanafi Sat, 15 Jul 2023 16:37:29 +0000 Fri, 17 Nov 2023 00:47:08 +0000 Mon, 16 Oct 2023 12:47:11 +0000 Lustre 2.15.2 Lustre 2.16.0 Lustre 2.15.4 0 7 <p>looks like a duplicate of <a href="https://jira.whamcloud.com/browse/LU-15800" title="Fallocate causes transaction deadlock" class="issue-link" data-issue-key="LU-15800"><del>LU-15800</del></a> </p> <p>Thanks Alex! </p> <p>Xing</p> <p>Can you please port the fox from <a href="https://jira.whamcloud.com/browse/LU-15800" title="Fallocate causes transaction deadlock" class="issue-link" data-issue-key="LU-15800"><del>LU-15800</del></a> to b2_15?</p> <p>Thanks</p> <p>Peter</p> <p>Yes, Peter, I'll today.</p> <p>We applied <a href="https://jira.whamcloud.com/browse/LU-15800" title="Fallocate causes transaction deadlock" class="issue-link" data-issue-key="LU-15800"><del>LU-15800</del></a> but we say a filesystem hang. Longer console logs attached to the case.<span class="nobr"><a href="https://jira.whamcloud.com/secure/attachment/49928/49928_nbp15.hang" title="nbp15.hang attached to LU-16966">nbp15.hang^{<img class="rendericon" src="https://jira.whamcloud.com/images/icons/link_attachment_7.gif" height="7" width="7" align="absmiddle" alt="" border="0"/>}</a></span></p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> Aug  2 23:09:33 nbp15-srv1 kernel: INFO: task ll_ost02_011:14622 blocked <span class="code-keyword">for</span> more than 120 seconds. Aug  2 23:09:33 nbp15-srv1 kernel:      Tainted: G           OE    --------- -  - 4.18.0-477.10.1.el8_lustre.x86_64 #1 Aug  2 23:09:33 nbp15-srv1 kernel: <span class="code-quote">"echo 0 &gt; /proc/sys/kernel/hung_task_timeout_secs"</span> disables <span class="code-keyword">this</span> message. Aug  2 23:09:33 nbp15-srv1 kernel: task:ll_ost02_011    state:D stack:    0 pid:14622 ppid:     2 flags:0x80004080 Aug  2 23:09:33 nbp15-srv1 kernel: Call Trace: Aug  2 23:09:33 nbp15-srv1 kernel: __schedule+0x2d1/0x870 Aug  2 23:09:33 nbp15-srv1 kernel: schedule+0x55/0xf0 Aug  2 23:09:33 nbp15-srv1 kernel: wait_transaction_locked+0x89/0xd0 [jbd2] Aug  2 23:09:33 nbp15-srv1 kernel: ? finish_wait+0x80/0x80 Aug  2 23:09:33 nbp15-srv1 kernel: add_transaction_credits+0xd4/0x290 [jbd2] Aug  2 23:09:33 nbp15-srv1 kernel: ? osd_declare_qid+0x398/0x4c0 [osd_ldiskfs] Aug  2 23:09:33 nbp15-srv1 kernel: start_this_handle+0x10a/0x520 [jbd2] Aug  2 23:09:33 nbp15-srv1 kernel: ? jbd2__journal_start+0x8f/0x1f0 [jbd2] Aug  2 23:09:33 nbp15-srv1 kernel: ? kmem_cache_alloc+0x13f/0x280 Aug  2 23:09:33 nbp15-srv1 kernel: jbd2__journal_start+0xee/0x1f0 [jbd2] Aug  2 23:09:33 nbp15-srv1 kernel: ? osd_trans_start+0x13b/0x500 [osd_ldiskfs] Aug  2 23:09:33 nbp15-srv1 kernel: __ldiskfs_journal_start_sb+0x6e/0x140 [ldiskfs] Aug  2 23:09:33 nbp15-srv1 kernel: osd_trans_start+0x13b/0x500 [osd_ldiskfs] Aug  2 23:09:33 nbp15-srv1 kernel: ofd_attr_set+0x546/0x1090 [ofd] Aug  2 23:09:33 nbp15-srv1 kernel: ofd_setattr_hdl+0x458/0x8e0 [ofd] Aug  2 23:09:33 nbp15-srv1 kernel: tgt_request_handle+0xccd/0x1b10 [ptlrpc] Aug  2 23:09:33 nbp15-srv1 kernel: ? ptlrpc_nrs_req_get_nolock0+0xff/0x1f0 [ptlrpc] Aug  2 23:09:33 nbp15-srv1 kernel: ptlrpc_server_handle_request+0x323/0xbe0 [ptlrpc] Aug  2 23:09:33 nbp15-srv1 kernel: ptlrpc_main+0xc0f/0x1570 [ptlrpc] Aug  2 23:09:33 nbp15-srv1 kernel: ? ptlrpc_wait_event+0x590/0x590 [ptlrpc] Aug  2 23:09:33 nbp15-srv1 kernel: kthread+0x134/0x150 Aug  2 23:09:33 nbp15-srv1 kernel: ? set_kthread_struct+0x50/0x50 Aug  2 23:09:33 nbp15-srv1 kernel: ret_from_fork+0x1f/0x40 Aug  2 23:09:33 nbp15-srv1 kernel: INFO: task ll_ost03_006:14631 blocked <span class="code-keyword">for</span> more than 120 seconds. Aug  2 23:09:33 nbp15-srv1 kernel:      Tainted: G           OE    --------- -  - 4.18.0-477.10.1.el8_lustre.x86_64 #1 Aug  2 23:09:33 nbp15-srv1 kernel: <span class="code-quote">"echo 0 &gt; /proc/sys/kernel/hung_task_timeout_secs"</span> disables <span class="code-keyword">this</span> message. Aug  2 23:09:33 nbp15-srv1 kernel: task:ll_ost03_006    state:D stack:    0 pid:14631 ppid:     2 flags:0x80004080 Aug  2 23:09:33 nbp15-srv1 kernel: Call Trace: Aug  2 23:09:33 nbp15-srv1 kernel: __schedule+0x2d1/0x870 Aug  2 23:09:33 nbp15-srv1 kernel: schedule+0x55/0xf0 Aug  2 23:09:33 nbp15-srv1 kernel: wait_transaction_locked+0x89/0xd0 [jbd2] Aug  2 23:09:33 nbp15-srv1 kernel: ? finish_wait+0x80/0x80 Aug  2 23:09:33 nbp15-srv1 kernel: add_transaction_credits+0xd4/0x290 [jbd2] Aug  2 23:09:33 nbp15-srv1 kernel: ? ldiskfs_do_update_inode+0x604/0x800 [ldiskfs] Aug  2 23:09:33 nbp15-srv1 kernel: start_this_handle+0x10a/0x520 [jbd2] Aug  2 23:09:33 nbp15-srv1 kernel: ? osd_fallocate_preallocate.isra.37+0x275/0x760 [osd_ldiskfs] Aug  2 23:09:33 nbp15-srv1 kernel: ? ldiskfs_mark_iloc_dirty+0x32/0x90 [ldiskfs] Aug  2 23:09:33 nbp15-srv1 kernel: jbd2__journal_restart+0xb4/0x160 [jbd2] Aug  2 23:09:33 nbp15-srv1 kernel: osd_fallocate_preallocate.isra.37+0x5a6/0x760 [osd_ldiskfs] Aug  2 23:09:33 nbp15-srv1 kernel: osd_fallocate+0xfd/0x370 [osd_ldiskfs] Aug  2 23:09:33 nbp15-srv1 kernel: ofd_object_fallocate+0x5dc/0xa30 [ofd] Aug  2 23:09:33 nbp15-srv1 kernel: ofd_fallocate_hdl+0x467/0x730 [ofd] Aug  2 23:09:33 nbp15-srv1 kernel: tgt_request_handle+0xccd/0x1b10 [ptlrpc] Aug  2 23:09:33 nbp15-srv1 kernel: ? ptlrpc_nrs_req_get_nolock0+0xff/0x1f0 [ptlrpc] Aug  2 23:09:33 nbp15-srv1 kernel: ptlrpc_server_handle_request+0x323/0xbe0 [ptlrpc] Aug  2 23:09:33 nbp15-srv1 kernel: ptlrpc_main+0xc0f/0x1570 [ptlrpc] Aug  2 23:09:33 nbp15-srv1 kernel: ? ptlrpc_wait_event+0x590/0x590 [ptlrpc] Aug  2 23:09:33 nbp15-srv1 kernel: kthread+0x134/0x150 Aug  2 23:09:33 nbp15-srv1 kernel: ? set_kthread_struct+0x50/0x50 Aug  2 23:09:33 nbp15-srv1 kernel: ret_from_fork+0x1f/0x40 </pre> </div></div> <p>This looks more like <a href="https://jira.whamcloud.com/browse/LU-16691" title="optimize ldiskfs prealloc (PA) under random read workloads" class="issue-link" data-issue-key="LU-16691"><del>LU-16691</del></a></p> <p> </p> <p>Filesystem hung again. attaching stack output.</p> <p><span class="nobr"><a href="https://jira.whamcloud.com/secure/attachment/49934/49934_stack.out" title="stack.out attached to LU-16966">stack.out^{<img class="rendericon" src="https://jira.whamcloud.com/images/icons/link_attachment_7.gif" height="7" width="7" align="absmiddle" alt="" border="0"/>}</a></span></p> <p> </p> <p> </p> <blockquote><p>Filesystem hung again. attaching stack output.</p></blockquote> <p>thanks, need some time to analyze the traces.</p> <blockquote><p>We applied <a href="https://jira.whamcloud.com/browse/LU-15800" title="Fallocate causes transaction deadlock" class="issue-link" data-issue-key="LU-15800"><del>LU-15800</del></a> but we say a filesystem hang. Longer console logs attached to the case.nbp15.hang</p></blockquote> <p>I noticed OOM:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> Aug 2 20:55:33 nbp15-srv1 kernel: mdt_rdpg02_001: page allocation failure: order:0, mode:0x40(__GFP_IO), nodemask=(<span class="code-keyword">null</span>),cpuset=/,mems_allowed=0 </pre> </div></div> <p>can you please show output for lctl get_param osd*.<b>OST</b>.brw_stats from that OST?</p> <p>could you please clarify what exact version you're running? the ticket says 2.15.2, but you also siad <a href="https://jira.whamcloud.com/browse/LU-15800" title="Fallocate causes transaction deadlock" class="issue-link" data-issue-key="LU-15800"><del>LU-15800</del></a> was added? anything else? I need to know exact state of the source.</p> <p>Alex</p> <p>I would expect that the answer will be the b2_15 branch from <a href="https://github.com/champios/lustre-nas" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/champios/lustre-nas</a></p> <p>Peter</p> <p>thanks Peter</p> <p>b2_15-nas is the only "15" one, right?</p> <p>Initially we were running wc 2.15.2. After we got the patch we were running 2.15.3 + <a href="https://jira.whamcloud.com/browse/LU-15800" title="Fallocate causes transaction deadlock" class="issue-link" data-issue-key="LU-15800"><del>LU-15800</del></a> (2.15.3-2nas) </p> <p><a href="https://github.com/champios/lustre-nas" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/champios/lustre-nas</a>)</p> <p>btw_stats attached.</p> <p><span class="nobr"><a href="https://jira.whamcloud.com/secure/attachment/49955/49955_brw_stats" title="brw_stats attached to LU-16966">brw_stats^{<img class="rendericon" src="https://jira.whamcloud.com/images/icons/link_attachment_7.gif" height="7" width="7" align="absmiddle" alt="" border="0"/>}</a></span></p> <p>looking at the code in that tree I noticed couple things:</p> <ul> <li><a href="https://jira.whamcloud.com/browse/LU-15117" title="ofd_read_lock vs transaction deadlock while allocating buffers " class="issue-link" data-issue-key="LU-15117"><del>LU-15117</del></a> is missing (not sure it's really related, but I saw few RPC timeouts and that could cause similar symptoms)</li> <li><a href="https://jira.whamcloud.com/browse/LU-15894" title="Range locking in ofd is no longer needed" class="issue-link" data-issue-key="LU-15894"><del>LU-15894</del></a> is not reverted (and I see one trace stuck at the range lock)</li> </ul> <blockquote><p>btw_stats attached</p></blockquote> <p>unfortunately, <a href="https://jira.whamcloud.com/browse/LU-15564" title="allocation stats in osd-ldiskfs" class="issue-link" data-issue-key="LU-15564"><del>LU-15564</del></a> has not been landed yet in that tree. that could help to understand whether it's block allocation related or not.</p> <p>Is there some additional debugging we can do to help with this issue.</p> <blockquote><p>Is there some additional debugging we can do to help with this issue.</p></blockquote> <p>would it be possible to apply <a href="https://jira.whamcloud.com/browse/LU-15564" title="allocation stats in osd-ldiskfs" class="issue-link" data-issue-key="LU-15564"><del>LU-15564</del></a> so we can track allocation time?</p> <p>We are going to do a build with <a href="https://jira.whamcloud.com/browse/LU-15564" title="allocation stats in osd-ldiskfs" class="issue-link" data-issue-key="LU-15564"><del>LU-15564</del></a>. Should we also pick up <a href="https://jira.whamcloud.com/browse/LU-15117" title="ofd_read_lock vs transaction deadlock while allocating buffers " class="issue-link" data-issue-key="LU-15117"><del>LU-15117</del></a> and revert <a href="https://jira.whamcloud.com/browse/LU-15894" title="Range locking in ofd is no longer needed" class="issue-link" data-issue-key="LU-15894"><del>LU-15894</del></a>?</p> <p>We would need a backport for <a href="https://jira.whamcloud.com/browse/LU-15117" title="ofd_read_lock vs transaction deadlock while allocating buffers " class="issue-link" data-issue-key="LU-15117"><del>LU-15117</del></a>.</p> <p>Still waiting for answer to above question.</p> <p>Hi <a href="https://jira.whamcloud.com/secure/ViewProfile.jspa?name=mhanafi" class="user-hover" rel="mhanafi">mhanafi</a><br/> Sorry for the delay, you can try <a href="https://jira.whamcloud.com/browse/LU-15117" title="ofd_read_lock vs transaction deadlock while allocating buffers " class="issue-link" data-issue-key="LU-15117"><del>LU-15117</del></a> (there is a port already for b2_15). Likely <a href="https://jira.whamcloud.com/browse/LU-15894" title="Range locking in ofd is no longer needed" class="issue-link" data-issue-key="LU-15894"><del>LU-15894</del></a> may help but there is no port available, the patch <a href="https://jira.whamcloud.com/secure/ViewProfile.jspa?name=bzzz" class="user-hover" rel="bzzz">bzzz</a> is asking for you to try will provide additional statistics to help better understand the problem. I would suggest that you first start there, provide the requested statistics and allow us to better understand the problem before attempting other patches.</p> <p>We were able to get some of our servers patched with <a href="https://jira.whamcloud.com/browse/LU-15564" title="allocation stats in osd-ldiskfs" class="issue-link" data-issue-key="LU-15564"><del>LU-15564</del></a> and got brw_stats after a hang, see below. btw, if we set debug=+trace it reduce the chance of hitting this bug. </p> <p><span class="nobr"><a href="https://jira.whamcloud.com/secure/attachment/50170/50170_brw_stats.save.1693236421" title="brw_stats.save.1693236421 attached to LU-16966">brw_stats.save.1693236421^{<img class="rendericon" src="https://jira.whamcloud.com/images/icons/link_attachment_7.gif" height="7" width="7" align="absmiddle" alt="" border="0"/>}</a></span></p> <p><span class="nobr"><a href="https://jira.whamcloud.com/secure/attachment/50171/50171_stack1.out" title="stack1.out attached to LU-16966">stack1.out^{<img class="rendericon" src="https://jira.whamcloud.com/images/icons/link_attachment_7.gif" height="7" width="7" align="absmiddle" alt="" border="0"/>}</a></span></p> <p> </p> <p>Can we get an update please. We have filesystem hanging multiple times a day.</p> <blockquote><p>Can we get an update please. We have filesystem hanging multiple times a day.</p></blockquote> <p><a href="https://jira.whamcloud.com/secure/ViewProfile.jspa?name=mhanafi" class="user-hover" rel="mhanafi">mhanafi</a>sorry for the delay, I'm trying to reconstruct the problem using brw_stats you provided.</p> <p><a href="https://jira.whamcloud.com/secure/ViewProfile.jspa?name=mhanafi" class="user-hover" rel="mhanafi">mhanafi</a> could you please apply the patch just added? the patch reverts range locking.</p> <p>Thanks we'll get the patch applied this week and let you know the results.</p> <p><a href="https://jira.whamcloud.com/secure/ViewProfile.jspa?name=mhanafi" class="user-hover" rel="mhanafi">mhanafi</a> I'm very very sorry, but ... <img class="emoticon" src="https://jira.whamcloud.com/images/icons/emoticons/smile.png" height="16" width="16" align="absmiddle" alt="" border="0"/> could you please instead apply the patch I'm attaching. I've gone through few code paths and now think there is another problem with fallocate and actually we better reuse range locking you still have in your tree to fix the problem.<br/> the path is fallocate-range-locking.patch</p> <p>"Alex Zhuravlev &lt;bzzz@whamcloud.com&gt;" uploaded a new patch: <a href="https://review.whamcloud.com/c/fs/lustre-release/+/52264" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/c/fs/lustre-release/+/52264</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-16966" title="ofd_object_fallocate dead lock?" class="issue-link" data-issue-key="LU-16966"><del>LU-16966</del></a> osd: take trunc_lock for fallocate<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 48a6d52640fe716760d1a369f4bc53ebdba25e6d</p> <p>We applied the patch provided and we have not seeing the issue.</p> <p>"Oleg Drokin &lt;green@whamcloud.com&gt;" merged in patch <a href="https://review.whamcloud.com/c/fs/lustre-release/+/52264/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/c/fs/lustre-release/+/52264/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-16966" title="ofd_object_fallocate dead lock?" class="issue-link" data-issue-key="LU-16966"><del>LU-16966</del></a> osd: take trunc_lock for fallocate<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: 51529fb57f85210e292a15c882cf25a4689ea77d</p> <p>Landed for 2.16</p> <blockquote><p>Does this issue also affect b_es6_0 and b2_15?</p></blockquote> <p>yes, b_es6_0 needs that for sure, will check b2_15</p> <p>"Alex Zhuravlev &lt;bzzz@whamcloud.com&gt;" uploaded a new patch: <a href="https://review.whamcloud.com/c/fs/lustre-release/+/52710" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/c/fs/lustre-release/+/52710</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-16966" title="ofd_object_fallocate dead lock?" class="issue-link" data-issue-key="LU-16966"><del>LU-16966</del></a> osd: take trunc_lock for fallocate<br/> Project: fs/lustre-release<br/> Branch: b2_15<br/> Current Patch Set: 1<br/> Commit: d6e549e9ea2eb6e7b141203dad0130cc8da5f1db</p> <p>"Oleg Drokin &lt;green@whamcloud.com&gt;" merged in patch <a href="https://review.whamcloud.com/c/fs/lustre-release/+/52710/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/c/fs/lustre-release/+/52710/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-16966" title="ofd_object_fallocate dead lock?" class="issue-link" data-issue-key="LU-16966"><del>LU-16966</del></a> osd: take trunc_lock for fallocate<br/> Project: fs/lustre-release<br/> Branch: b2_15<br/> Current Patch Set: <br/> Commit: 9c97d1969e2298fdfe5daa616e36cbe17a9b3d5e</p> <p>Will be included in 2.15.4</p> Duplicate LU-15800 Development Rank 1|i03qm7: Rank (Obsolete) 9223372036854775807 Severity