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-849 Lustre <p>When running parallel-scale test_iorfpp over NFS v3 got "nfs server not responding" error</p> <p>Lustre: DEBUG MARKER: ----<del>============= acceptance-small: parallel-scale ============</del>---- Tue Nov 15 11:54:31 PST 2011<br/> Lustre: DEBUG MARKER: excepting tests: parallel_grouplock<br/> Lustre: DEBUG MARKER: == parallel-scale test compilebench: compilebench == 11:54:33 (1321386873)<br/> Lustre: DEBUG MARKER: ./compilebench -D /mnt/lustre/d0.compilebench -i 2 -r 2 --makej<br/> Lustre: DEBUG MARKER: == parallel-scale test metabench: metabench == 12:32:28 (1321389148)<br/> Lustre: DEBUG MARKER: == parallel-scale test simul: simul == 12:33:57 (1321389237)<br/> Lustre: DEBUG MARKER: SKIP: parallel-scale test_simul skipped for NFSCLIENT mode<br/> Lustre: DEBUG MARKER: == parallel-scale test mdtestssf: mdtestssf == 12:33:58 (1321389238)<br/> Lustre: DEBUG MARKER: SKIP: parallel-scale test_mdtestssf skipped for NFSCLIENT mode<br/> Lustre: DEBUG MARKER: == parallel-scale test mdtestfpp: mdtestfpp == 12:33:58 (1321389238)<br/> Lustre: DEBUG MARKER: SKIP: parallel-scale test_mdtestfpp skipped for NFSCLIENT mode<br/> Lustre: DEBUG MARKER: == parallel-scale test connectathon: connectathon == 12:33:59 (1321389239)<br/> Lustre: DEBUG MARKER: ./runtests -N 2 -b -f /mnt/lustre/d0.connectathon<br/> Lustre: DEBUG MARKER: ./runtests -N 2 -g -f /mnt/lustre/d0.connectathon<br/> Lustre: DEBUG MARKER: ./runtests -N 2 -s -f /mnt/lustre/d0.connectathon<br/> Lustre: DEBUG MARKER: ./runtests -N 2 -l -f /mnt/lustre/d0.connectathon<br/> Lustre: DEBUG MARKER: == parallel-scale test iorssf: iorssf == 12:35:05 (1321389305)<br/> Lustre: DEBUG MARKER: == parallel-scale test iorfpp: iorfpp == 12:37:56 (1321389476)<br/> nfs: server 10.10.4.15 not responding, still trying<br/> nfs: server 10.10.4.15 not responding, still trying</p> server and client: RHEL6-x86_64 build <a href="https://newbuild.whamcloud.com/job/lustre-master/353/">https://newbuild.whamcloud.com/job/lustre-master/353/</a> LU-849

NFS server not responding when running parallel-scale test_iorfpp

Bug Minor Resolved Duplicate Lai Siyao Sarah Liu Tue, 15 Nov 2011 17:17:27 +0000 Mon, 16 Jan 2012 15:26:54 +0000 Mon, 16 Jan 2012 15:26:54 +0000 0 4 <p>NFSv4 has this issue too.</p> <p>the attached are the logs from lustre client(NFS server)</p> <p>Lai</p> <p>Could you please comment on this one?</p> <p>Thanks</p> <p>Peter</p> <p>hm, several nfsd threads seems to be stuck in splice_read (somewhere in cl_page_list_disown() although it is not clear if the stack is reliable).<br/> Sarah, could you please rerun the test and collect lustre debug logs?</p> <p>sure, will keep you updated.</p> <p>debug log of lustre client(NFS server)</p> <p>ah, this is with the default debug mask. Could you please collect one with the debug mask set to -1? Thanks in advance.</p> <p>debug -1 log</p> <p>Lai, Jinshan, we need to look into this as this potentially underscores how recent clio changes introduced some deadlocks in sendfile path.</p> <p>nfsd uses splice read/write interface on new kernels, I tested some splice test (from LTP), and it could pass. I'll do more test later.</p> <p>In my local test, I found it's stack overflow too. I'll try to decrease stack size a bit and verify it.</p> <p><a href="http://jira.whamcloud.com/browse/LU-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=26225#comment-26225" class="external-link" rel="nofollow">http://jira.whamcloud.com/browse/LU-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=26225#comment-26225</a></p> <p>According to Jinshan's comment on <a href="https://jira.whamcloud.com/browse/LU-861" title="ASSERTION(!cfs_in_interrupt()) failed on MDS during compilebench over nfsv4" class="issue-link" data-issue-key="LU-861"><del>LU-861</del></a>, two fixes may help, this work will be continued after that.</p> <p>let's track this under lu-861 and then open a new ticket if the problems still exist with those fixes landed</p> Development Rank 1|hzvhqv: Rank (Obsolete) 6524 Severity