<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>The work disk is now available for use. In fact it was ready
about an hour ago (I misinterpreted the message I received at that
time).<br>
</p>
<br>
<div class="moz-cite-prefix">On 11/29/2017 10:20 AM, Mark Ito wrote:<br>
</div>
<blockquote type="cite"
cite="mid:b7c165bb-6891-4663-43c8-00670255c4af@jlab.org">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<p>The move is still in progress, though very close to done. Stay
tuned for the all-clear...<br>
</p>
<br>
<div class="moz-cite-prefix">On 11/28/2017 10:47 AM, Mark Ito
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:535ed039-534a-7e51-27f0-74952b68694f@jlab.org">
<meta http-equiv="content-type" content="text/html;
charset=utf-8">
<p>Folks,<br>
<br>
We are scheduled to make the move of our work space from a
Lustre-based system to a ZFS file system. This will happen
tomorrow (Wednesday, November 29) starting at 9 am. The move
should take about an hour.<br>
<br>
N. B.: <b>during this time, you will not be able to write to
the Hall D work disks</b>. Reading may be intermittent as
well.<br>
<br>
Some notes on the new configuration:<br>
<br>
Both /work/halld and /work/halld2 will be on the same
partition. The old /work/halld2 will actually appear as a new
directory, /work/halld/halld2. A merge of the two systems is
not a practical option. There will be a soft link,
/work/halld2 pointing to the new /work/halld/halld2 directory,
so legacy scripts should work.<br>
<br>
Since there will be no distinction in the underlying hardware
for the old /work/halld and /work/halld2, there is no more
need to distinguish how they should be used. Small files and
SQLite files are OK anywhere on the new work disk.<br>
<br>
To reduce future confusion, you may want to move your files
out of /work/halld/halld2, but that is not required at
present.<br>
<br>
Any scripts that use<br>
</p>
<p> /lustre/expphy/work/halld or /v/lustre2/expphy/work/halld</p>
<p>instead of</p>
<p> /work/halld</p>
<p>or that use<br>
</p>
<p> /w/halld-scifs1a</p>
<p>instead of</p>
<p> /work/halld2<br>
</p>
<p>will break. In other words, the server-specific directory
names will change (as they must).<br>
<br>
Let me know if there are any questions or objections to this
schedule.<br>
<br>
- Mark<br>
</p>
<pre class="moz-signature" cols="72">--
Mark Ito, <a class="moz-txt-link-abbreviated" href="mailto:marki@jlab.org" moz-do-not-send="true">marki@jlab.org</a>, (757)269-5295
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Halld-offline mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Halld-offline@jlab.org" moz-do-not-send="true">Halld-offline@jlab.org</a>
<a class="moz-txt-link-freetext" href="https://mailman.jlab.org/mailman/listinfo/halld-offline" moz-do-not-send="true">https://mailman.jlab.org/mailman/listinfo/halld-offline</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Mark Ito, <a class="moz-txt-link-abbreviated" href="mailto:marki@jlab.org" moz-do-not-send="true">marki@jlab.org</a>, (757)269-5295
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<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>
<br>
<pre class="moz-signature" cols="72">--
Mark Ito, <a class="moz-txt-link-abbreviated" href="mailto:marki@jlab.org">marki@jlab.org</a>, (757)269-5295
</pre>
</body>
</html>