<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><br></div>Hi All,<div><br></div><div> See the message below from Sandy. We had always had running independent of the CC as a design goal.</div><div>This will be a partial actual test of it. Before it happens, does anyone know of any dependency we have that may</div><div>prevent us from running if those filesystems go away?</div><div><br></div><div>Regards,</div><div>-David<br><div><br><div>Begin forwarded message:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; color:rgba(0, 0, 0, 1.0);"><b>From: </b></span><span style="font-family:'Helvetica';">Sandy Philpott <<a href="mailto:philpott@jlab.org">philpott@jlab.org</a>><br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; color:rgba(0, 0, 0, 1.0);"><b>Subject: </b></span><span style="font-family:'Helvetica';"><b>outage of offline farm systems Feb 23 (and Feb 24 if needed)</b><br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; color:rgba(0, 0, 0, 1.0);"><b>Date: </b></span><span style="font-family:'Helvetica';">February 10, 2016 at 2:49:18 PM EST<br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; color:rgba(0, 0, 0, 1.0);"><b>To: </b></span><span style="font-family:'Helvetica';">Ole Hansen <<a href="mailto:ole@jlab.org">ole@jlab.org</a>>, Robert Michaels <<a href="mailto:rom@jlab.org">rom@jlab.org</a>>, Sergey Boyarinov <<a href="mailto:boiarino@jlab.org">boiarino@jlab.org</a>>, Harut Avakian <<a href="mailto:avakian@jlab.org">avakian@jlab.org</a>>, Brad Sawatzky <<a href="mailto:brads@jlab.org">brads@jlab.org</a>>, Stephen Wood <<a href="mailto:saw@jlab.org">saw@jlab.org</a>>, David Lawrence <<a href="mailto:davidl@jlab.org">davidl@jlab.org</a>>, Mark Ito <<a href="mailto:marki@jlab.org">marki@jlab.org</a>><br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; color:rgba(0, 0, 0, 1.0);"><b>Cc: </b></span><span style="font-family:'Helvetica';">Heyes Graham <<a href="mailto:heyes@jlab.org">heyes@jlab.org</a>>, Chip Watson <<a href="mailto:watson@jlab.org">watson@jlab.org</a>><br></span></div><br><div>Hello Physics Onliners and Offliners,<br><br>We are planning updates to our Lustre 2.5.3 filesystem on Tuesday Feb 23 that will impact the batch farm and storage, as the Lustre-based /mss, /cache, /work, and /volatile filesystems will be unavailable. File services may be restored at the end of the 10 hour day Tuesday, or if more time is needed we may continue through Wednesday cob. This update is part of our continuing effort to improve the stability of the Lustre and ZFS hardware and software that have been intermittently problematic since our upgrade from Lustre 1.8 started last May. <br><br>Please verify that your online systems can sustain up to a 72 hour outage without data center services if you are running beam then, before we announce this up-to-36-hour-outage to all the users. Or, please let me know if this outage won't impact your experimental hall's online systems because you won't be running.<br><br>Thanks,<br>Sandy<br><br></div></blockquote></div><br></div></body></html>