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-3314 Lustre <p>For lustre-2.x (x &lt;= 3), the ".lustre" object has NO FID-in-LMA, so the client will get IGIF for the ".lustre" object when the MDT restart. From the OI scrub view, when the MDT upgrade to Lustre-2.4, it does not know whether there are some alive clients have cached ".lustre" IGIF during the upgrading, so it has to generate IGIF-in-LMA and IGIF-in-OI for ".lustre" object. It will cause the others on the MDT failed to check "fid_is_dot_lustre()".</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"><span class="code-keyword">static</span> inline <span class="code-object">int</span> fid_is_dot_lustre(<span class="code-keyword">const</span> struct lu_fid *fid) { <span class="code-keyword">return</span> unlikely(fid_seq(fid) == FID_SEQ_DOT_LUSTRE &amp;&amp; fid_oid(fid) == FID_OID_DOT_LUSTRE); } </pre> </div></div> LU-3314

failed to check ".lustre" for the MDT upgraded from Lustre-2.x (x <= 3)

Bug Blocker Resolved Fixed nasf nasf LB fid Fri, 10 May 2013 08:49:22 +0000 Tue, 29 Apr 2014 20:12:34 +0000 Mon, 13 May 2013 19:50:20 +0000 Lustre 2.4.0 Lustre 2.4.0 0 7 <p>This is the patch:</p> <p><a href="http://review.whamcloud.com/#change,6309" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#change,6309</a></p> <p>Chris, Ned,<br/> This is advance warning that the above patch will potentially cause clients that are using the .lustre/ to be unable to access this directory until the next time they are remounted. We do not expect this to affect (m)any users, since .lustre is only used by lustre_rsync and HSM and "lfs fid2path", but it is worthwhile to alert you anyway. </p> <p>Andreas, thanks a lot for the heads up.</p> <p>The current solution is that:</p> <p>Use fixed FID {FID_SEQ_DOT_LUSTRE, FID_OID_DOT_LUSTRE, 0} for ".lustre" in spite of whether there are some old clients cached the ".lustre" IGIF or not. It enables the check "fid_is_dot_lustre()" on the MDT, although it will cause that the old connected clients cannot access the ".lustre" with the cached IGIF.</p> <p>Usually, it is rare case for the old connected clients to access the ".lustre" with cached IGIF. </p> <p>Landed for 2.4</p> Development Rank 1|hzvqnj: Rank (Obsolete) 8202 Severity