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-1580 Lustre <p>This issue was created by maloo for Chris Gearing &lt;chris@whamcloud.com&gt;</p> <p>This issue relates to the following test suite run: <a href="https://maloo.whamcloud.com/test_sets/e8bc176e-c0a4-11e1-a5ca-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/e8bc176e-c0a4-11e1-a5ca-52540035b04c</a>.</p> <p>The sub-test test_1 failed with the following error:</p> <blockquote> <p>Run POSIX testsuite on /mnt/lustre failed</p></blockquote> <p>Info required for matching: posix 1</p> LU-1580

POSIX: pathconf.32: pathconf("/dev/pts/0", _PC_NAME_MAX) did not give correct results

Bug Blocker Resolved Fixed Jian Yu Maloo Thu, 28 Jun 2012 11:07:31 +0000 Thu, 27 Sep 2012 18:22:50 +0000 Wed, 8 Aug 2012 19:47:21 +0000 Lustre 2.3.0 0 5 <p>another failure: <a href="https://maloo.whamcloud.com/test_sets/aeb9eac8-c57c-11e1-ab7d-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/aeb9eac8-c57c-11e1-ab7d-52540035b04c</a><br/> From the test report there are 4 failed tests, 3 of them are known issues listed in <a href="https://jira.whamcloud.com/browse/LU-380" title="POSIX: write.15: time stamps incorrect: mtime, ctime were not updated" class="issue-link" data-issue-key="LU-380"><del>LU-380</del></a> and <a href="https://jira.whamcloud.com/browse/LU-379" title="POSIX: read.13 and readdir.6: time stamps incorrect: atime was not updated" class="issue-link" data-issue-key="LU-379"><del>LU-379</del></a> while the pathconf.32 is a new one.</p> <p>14:21:04:Test Name: pathconf.32 Failed<br/> 14:21:04:<br/> 14:21:04: Test Description:<br/> 14:21:04:When path does not refer to a directory, then a call to pathconf(path,<br/> 14:21:04:_PC_NAME_MAX) either returns a value of -1 and sets errno to <span class="error">&#91;EINVAL&#93;</span>,<br/> 14:21:04:or returns a valid value for </p> {NAME_MAX} <p>.<br/> 14:21:04:Posix Ref: Component PATHCONF Assertion 5.7.1.4-52(A)<br/> 14:21:04:<br/> 14:21:04: Test Strategy:<br/> 14:21:04:FOR a regular file, a FIFO (when not testing XNFS) and a terminal file<br/> 14:21:04:(when not testing XNFS)<br/> 14:21:04: OBTAIN the system value associated with pathconf() and _PC_NAME_MAX<br/> 14:21:04: VERIFY that pathconf() returned successfully or pathconf() returned<br/> 14:21:04: -1 and errno was set to EINVAL<br/> 14:21:04:<br/> 14:21:04: Test Information:<br/> 14:21:04:pathconf("/dev/pts/0", _PC_NAME_MAX) did not give correct results<br/> 14:21:04:expected: return value == -1, errno == 22 (EINVAL)<br/> 14:21:04: OR: return value != -1<br/> 14:21:04:observed: return value == -1, errno == 2 (ENOENT)</p> <p>I'll try this manually to see if it makes a difference. This is not due to testsuite but posix detect some issue.</p> <p>I have reproduced this manually. This seems like Posix issue<br/> <a href="https://maloo.whamcloud.com/test_sets/2ed77eb4-d077-11e1-aa18-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/2ed77eb4-d077-11e1-aa18-52540035b04c</a></p> <p>Yu Jian,<br/> Can you please take a look at this one?</p> <p>Since Lustre never pass all the POSIX test cases. We need to check whether above failures are new ones or known issues.</p> <p>The unlink.6 and write.15 failures are <a href="https://jira.whamcloud.com/browse/LU-380" title="POSIX: write.15: time stamps incorrect: mtime, ctime were not updated" class="issue-link" data-issue-key="LU-380"><del>LU-380</del></a>. The readdir.6 failure is <a href="https://jira.whamcloud.com/browse/LU-379" title="POSIX: read.13 and readdir.6: time stamps incorrect: atime was not updated" class="issue-link" data-issue-key="LU-379"><del>LU-379</del></a>. This ticket is used to track pathconf.32 failure.</p> <p>I found that while formatting a partition/disk as ext4 filesystem and run POSIX test suite on it to generate baseline, the pathconf.32 test also failed. However, if a loop device is used to be formatted as ext4, the test passed. So, the issue is related to the baseline, not Lustre.</p> <p>This item needs to be added to the release notes.</p> <p>Actually, Yujian is working on a fix.</p> <p>I just verified again that the same failure also occurred on ext4 filesystem. After updating the LSB-VSX POSIX test suite to disable the terminal file test in pathconf.32, Lustre POSIX compliance testing passed on T.pathconf test set (baseline is ext4):</p> <p>Lustre branch: master<br/> Lustre build: <a href="http://build.whamcloud.com/job/lustre-master/766/" class="external-link" target="_blank" rel="nofollow noopener">http://build.whamcloud.com/job/lustre-master/766/</a><br/> <a href="https://maloo.whamcloud.com/test_sets/3df07240-e088-11e1-a388-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/3df07240-e088-11e1-a388-52540035b04c</a></p> <p>The change on LSB-VSX POSIX test suite has been pushed into the toolkit repository. Let's wait for a successful posix test run performed by autotest and then we can close this ticket as resolved.</p> <p>Yujian, you can verify by doing a yum install posix on any node. If the src include your change, then we are good. If not, please contact Joshua to sync the repo with yum</p> <blockquote><p>Yujian, you can verify by doing a yum install posix on any node. If the src include your change, then we are good. If not, please contact Joshua to sync the repo with yum</p></blockquote> <p>Thanks Minh for this info. I've verified this by provisioning Lustre 2.1.3 test nodes and run posix test on them, the posix-1.0-wc1 package contained the new changes and posix test passed:<br/> <a href="https://maloo.whamcloud.com/test_sessions/150c92c0-e158-11e1-9a39-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sessions/150c92c0-e158-11e1-9a39-52540035b04c</a> </p> Development Rank 1|hzvdl3: Rank (Obsolete) 5807 Severity