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-15333 Lustre <p>LFSCK test reports "XATTR trusted.fid: the parent FID is invalid" error in the current 2.15 run.</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>00100000:10000000:4.0:1637044175.473115:0:148585:0:(lfsck_namespace.c:264:lfsck_namespace_record_failure()) kjcf05-MDT0000-osd: namespace LFSCK hit first non-repaired inconsistency at the pos [2633473, [0x0:0x0:0x0], 0x0] 00100000:10000000:26.0:1637044377.319767:0:148587:0:(lfsck_layout.c:4153:lfsck_layout_check_parent()) kjcf05-MDT0000-osd:([0x20000ea75:0xee9:0x0]|[0x0:0x0:0x0])/[0x100010000:0x6fb6352:0x0]:XATTR trusted.fid: the parent FID is invalid </pre> </div></div> <p>Will upload lfsck logs to the FTP.</p> <p> </p> client cluster: Walleye-P5 <br/> 20 x Lustre 2.15 clients <br/> 4 X LNet routers <br/> Lustre client: 2.14.55_81_gc26b347 <br/> storage cluster: kjcf05 <br/> NEO build: 6.0-65-cm-21.10.24-g2c588a6 <br/> Lustre server: 2.14.55_81_gc26b347 <br/> Model SSUs: 1xE1000D 1xE1000F <br/> 4 x OSS nodes with 2 x HDD OSTs and 2 x flash OSTs LU-15333

lfsck reports "XATTR trusted.fid: the parent FID is invalid"

Bug Major Resolved Duplicate Alexander Zarochentsev Prasannakumar Nagasubramani Tue, 7 Dec 2021 13:39:26 +0000 Thu, 28 Jul 2022 22:57:18 +0000 Thu, 7 Jul 2022 16:38:59 +0000 Lustre 2.15.0 0 4 <p>LFSCK logs uploaded to FTP.</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> ftp&gt; put lfsck_gc26b347.tar.gz local: lfsck_gc26b347.tar.gz remote: lfsck_gc26b347.tar.gz 227 Entering Passive Mode (50,222,100,36,211,43). 150 Ok to send data. 226 Transfer complete. 1875396 bytes sent in 0.0423 secs (44349.23 Kbytes/sec) ftp&gt; pwd 257 <span class="code-quote">"/uploads/LU15333"</span> ftp&gt; </pre> </div></div> <p>Cory</p> <p>Is someone from your team investigating this reported issue?</p> <p>Peter</p> <p>Yes, Zam is investigating this issue. I believe it is fallout from <a href="https://jira.whamcloud.com/browse/LU-15404" title="kernel panic and filesystem corruption in setxattr due to journal transaction restart" class="issue-link" data-issue-key="LU-15404"><del>LU-15404</del></a> where LFSCK is finding the non-Lustre EA inodes, which lack FID linkage. Since LFSCK does the right thing and reports the issue (while leaving it up to e2fsck to solve), I think we should resolve it as not a bug. Zam, do you agree? Please correct me if I'm wrong.</p> <p>Looks like a dup of <a href="https://jira.whamcloud.com/browse/LU-15683" class="external-link" rel="nofollow">https://jira.whamcloud.com/browse/LU-15683</a>. Propose to close this one.</p> Duplicate LU-15683 Related LU-15404 Development Rank 1|i02bsv: Rank (Obsolete) 9223372036854775807 Severity