<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p style="margin-top:0;margin-bottom:0">Would you mind listing current lfs find options to help kickstart discussion?</p>
<p style="margin-top:0;margin-bottom:0"><br>
It seems like I might want it for lots of them, maybe close to all - For example, stripe size seems at first (to me) it wouldn't be useful, but what if I want to check to see if anyone is using a weird stripe size? I expect stripe size to be 1 MiB, and if
I can search for ! that, then I can find users who set weird stripe sizes and help them fix it.</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">- Patrick</p>
<p style="margin-top:0;margin-bottom:0"></p>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> lustre-discuss <lustre-discuss-bounces@lists.lustre.org> on behalf of Vitaly Fertman <c17818@cray.com><br>
<b>Sent:</b> Friday, April 26, 2019 10:35:54 AM<br>
<b>To:</b> lustre-discuss@lists.lustre.org<br>
<b>Subject:</b> [lustre-discuss] lfs find</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Hi<br>
<br>
during a discussion of a bug in lfs find, an improvement idea appeared, it is well<br>
described by Andreas below, and this thread is to discuss which options may need this<br>
functionality.<br>
<br>
<br>
> On 26 Apr 2019, at 03:41, Andreas Dilger <adilger@whamcloud.com> wrote:<br>
> <br>
> lfs find ! --pool HDD ...<br>
> <br>
> should IMHO find files that do not have any instantiated components in pool HDD, rather than files that have any component not on HDD.
<br>
> <br>
> That said, I could imagine that we may need to make some parameters more flexible, like adding "--pool =<poolname>" to allow specifying all components on the specified pool, and possibly + to specify "at least one component" (which would be the same as without
"+" but may be more clear to some users)? <br>
> <br>
> A similar situation arose with "-mode" for regular find (any vs. all bits) that took a while to sort out, so we should learn from what they did and get it right.
<br>
<br>
<br>
Vitaly Fertman<br>
_______________________________________________<br>
lustre-discuss mailing list<br>
lustre-discuss@lists.lustre.org<br>
<a href="http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org">http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org</a><br>
</div>
</span></font></div>
</body>
</html>