<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Units are kilobytes...<br>
</p>
<div class="moz-cite-prefix">On 2/24/20 10:38 PM, Mark Ito wrote:<br>
</div>
<blockquote type="cite"
cite="mid:5ea8fbc8-39f8-2f4b-8126-4d969c7a109a@jlab.org">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>Folks,</p>
<p>I made a listing of the 5,000 largest directories on
/volatile/halld_old, inclusive of subdirectories. Find it at</p>
<p> <a class="moz-txt-link-freetext"
href="https://halldweb.jlab.org/disk_management/volatile_halld_old.txt"
moz-do-not-send="true">https://halldweb.jlab.org/disk_management/volatile_halld_old.txt</a></p>
<p>You might want to grep it for your username if you are
wondering if you have any files at risk.</p>
<p> -- Mark<br>
</p>
<div class="moz-cite-prefix">On 2/24/20 5:50 PM, Mark Ito wrote:<br>
</div>
<blockquote type="cite"
cite="mid:01afde7f-cc2c-0a0b-98d3-aed5c55ecb14@jlab.org">
<p>Folks,<br>
</p>
<p>A reminder: all files on /volatile/halld_old will be deleted
in nine days, on Wednesday, March 4. See item 4 in the
procedure below.</p>
<p>There is still quite a lot of data in /volatile/halld_old.
People should check that they do not have anything important
there.<br>
</p>
<p> -- Mark</p>
<div class="moz-cite-prefix">On 1/23/20 6:20 PM, Mark Ito wrote:<br>
</div>
<blockquote type="cite"
cite="mid:80b4799d-93ac-6143-ae88-99850fc9986e@jlab.org">
<p>Gluons,</p>
<p>Our volatile disk space is moving to a newly purchased
Lustre system. I mentioned this at the last Software
Meeting. In the end our space will double from 70 TB to 140
TB. This will also give us independence from LQCD Lustre.</p>
<p>Recall that volatile is not backed up and <a
moz-do-not-send="true"
href="https://scicomp.jlab.org/docs/volatile_disk_pool">files
are subject to deletion when it gets full</a>, just as
before.</p>
<p>The transition will start on Tuesday, February 4. And it
goes like this (please note step 4):</p>
<ol>
<li>/volatile/halld will be renamed as /volatile/halld_old.
All files and directories will be preserved other than the
change to the name of the top level directory. Files can
be read from and written to the renamed location.<br>
</li>
<li>A new directory will appear on the new system named
/volatile/halld (what else?). It will be empty, no
directories, no files. This is our new volatile space.<br>
</li>
<li>We can now use the new space in any way we like. An
example of a likely use is to copy the contents of
/volatile/halld_old/foo/bar to /volatile/halld/foo/bar.
Such actions will not happen automatically. SciComp
requests that we delete the contents of
/volatile/halld_old/foo/bar after such a copy is done, but
deletion is not required.</li>
<li>After a month, all files remaining on
/volatile/halld_old will be deleted.<br>
</li>
</ol>
<p>Hall B is in the process of going through this now, FYI.</p>
<p> -- Mark</p>
<p><br>
</p>
</blockquote>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Halld-offline mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Halld-offline@jlab.org">Halld-offline@jlab.org</a>
<a class="moz-txt-link-freetext" href="https://mailman.jlab.org/mailman/listinfo/halld-offline">https://mailman.jlab.org/mailman/listinfo/halld-offline</a></pre>
</blockquote>
</body>
</html>