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-1112 Lustre <p>SUCCESS SUMMARY:</p> <p>News POSIX successes: 1</p> <p>Test Name Baseline Lustre Report<br/> read.15 Failed Succeeded</p> <p>FAILURE SUMMARY:</p> <p>POSIX failures: 9</p> <p>Test Name Baseline Lustre Report<br/> creat.10 Succeeded Failed<br/> creat.15 Succeeded Failed<br/> creat.7 Succeeded Failed<br/> open.14 Succeeded Failed<br/> open.15 Succeeded Failed<br/> unlink.6 Succeeded Failed<br/> utime.4 Succeeded Failed<br/> utime.9 Succeeded Failed<br/> write.15 Succeeded Failed</p> <p>For the failure of write.15 and unlink.6 please refer to <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></p> LU-1112

POSIX test failed in 2.1.55

Bug Blocker Resolved Duplicate Zhenyu Xu Sarah Liu Fri, 17 Feb 2012 00:18:26 +0000 Wed, 29 Feb 2012 08:27:03 +0000 Wed, 29 Feb 2012 08:27:03 +0000 Lustre 2.2.0 0 2 <p>Bobi</p> <p>Could you please look at this one</p> <p>Thanks</p> <p>Peter</p> <p>Is there any lustre logs?</p> <p>what is the LSB-VSX posix test suite version?</p> <p>And please also upload posix test result, so that we can see what specific test step fails.</p> <p>Hi, you can find the version and posix result in the attached file and there is no lustre log. </p> <p>Is the uploaded "posix" detailed posix test result? Sorry, would you collect lustre logs for another try? I still need lustre logs to analyse what problem it is.</p> <p>ok, will keep you updated.</p> <p>From the log file "posix" all errors are EPERM, I'm wondering that it's because user "vsx0" has no proper access right in /mnt/lustre/TESTROOT.</p> <p>If you re-hit the issue, would you mind trying "chown -R vsx0.vsxg0 /mnt/lustre/TESTSROOT" after /mnt/lutsre is mounted and run the test again?</p> <p>Hi,<br/> I found the permission of /mnt/lustre/TESTROOT is</p> <p><span class="error">&#91;root@client-15 tmp&#93;</span># ls -al /mnt/lustre/<br/> total 16<br/> drwxr-xr-x 4 root root 4096 Feb 22 13:13 .<br/> drwxr-xr-x. 4 root root 4096 Feb 22 12:25 ..<br/> drwxr-xr-x 2 root root 4096 Feb 22 13:05 .lustre<br/> drwxr-sr-x 5 vsx0 vsxg0 4096 Feb 22 13:14 TESTROOT</p> <p>I don't know why it will cause permission issue. And please find the lustre debug log in the attached.I also upload the whole result dir, hope that does help.</p> <p>results. Sorry the debug log is too big to be uploaded, you can find it in my home dir on brent /home/sarah/debug_log</p> <p><tt><div class="panel" style="border-width: 1px;"><div class="panelContent"> <p>00000080:00200000:1.0:1329945342.255336:0:7319:0:(namei.c:535:ll_lookup_it()) VFS Op:name=creat-t.10,dir=144115205255726268/33554436(ffff88023fca3828),intent=open|creat<br/> 00000080:00200000:1.0:1329945342.256257:0:7319:0:(namei.c:789:ll_create_it()) VFS Op:name=creat-t.10,dir=144115205255726268/33554436(ffff88023fca3828),intent=open|creat<br/> 00000080:00010000:1.0:1329945342.256279:0:7319:0:(namei.c:758:ll_create_node()) setting l_ast_data to inode ffff8802a3b3f768 (144115205255726326/33554436)<br/> 00000080:00010000:1.0:1329945342.256281:0:7319:0:(llite_internal.h:1431:ll_set_lock_data()) setting l_data to inode ffff8802a3b3f768 (144115205255726326/33554436)<br/> 00000080:00200000:1.0:1329945342.256284:0:7319:0:(file.c:513:ll_file_open()) VFS Op:inode=144115205255726326/33554436(ffff8802a3b3f768), flags 100101 <font color="blue">==&gt; O_LARGEFILE|O_CREAT|O_WRONLY</font><br/> 00000080:00200000:1.0:1329945342.256297:0:7319:0:(file.c:2509:ll_inode_permission()) VFS Op:inode=144115205255726326/33554436(ffff8802a3b3f768), inode mode 81ff mask 0<br/> 00000080:00200000:1.0:1329945342.257014:0:7319:0:(xattr.c:419:ll_getxattr()) VFS Op:inode=144115205255726326/33554436(ffff8802a3b3f768), xattr security.capability<br/> 00000080:00200000:1.0:1329945342.257016:0:7319:0:(xattr.c:284:ll_getxattr_common()) VFS Op:inode=144115205255726326/33554436(ffff8802a3b3f768)<br/> 00000080:00200000:1.0:1329945342.257106:0:7319:0:(file.c:297:ll_file_release()) VFS Op:inode=144115205255726326/33554436(ffff8802a3b3f768)</p> <p>00000080:00200000:3.0:1329945342.263165:0:7323:0:(namei.c:535:ll_lookup_it()) VFS Op:name=creat-t.10,dir=144115205255726268/33554436(ffff88023fca3828),intent=getattr<br/> 00000080:00010000:0.0:1329945342.263964:0:7323:0:(llite_internal.h:1431:ll_set_lock_data()) setting l_data to inode ffff8802a3b3f768 (144115205255726326/33554436)<br/> 00000080:00010000:0.0:1329945342.263967:0:7323:0:(dcache.c:376:ll_lookup_finish_locks()) setting l_data to inode ffff8802a3b3f768 (144115205255726326/33554436)<br/> 00000080:00200000:0.0:1329945342.263986:0:7323:0:(file.c:2252:__ll_inode_revalidate_it()) VFS Op:inode=144115205255726326/33554436(ffff8802a3b3f768),name=creat-t.10<br/> 00000080:00010000:0.0:1329945342.264004:0:7323:0:(dcache.c:376:ll_lookup_finish_locks()) setting l_data to inode ffff8802a3b3f768 (144115205255726326/33554436)<br/> 00000080:00010000:0.0:1329945342.264006:0:7323:0:(llite_internal.h:1431:ll_set_lock_data()) setting l_data to inode ffff8802a3b3f768 (144115205255726326/33554436)<br/> 00000080:00200000:0.0:1329945342.264415:0:7323:0:(dcache.c:410:ll_revalidate_it()) VFS Op:name=creat-t.10,intent=open|creat<br/> 00000080:00010000:1.0:1329945342.265200:0:7323:0:(llite_internal.h:1431:ll_set_lock_data()) setting l_data to inode ffff8802a3b3f768 (144115205255726326/33554436)<br/> 00000080:00200000:1.0:1329945342.265204:0:7323:0:(file.c:513:ll_file_open()) VFS Op:inode=144115205255726326/33554436(ffff8802a3b3f768), flags 101101 <font color="blue">==&gt;O_LARGEFILE|O_TRUNC|O_CREAT|O_WRONLY</font><br/> 00000080:00200000:1.0:1329945342.265224:0:7323:0:(file.c:2509:ll_inode_permission()) VFS Op:inode=144115205255726326/33554436(ffff8802a3b3f768), inode mode 81ff mask 42 <font color="blue">==&gt;mode:S_IFREG|S_IRWXU|S_IRWXG|S_IRWXO ==&gt;mask:MAY_CHDIR|MAY_WRITE</font><br/> 00000080:00200000:1.0:1329945342.265229:0:7323:0:(llite_lib.c:1329:ll_setattr_raw()) VFS Op:inode=144115205255726326 valid a068<br/> 00000080:00200000:1.0:1329945342.265794:0:7323:0:(file.c:297:ll_file_release()) VFS Op:inode=144115205255726326/33554436(ffff8802a3b3f768)<br/> 00000080:00200000:0.0:1329945342.272682:0:7319:0:(namei.c:535:ll_lookup_it()) VFS Op:name=creat-t.10,dir=144115205255726268/33554436(ffff88023fca3828),intent=getattr<br/> 00000080:00010000:1.0:1329945342.273533:0:7319:0:(llite_internal.h:1431:ll_set_lock_data()) setting l_data to inode ffff8802a3b3f768 (144115205255726326/33554436)<br/> 00000080:00010000:1.0:1329945342.273536:0:7319:0:(dcache.c:376:ll_lookup_finish_locks()) setting l_data to inode ffff8802a3b3f768 (144115205255726326/33554436)<br/> 00000080:00200000:1.0:1329945342.273556:0:7319:0:(namei.c:1135:ll_unlink_generic()) VFS Op:name=creat-t.10,dir=144115205255726268/33554436(ffff88023fca3828)<br/> 00000080:00200000:1.0:1329945342.274565:0:7319:0:(llite_lib.c:1130:ll_clear_inode()) VFS Op:inode=144115205255726326/33554436(ffff8802a3b3f768)<br/> 00000080:00200000:3.0:1329945383.166170:0:7319:0:(namei.c:535:ll_lookup_it()) VFS Op:name=creat-t.10,dir=144115205255726268/33554436(ffff88023fca3828),intent=getattr</p> </div></div></tt></p> <p>from the log (in creatt.10 case), the permission check is ok, also inode_permission() will not return -EPERM, but suspicious code lies in may_open()</p> <div class="code panel" style="border-width: 1px;"><div class="codeHeader panelHeader" style="border-bottom-width: 1px;"><b>excerpt from may_open()</b></div><div class="codeContent panelContent"> <pre class="code-java"> error = inode_permission(inode, acc_mode); <span class="code-keyword">if</span> (error) <span class="code-keyword">return</span> error; /* * An append-only file must be opened in append mode <span class="code-keyword">for</span> writing. */ <span class="code-keyword">if</span> (IS_APPEND(inode)) { <span class="code-keyword">if</span> ((flag &amp; O_ACCMODE) != O_RDONLY &amp;&amp; !(flag &amp; O_APPEND)) <span class="code-keyword">return</span> -EPERM; <span class="code-keyword">if</span> (flag &amp; O_TRUNC) <span class="code-keyword">return</span> -EPERM; } <span class="code-comment">/* O_NOATIME can only be set by the owner or superuser */</span> <span class="code-keyword">if</span> (flag &amp; O_NOATIME &amp;&amp; !inode_owner_or_capable(inode)) <span class="code-keyword">return</span> -EPERM; </pre> </div></div> <p>The second ll_file_open() call has O_TRUNC flag, I suspect that the inode was set S_APPEND flag.</p> <p>my local vm test does not have this issue. </p> <p>Hi Sarah and Bobi,</p> <p>FYI...</p> <p>Lustre Branch: master<br/> Lustre Build: <a href="http://build.whamcloud.com/job/lustre-master/491/" class="external-link" target="_blank" rel="nofollow noopener">http://build.whamcloud.com/job/lustre-master/491/</a><br/> Distro/Arch: RHEL6/x86_64 (kernel version: 2.6.32_220.4.2.el6)<br/> Network: IB (in-kernel OFED)</p> <p>I ran the same POSIX compliance test but did not hit the issues in this ticket (except unlink.6 and write.15 which is issue <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>). Here is the summary:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>FAILURE SUMMARY: POSIX failures: 2 Test Name Baseline Lustre Report unlink.6 Succeeded Failed write.15 Succeeded Failed </pre> </div></div> <p>Maloo report: <a href="https://maloo.whamcloud.com/test_sets/4c324da6-61d5-11e1-b462-5254004bbbd3" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/4c324da6-61d5-11e1-b462-5254004bbbd3</a></p> <p>I ran POSIX on the same build and distro as Yu Jian(build 491-RHEL6-x86_64) and got 3 failures, two of them are mentioned 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 another one is readdir.6 which is shown in <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>. </p> <p>FAILURE SUMMARY:</p> <p>POSIX failures: 3</p> <p>Test Name Baseline Lustre Report<br/> readdir.6 Succeeded Failed<br/> unlink.6 Succeeded Failed<br/> write.15 Succeeded Failed</p> <p>Thanks everyone. So we can close this ticket as a duplicate of <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> and <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></p> Development Rank 1|hzvhb3: Rank (Obsolete) 6453 Severity