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-13015 Lustre <h2><a name="lfswbccommands"></a>lfs wbc commands</h2> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> # lfs wbc cache $DIR </pre> </div></div> <p>If $DIR is an empty directory, try to acquire WBC EX lock from MDT for $DIR;<br/> If $DIR is not an empty directory, add hint to the directory $DIR to indicate that:</p> <ul> <li>all new creating sub dirs ( not include regular files?) should obtain the EX lock;</li> <li>New sub dirs create on MDT synchronously.</li> <li>New sub dirs are in (P|S) state;</li> </ul> <p> </p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> # lfs wbc list $MOUNT </pre> </div></div> <p>List all root WBC directories on a client.</p> <p> </p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> # lfs wbc uncache $DIR </pre> </div></div> <p>Sync and remove a cached root WBC directory $DIR.</p> <p> </p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> #lfs wbc state $file </pre> </div></div> <p>Display the WBC state of the file $file.</p> <h2><a name="lctlwbccommands"></a>lctl wbc commands</h2> <p><a href="https://jira.whamcloud.com/browse/LU-13012" title="WBC: Rule based auto WBC" class="issue-link" data-issue-key="LU-13012">LU-13012</a> WBC: Rule based auto WBC;</p> <p> </p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> # lctl wbc /mnt/lustre [--data-on-pcc] [--metadata-on-pcc] [--device /mnt/pcc] [--memfs]... </pre> </div></div> LU-13015

WBC: lfs wbc and lctl wbc utils

Technical task LU-10938 Blocker Open Unresolved Qian Yingjin Qian Yingjin Tue, 26 Nov 2019 15:41:17 +0000 Fri, 29 Nov 2019 23:09:57 +0000 0 4 <p>I think it makes sense for the client to <b>always</b> try to get the WBC EX directory lock on a new directory. In the worst case this causes an extra LDLM blocking callback if the directory is immediately contended, but I think the far more common case is that the client creating the directory will also create at least a few files in it (eg. num_threads per client) before it is accessed by other clients. This makes WBC immediately useful for users, and also improves test coverage significantly. </p> <p>The "<tt>lfs wbc cache $DIR</tt>" command should force the client to try and get the WBC EX lock on <b>existing</b> directory "<tt>$DIR</tt>" and fetch the list of filenames via <tt>readdir</tt> so that it can make local decisions whether the filename exists already or not. Eventually, even the fetching and caching of directory entries should be done automatically based on how many files the one client is creating in the same directory, and if other clients are contending for the directory lock. For WBCv1 we shouldn't try to handle existing directories, only new directories.</p> Related LU-10938 LU-13012 LU-10938 Development Rank 1|i00pzb: Rank (Obsolete) 9223372036854775807