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-15015 Lustre <p>This issue was created by maloo for S Buisson &lt;sbuisson@ddn.com&gt;</p> <p>This issue relates to the following test suite run: <a href="https://testing.whamcloud.com/test_sets/de86ad94-a713-4683-84d0-368a514164fa" class="external-link" target="_blank" rel="nofollow noopener">https://testing.whamcloud.com/test_sets/de86ad94-a713-4683-84d0-368a514164fa</a></p> <p>test_13c failed with the following error:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>Timeout occurred after 123 mins, last suite running was sanity-pcc </pre> </div></div> <p>Time out occurred after MDT0 was unmounted.</p> <p>VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV<br/> sanity-pcc test_13c - Timeout occurred after 123 mins, last suite running was sanity-pcc</p> LU-15015

test timeout with "tee" hung in nfs_updatepage()

Bug Minor Open Unresolved WC Triage Maloo Fri, 17 Sep 2021 15:19:54 +0000 Thu, 16 Dec 2021 11:27:29 +0000 0 4 <p>In the client1 console log, I see tee/NFS hung</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>[ 4178.294408] INFO: task tee:104241 blocked for more than 120 seconds. [ 4178.295637] Tainted: G OE --------- - - 4.18.0-240.22.1.el8_3.x86_64 #1 [ 4178.297034] "echo 0 &gt; /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 4178.298287] tee D 0 104241 28015 0x00000080 [ 4178.299201] Call Trace: [ 4178.299655] __schedule+0x2c4/0x700 [ 4178.301745] schedule+0x38/0xa0 [ 4178.302291] io_schedule+0x12/0x40 [ 4178.302879] bit_wait_io+0xd/0x50 [ 4178.303464] __wait_on_bit+0x6c/0x80 [ 4178.304068] out_of_line_wait_on_bit+0x91/0xb0 [ 4178.305557] nfs_lock_and_join_requests+0x3d8/0x530 [nfs] [ 4178.307685] nfs_updatepage+0x2d8/0x950 [nfs] [ 4178.308430] nfs_write_end+0x63/0x4d0 [nfs] [ 4178.310016] generic_perform_write+0x138/0x1b0 [ 4178.310778] nfs_file_write+0xf6/0x270 [nfs] [ 4178.311511] new_sync_write+0x124/0x170 [ 4178.312160] vfs_write+0xa5/0x1a0 [ 4178.312742] ksys_write+0x4f/0xb0 [ 4178.313315] do_syscall_64+0x5b/0x1a0 [ 4178.313944] entry_SYSCALL_64_after_hwframe+0x65/0xca [ 4178.314788] RIP: 0033:0x7f4d1f5cd8a8 [ 4178.315417] Code: Bad RIP value. </pre> </div></div> <p>I've faced the same hung, but on sanity test_27v - <a href="https://testing.whamcloud.com/test_sets/0ef31cd1-1dfc-4480-8ad0-d682184bd91f" class="external-link" target="_blank" rel="nofollow noopener">https://testing.whamcloud.com/test_sets/0ef31cd1-1dfc-4480-8ad0-d682184bd91f</a></p> <p>Probably, it is better to change the name of the ticket to smth like: TIMEOUT due to hung in nfs(nfs_updatepage).</p> <p>the same at conf-sanity test_28a: - <a href="https://testing.whamcloud.com/test_sets/872319dd-a037-49d8-8ed4-91356bf476e4" class="external-link" target="_blank" rel="nofollow noopener">https://testing.whamcloud.com/test_sets/872319dd-a037-49d8-8ed4-91356bf476e4</a></p> Related LU-14005 Development Rank 1|i024m7: Rank (Obsolete) 9223372036854775807 Severity