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-4742 Lustre <p>I have been seeing this a few times recently. It doesn't seem to be particularly critical but I don't think this file exists on the filesystem.</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>Mar 10 10:29:37 cmds1 kernel: Lustre: 35876:0:(mdd_device.c:563:obf_lookup()) charlie-MDD0000: bad FID format [.fungus_skip], should be [0x200000400:0x1:0x0] Mar 10 10:38:03 cmds1 kernel: Lustre: 35876:0:(mdd_device.c:563:obf_lookup()) charlie-MDD0000: bad FID format [.fungus_skip], should be [0x200000400:0x1:0x0] Mar 10 10:49:20 cmds1 kernel: Lustre: 5100:0:(mdd_device.c:563:obf_lookup()) charlie-MDD0000: bad FID format [.fungus_skip], should be [0x200000400:0x1:0x0] Mar 10 10:59:45 cmds1 kernel: Lustre: 35652:0:(mdd_device.c:563:obf_lookup()) charlie-MDD0000: bad FID format [.fungus_skip], should be [0x200000400:0x1:0x0] Mar 10 11:09:45 cmds1 kernel: Lustre: 35652:0:(mdd_device.c:563:obf_lookup()) charlie-MDD0000: bad FID format [.fungus_skip], should be [0x200000400:0x1:0x0] Mar 10 11:21:01 cmds1 kernel: Lustre: 5100:0:(mdd_device.c:563:obf_lookup()) charlie-MDD0000: bad FID format [.fungus_skip], should be [0x200000400:0x1:0x0] </pre> </div></div> <p>The ".fungus_skip" file is just a blank file that our filesystem trawler tries to write to dirs we know we don't need to scan (OLD/ARCHIVE etc). We do not see this message on a similar (same version) filesystem. The only thing that I think may have happened to this filesystem is that the mds-survey benchmark was aborted halfway through and left some "test" dirs that had to be manually deleted by mounting with ldiskfs. I'm not sure if this has messed up the FIDs.</p> LU-4742

bad FID format - should be [0x200000400:0x1:0x0]

Bug Minor Resolved Fixed Niu Yawei Daire Byrne Mon, 10 Mar 2014 12:50:26 +0000 Fri, 18 Apr 2014 13:14:03 +0000 Fri, 18 Apr 2014 13:14:03 +0000 Lustre 2.4.1 Lustre 2.6.0 Lustre 2.6.0 0 4 <p>Niu</p> <p>Could you please advise on this one?</p> <p>Thanks</p> <p>Peter</p> <p>Did you accidently create .fungus_skip in the .lustre directory (.lustre/fid/) when you mount the mds with ldiskfs?</p> <p>Well no, I don't see how I could have done that. I can remount ldiskfs and remove the file if that helps. Like I said the file is not important.</p> <p>I think it is your crawler trying to create this file in the .lustre/fid directory that is causing this error. You should exclude this directory from your crawling. </p> <p>The main question is whether this error message is useful at all? It could be improved to indicate this is caused by opening files in <tt>.lustre/fid/</tt>, or just removed entirely.</p> <blockquote> <p>The main question is whether this error message is useful at all? It could be improved to indicate this is caused by opening files in .lustre/fid/, or just removed entirely.</p></blockquote> <p>Giving a warnning to inform user what's wrong could be better than return error silently, maybe we just need to re-stating the message to indicate that's just a lookup in .lustre/fid/.</p> <p>improved warning message: <a href="http://review.whamcloud.com/9594" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/9594</a></p> <p>Okay it looks like our trawler was trying to scan .lustre (over NFS). We have excluded it now and predictably the (confusing!) error message has disappeared. Cheers! </p> <p>Landed for 2.6</p> Development Rank 1|hzwh8f: Rank (Obsolete) 13035 Severity