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-3087 Lustre <p>When a file layout is created or changed no changelog record is generated.<br/> We propose to add a CL_LAYOUT event.<br/> First use case seen are:</p> <ul class="alternate" type="square"> <li>file created</li> <li>layout allocated after file created with LOV_DELAY_CREATE</li> <li>layout swap (1 event per file)</li> </ul> LU-3087

File layout change does not generate a changelog record

Bug Minor Resolved Fixed Jinshan Xiong CEA Tue, 2 Apr 2013 13:27:12 +0000 Wed, 5 Aug 2020 13:32:56 +0000 Thu, 18 Apr 2013 00:57:10 +0000 Lustre 2.4.0 0 5 <p>We will propose a patch</p> <p>Jinshan</p> <p>I think that you will be the natural person to review this patch when it has been supplied</p> <p>Peter</p> <p>shouldn't the even for xattr change be enough?</p> <p>The xattr event can be used but it comes from the implementation of lovea and the way it is written on disk. We think a CL_LAYOUT event which matches the "functional" change is better.</p> <p>strictly speaking, there is no notion of layout in MDD... MDD isn't even aware always of layout change.</p> <p>Additionally, changelog readers (lustre_rsync or robinhood, typically) may react differently to setxattr and layout changes. This was rather in favor of adding a CL_LAYOUT event.</p> <p>setxattr(LOVEA) is changing layout by definition, no?</p> <p>yes but it comes from the way lovea is implemented in lustre, this is side effect of implementation not a goal</p> <p>speaking of goals.. I'd rather say there should be no notion of layout on the server (MDS) - the less details to take care about, the better scalability.</p> <p>Here's a patch to address the issue: <a href="http://review.whamcloud.com/5966" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/5966</a></p> <p>Landed for 2.4</p> Development Rank 1|hzvmvb: Rank (Obsolete) 7501 Severity