<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 20, 2017 at 10:19 PM, Dilger, Andreas <span dir="ltr"><<a target="_blank" href="mailto:andreas.dilger@intel.com">andreas.dilger@intel.com</a>></span> wrote:<br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
<div dir="auto">
<div>The underlying "lfs migrate" command (not the "lfs_migrate" script) in newer Lustre versions (2.9) is capable of migrating files that are in use by using the "--block" option, which prevents other processes from accessing or modifying the file during migration.</div>
<div><br>
</div>
<div>Unfortunately, "lfs_migrate" doesn't pass that argument on, though it wouldn't be hard to change the script. Ideally, the "lfs_migrate" script would pass all unknown options to "lfs migrate". </div>
<div><br>
</div>
<div><br>
</div>
<div>The other item of note is that setting the OST inactive on the MDS will prevent the MDS from deleting objects on the OST (see <a target="_blank" href="https://jira.hpdd.intel.com/browse/LU-4825">https://jira.hpdd.intel.<wbr>com/browse/LU-4825</a> for details). In Lustre 2.9
and later it is possible to set on the MDS:</div>
<div><br>
</div>
<div> mds# lctl set_param osp.<OST>.create_count=0</div>
<div><br>
</div>
<div>to stop MDS allocation of new objects on that OST. On older versions it is possible to set on the OSS:</div>
<div><br>
oss# lctl set_param obdfilter.<OST>.degraded=1</div>
<div><br>
</div>
<div>so that it tells the MDS to avoid it if possible, but this isn't a hard exclusion.</div>
<div><br>
</div>
<div>It is also possible to use a testing hack to mark an OST as out of inodes, but that only works for one OST per OSS and it sounds like that won't be useful in this case. </div>
<div><br>
<div>Cheers, Andreas</div></div></div></blockquote><div>You're making me want Lustre 2.9 more :) but for now I'm still stuck on
2.8 and because this is very much production these days I'm more careful
with the update (hoping to finally get hw allocated for a test env soon
to test the update).<br></div><div>Thanks,<br></div><div>Eli <br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"><div dir="auto"><div>
</div><div><div class="gmail-h5">
<div><br>
On Mar 20, 2017, at 13:11, Brett Lee <<a target="_blank" href="mailto:brettlee.lustre@gmail.com">brettlee.lustre@gmail.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div dir="ltr">
<div>Hi Eli,<br>
<br>
I believe that is still the case with lfs_migrate. If otherwise, we'll probably hear soon.<br>
<br>
You should be able to disable those OSTs while keeping the file system active - via a command on the MDS(s) as well as the clients. My notes have the command as shown below, but please confirm via the appropriate Lustre manual:<br>
<br>
</div>
lctl set_param osc.<fsname>-<OST00xy>-*.<wbr>active=0<br>
<div>
<div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">
<div>
<div class="gmail-m_2989405016505302045gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div>Brett</div>
<div>--<br>
</div>
<div dir="ltr"><span style="font-size:small">Protect Yourself </span><span style="font-size:small"><span><span style="font-size:small">Against</span></span> Cybercrime</span><br>
<div>
<div>PDS Software Solutions LLC</div>
<div><a target="_blank" href="https://www.trustpds.com/">https://www.TrustPDS.com</a></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">On Mon, Mar 20, 2017 at 10:43 AM, E.S. Rosenberg <span dir="ltr">
<<a target="_blank" href="mailto:esr+lustre@mail.hebrew.edu">esr+lustre@mail.hebrew.edu</a>></span> wrote:<br>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
<div dir="ltr">
<div>
<div>
<div>
<div>In the man page it says the following:<br>
<br>
Because lfs_migrate is not yet closely integrated with the MDS, it cannot determine whether a file is currently open and/or in-use by other applications or nodes. That makes it UNSAFE for use on files that might be modified by other applications, since
the migrated file is only a copy of the current file, and this will result in the old file becoming an open-unlinked file and any modifications to that file will be lost.<br>
<br>
</div>
Is this still the case?<br>
</div>
Is there a better way to disable OSTs while keeping the filesystem live?<br>
<br>
</div>
<div>Background:<br>
</div>
<div>We need to take a OSS enclosure that hosts multiple OSTs offline for hardware maintenance, I'd like to do this without bringing Lustre as a whole down. I made sure there is enough space on the other OSTs to house the contents of the machine going offline
and am now about to move things.<br>
</div>
<div><br>
</div>
Thanks,<br>
</div>
Eli<br>
</div>
<br>
______________________________<wbr>_________________<br>
lustre-discuss mailing list<br>
<a target="_blank" href="mailto:lustre-discuss@lists.lustre.org">lustre-discuss@lists.lustre.or<wbr>g</a><br>
<a target="_blank" rel="noreferrer" href="http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org">http://lists.lustre.org/listin<wbr>fo.cgi/lustre-discuss-lustre.<wbr>org</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>______________________________<wbr>_________________</span><br>
<span>lustre-discuss mailing list</span><br>
<span><a target="_blank" href="mailto:lustre-discuss@lists.lustre.org">lustre-discuss@lists.lustre.<wbr>org</a></span><br>
<span><a target="_blank" href="http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org">http://lists.lustre.org/<wbr>listinfo.cgi/lustre-discuss-<wbr>lustre.org</a></span><br>
</div>
</blockquote>
</div></div></div>
</blockquote></div><br></div></div>