As some of you may have noticed, this morning jcwren's perlmonk.org server went down.
For the second time in recent memory, perlmonk.org spontaneously declared its filesystem to be read-only, most
likely due to physical disk errors. Unfortunately this time, despite the RO filesystem passing fsck before the
restart, rebooting didn't fix the problem. Our best guess, at this point, is that the hard drive is failing.
This evening it should be possible to have someone power cycle the machine. If that does not work, jc will
attempt to get to the server later this week for hands-on troubleshooting. Whatever the case, if you are a
perlmonk.org user you'll want to back up your data immediately when next you find the server up. While there is
a slight chance that the data will be irrecoverable, every effort will be made to restore the system to its former...
er... glory as soon as possible. ;-)
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
