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-1331 Lustre <p>In Lustre MDT changelog, rename operations are splitted in 2 lines CL_RENAME (displayed as RNMFM) and CL_EXT (displayed as RNMTO).<br/> I found some case where those 2 records are not consecutive in the changelog: other operations are inserted between them.</p> <p>example:<br/> 14989521 08RNMFM 03:09:52.275492602 2012.04.14 0x0 t=<span class="error">&#91;0x20000b8d3:0xaae6:0x0&#93;</span> p=<span class="error">&#91;0x20000b7ba:0x4b4c:0x0&#93;</span> .adcread.q6TIXm<br/> 14989522 14SATTR 03:09:52.275492602 2012.04.14 0x14 t=<span class="error">&#91;0x20000b7bb:0x1c1e:0x0&#93;</span><br/> 14989523 09RNMTO 03:09:52.275492602 2012.04.14 0x0 t=<span class="error">&#91;0:0x0:0x0&#93;</span> p=<span class="error">&#91;0x20000b7ba:0x4b4c:0x0&#93;</span> adcread</p> <p>Looking at lustre_rsync code, it seems CL_RENAME and CL_EXT are expected to be consecutive.<br/> So there are 2 options:</p> <ul class="alternate" type="square"> <li>lustre_rsync does a bad asumption about that<br/> or</li> <li>there is a locking or transaction issue when generating CL rename records which allows another operation to be logged in between</li> </ul> <p>Given that CL_EXT is an extra info related to CL_RENAME, it would be easier if they are together in the log...</p> LU-1331

changelogs: RNMTO record not always after RNMFRM

Bug Minor Resolved Fixed Lai Siyao Thomas LEIBOVICI - CEA Tue, 17 Apr 2012 10:46:01 +0000 Thu, 11 Jul 2013 16:06:58 +0000 Thu, 24 Jan 2013 13:15:10 +0000 Lustre 2.0.0 Lustre 2.1.0 Lustre 2.3.0 Lustre 2.1.5 0 6 <p>Lai</p> <p>Could you please look into this one?</p> <p>Thanks</p> <p>Peter</p> <p>Yes, the two rename logs should be written atomically, instead of introducing new lock which may hurt parallel operation performance, it's better to add llog support to write multiple records in one blow. This will change quite a number of interfaces, I'll commit the fix later.</p> <p>review is on <a href="http://review.whamcloud.com/#change,2577" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#change,2577</a>, Thomas, could you help verify it?</p> <p>Thomas</p> <p>When do you expect to be able to test whether this fix works for you&gt;</p> <p>Peter</p> <p>Patch landed.</p> <p>b2_1 patch port tracking at <a href="http://review.whamcloud.com/3835" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/3835</a></p> Duplicate LU-2866 Related LU-1458 Development Rank 1|hzv6bz: Rank (Obsolete) 4560 Severity