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-11948 Lustre <p>parallel-scale-nfsv4 test_connectathon fails with ''connectathon failed: 1'' . So far, we’ve only seen this issue once, a DNE with ZFS test session; <a href="https://testing.whamcloud.com/test_sets/a1fe9392-2b96-11e9-90fb-52540065bddc" class="external-link" target="_blank" rel="nofollow noopener">https://testing.whamcloud.com/test_sets/a1fe9392-2b96-11e9-90fb-52540065bddc</a> . Looking at the client test_log, we see a segmentation fault</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>Congratulations, you passed the basic tests! ... Pass 4 ... Starting BASIC tests: test directory /mnt/lustre/d0.parallel-scale-nfs/d0.connectathon (arg: -f) ./test1: File and directory creation test ./test1: (/opt/connectathon/basic) runtests: line 28: 8630 Segmentation fault ./test1 $TESTARG basic tests failed parallel-scale-nfsv4 test_connectathon: @@@@@@ FAIL: connectathon failed: 1 </pre> </div></div> <p>Looking at the MDS1, 3 (vm11) console log, we see the following errors</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>[124786.514802] Lustre: DEBUG MARKER: ./runtests -N 10 -l -f /mnt/lustre/d0.parallel-scale-nfs/d0.connectathon [124859.432032] LustreError: 28274:0:(file.c:3941:ll_file_flock()) unknown fcntl lock command: 1029 [124928.294500] LustreError: 28274:0:(file.c:3941:ll_file_flock()) unknown fcntl lock command: 1029 [125035.913851] LustreError: 28274:0:(file.c:3941:ll_file_flock()) unknown fcntl lock command: 1029 [125065.916330] LustreError: 28274:0:(file.c:3941:ll_file_flock()) unknown fcntl lock command: 1029 [125105.547691] LustreError: 28274:0:(file.c:3941:ll_file_flock()) unknown fcntl lock command: 1029 [125135.550497] LustreError: 28274:0:(file.c:3941:ll_file_flock()) unknown fcntl lock command: 1029 [125175.230096] LustreError: 28274:0:(file.c:3941:ll_file_flock()) unknown fcntl lock command: 1029 [125244.986669] LustreError: 28274:0:(file.c:3941:ll_file_flock()) unknown fcntl lock command: 1029 [125244.987704] LustreError: 28274:0:(file.c:3941:ll_file_flock()) Skipped 1 previous similar message [125251.814692] Lustre: DEBUG MARKER: lctl set_param -n fail_loc=0 fail_val=0 2&gt;/dev/null </pre> </div></div> DNE/ZFS LU-11948

parallel-scale-nfsv4 test connectathon fails ''connectathon failed: 1''

Bug Minor In Progress Unresolved Alex Deiter James Nunez Fri, 8 Feb 2019 18:34:37 +0000 Wed, 23 Nov 2022 10:10:18 +0000 Lustre 2.13.0 0 4 <p>Looking at the kernel code, it looks like <tt>1029</tt> is:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>#define FL_POSIX 1 #define FL_DELEG 4 /* NFSv4 delegation */ #define FL_OFDLCK 1024 /* lock is "owned" by struct file */ </pre> </div></div> <p><tt>FL_OFDLCK</tt> was "added" in <tt>v3.15-rc1-15-gcff2fce58b2b</tt>, but that is really just a rename of <tt>FL_FILE_PVT</tt> added in <tt>v3.14-rc1-10-gc918d42a27a9</tt>. This is a new type of lock that is attached to a process file struct rather than the file descriptor table (which may be shared between tasks). This avoids problems with file locks being accidentally dropped if a file descriptor is cloned due to fork/exec, and then the file is closed by the second process.</p> <p>Andriy, it looks like you have been working in this area most recently?</p> <p>We do still see the "unknown fcntl lock command: 1029" messages when running connectathon for parallel-scale-nfsv*, but it does not cause test connectathon to fail. </p> <p>One example is at <a href="https://testing.whamcloud.com/test_sets/bc5183ad-2cad-4b97-aba4-604b73b9765f" class="external-link" target="_blank" rel="nofollow noopener">https://testing.whamcloud.com/test_sets/bc5183ad-2cad-4b97-aba4-604b73b9765f</a> where the messages can be seen on the MDS console log. There are several other examples.</p> <p>It would be good to add support for the this type of lock, since I expect userspace servers like Samba and Ganesha are/will use this to avoid complexities in flock lock handling. </p> <p>However, I have no idea about how easy/hard it is to implement. Maybe just adding a flag to quiet the error message, or maybe a complete protocol change because the MDS needs different locking semantics. I'm not really sure, but I hope/suspect it is on the easier side. </p> Related LU-12230 Development Rank 1|i00bbr: Rank (Obsolete) 9223372036854775807 Severity