<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body>
<div style="color: rgb(33, 33, 33); background-color: rgb(255, 255, 255);"><br>
</div>
<div id="ms-outlook-mobile-signature">
<div><br>
</div>
-Eugene</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> Clas_offline <clas_offline-bounces@jlab.org> on behalf of Nathan Baltzell <baltzell@jlab.org><br>
<b>Sent:</b> Tuesday, February 18, 2020 10:09:56 AM<br>
<b>To:</b> clas12 software <clas12_software@jlab.org>; CLAS-OFFLINE <clas_offline@jlab.org>; HPS-SOFTWARE <hps-software@SLAC.STANFORD.EDU>; prad@jlab.org <prad@jlab.org><br>
<b>Subject:</b> Re: [Clas_offline] preparations for new Hall B /volatile</font>
<div> </div>
</div>
<style type="text/css" style="display:none">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0); background-color:rgb(255,255,255)">
Hello All,</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0); background-color:rgb(255,255,255)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0); background-color:rgb(255,255,255)">
One final REMINDER:</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0); background-color:rgb(255,255,255)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0); background-color:rgb(255,255,255)">
The deadline has passed, and *tomorrow* morning files on our old volatile be deleted:</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0); background-color:rgb(255,255,255)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0); background-color:rgb(255,255,255)">
/volatile/clas12_old</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0); background-color:rgb(255,255,255)">
/volatile/clas_old</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0); background-color:rgb(255,255,255)">
/volatile/hallb_old</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0); background-color:rgb(255,255,255)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0); background-color:rgb(255,255,255)">
-Nathan</div>
<div id="x_appendonsend"></div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Nathan Baltzell <baltzell@jlab.org><br>
<b>Sent:</b> Wednesday, February 5, 2020 9:57 AM<br>
<b>To:</b> clas12 software <clas12_software@jlab.org>; CLAS-OFFLINE <clas_offline@jlab.org>; HPS-SOFTWARE <hps-software@slac.stanford.edu>; prad@jlab.org <prad@jlab.org><br>
<b>Subject:</b> Re: [Clas_offline] preparations for new Hall B /volatile</font>
<div> </div>
</div>
<div class="x_BodyFragment"><font size="2"><span style="font-size:11pt">
<div class="x_PlainText">Hello All,<br>
<br>
REMINDER: Next Thursday, February 14, is still the scheduled end-of-life for files on the *old* Hall B /volatile filesystems:<br>
<br>
/volatile/clas12_old<br>
/volatile/clas_old<br>
/volatile/hallb_old<br>
<br>
If you want to keep any data that currently exists there, it needs to be copied elsewhere (e.g. the new /volatile/clas12, /volatile/clas, /volatile/hallb).<br>
<br>
And, if you have any data in those old /volatile directories that can be deleted, scicomp would like us to do that to expedite draining it and returning it to the new Lustre filesystems.<br>
<br>
FYI, more increase to this new Lustre is on its way, starting with another 2.2 PB for ENP in the coming weeks.<br>
<br>
-Nathan<br>
<br>
<br>
<br>
> On Jan 15, 2020, at 10:24, Nathan Baltzell <baltzell@jlab.org> wrote:<br>
> <br>
> Hello All,<br>
> <br>
> So far there’s been no complaints to hold this up. Unless that changes, the plan is to do the flip tomorrow, Thursday, January 16, at 10:00 AM.<br>
> <br>
> Here’s the final details:<br>
> <br>
> 1. All our existing, top-level /volatile directories and their data will be remounted/renamed with “_old” suffixes. These will remain available for at least 1 month, but read-only. For example:<br>
> <br>
> /volatile/clas12 -> /volatile/clas12_old<br>
> /volatile/clas/clase1 -> /volatile/clas/clase1_old<br>
> /volatile/hallb/prad -> /volatile/hallb/prad_old<br>
> <br>
> 2. The new filesystem will replace the old one, with all top-level directories and their permissions intact, but empty with *no* contents.<br>
> <br>
> 3. We then move any data we want from the old filesystem to the new one, recreate directory structures, etc.<br>
> <br>
> After no less than one month, the old filesystem will be deleted/drained (with a reminder email a ~week in advance) and returned to the disk pool for a further increase. To expedite that, us deleting our data on the old filesystem in advance will help.<br>
> <br>
> -Nathan<br>
> <br>
> <br>
> <br>
>> On Jan 13, 2020, at 20:14, Nathan Baltzell <baltzell@jlab.org> wrote:<br>
>> <br>
>> Hello Everyone,<br>
>> <br>
>> JLab's Scicomp is almost ready to switch Hall-B's Lustre filesystems at /volatile to new hardware, which should give us a *very* significant increase in disk space.<br>
>> <br>
>> However, the proposed transition will not be completely transparent to users with existing data on /volatile. See below for details.<br>
>> <br>
>> The earliest possible date for this is January 16, Thursday of this week. The next option would be next Tuesday, January 20, after the long weekend.<br>
>> <br>
>> This transition ideally applies to all these, and everything they contain, in one shot:<br>
>> <br>
>> /volatile/clas12<br>
>> /volatile/hallb<br>
>> /volatile/clas<br>
>> <br>
>> The proposed transition minimizes downtime and system overhead, but will *not* automatically replicate anyone's existing /volatile data to the new filesystem:<br>
>> <br>
>> 1. The old /volatile directories above will be renamed/remounted as /volatile-old (or a similar name), become *read-only*, and remain readable for ~one month (similar to our current lifetime on /volatile).<br>
>> <br>
>> 2. The new /volatile filesystem will replace the old one, with all quota-level directories and permissions replicated, but sub-directories left to us to recreate as needed.<br>
>> <br>
>> 3. We can then copy data from /volatile-old to /volatile if we want to, or leave it there (and keep reading it) until it is deleted in a ~month.<br>
>> <br>
>> I'm not aware of any production accounts currently running long batch workflows using /volatile. It will be good to minimize this transition's impact (and get a huge increase in disk space), so please let me know if you have any considerations, concerns,
etc about this.<br>
>> <br>
>> There will be a followup email with the final date and details ...<br>
>> <br>
>> Regards,<br>
>> Nathan<br>
> <br>
> _______________________________________________<br>
> Clas_offline mailing list<br>
> Clas_offline@jlab.org<br>
> <a href="https://mailman.jlab.org/mailman/listinfo/clas_offline">https://mailman.jlab.org/mailman/listinfo/clas_offline</a><br>
<br>
</div>
</span></font></div>
</div>
</body>
</html>