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-16320 Lustre <p>If directory layout is changed, client may send request to wrong MDT based on the old layout, e.g. directory split from 2 stripes to 3 stripes, client created a sub file under stripe2 in old layout, but this file should be located on stripe3 in new layout.</p> <p>To avoid such race, client can pack parent layout version in request, and MDT will compare layout version before processing, if mismatch, return -EAGAIN with a certain flag to client, and client can update directory layout and try again.</p> <p>Combined with FID map in <a href="https://jira.whamcloud.com/browse/LU-7607" title="Preserve inode number after MDT migration " class="issue-link" data-issue-key="LU-7607">LU-7607</a>, directory layout change may become opaque to user applications in most cases. </p> LU-16320

Pack parent directory layout version in client request

Improvement Minor Open Unresolved Lai Siyao Lai Siyao Thu, 17 Nov 2022 12:52:56 +0000 Thu, 17 Nov 2022 17:36:46 +0000 0 4 <p>Returning EAGAIN might be confusing in some cases. What about EREMOTE?</p> <p>as long as it results in layout refresh and retry it probably does not matter, but since EAGAIN means so many other things, perhaps ESTALE and friend might be a better choice?</p> <p>EREMOTE might not even be a correct choice because the stale layout could result in an RPC to a correct MDT, but we don't really know on the server, right?</p> Development Rank 1|i035z3: Rank (Obsolete) 9223372036854775807