<div dir="ltr">I agree. It might not be critical, but there's probably a good 30 or 40 devs that rely on it. (It's our jenkins box). Unfortunately there isn't really someone who "owns" it in the traditional sense. Unfortunately since I both #1 noticed it was broken and #2 attempted to fix it, I may have "volunteered" myself for the job. We'll have to see how things shake out. It's a hard box to take control of really, everyone has root, and I can't change the root without breaking numerous jobs, but I will say this. If I just "inherited" the jenkins box, #1 the long snapshot chain is going bye-bye, #2 I'm going to have to figure out some way to back it up, and #3 I don't care what anybody says, I'm patching the @#$@#$ thing. What's Debian on? 8? (sheesh)<div><br></div><div>Mike B</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 12, 2016 at 11:45 PM, David L. Anselmi <span dir="ltr"><<a href="mailto:anselmi@anselmi.us" target="_blank">anselmi@anselmi.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">Mike Bean wrote:<br>
> We have a fairly major system at work that somehow lost track of a disk<br>
> ALERT! /dev/disk/by-uuid/(some id) does not exist. Dropping to a shell<br>
<br>
</span>Here's a Debian bug that describes this symptom. Maybe the cause is similar.<br>
<br>
<a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741342" rel="noreferrer" target="_blank">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741342</a><br>
<span class=""><br>
> Must admit, my google-fu has failed me. I have no idea. I have a snapshot<br>
> I can revert to, but it's an old one, and the users will lose allot of<br>
> their work.<br>
<br>
</span>That sounds negligent to me (perhaps even in the legal sense). Snapshots != backups. There are two<br>
kinds of people in the world... Etc.<br>
<br>
Do the users at least know that their data on that machine will disappear one day?<br>
<br>
Once there was a windy ice storm that caused arcing on the power lines out to DIA. They have 2 feeds<br>
but the lines are set up the same way so both arced, tripping their breakers, and the airport was<br>
without power. So supposedly things like ILS and radar have backups but things like bag check<br>
computers and security check point scanners and computers don't.<br>
<br>
The quote from the DIA spokesperson was, "we've lost power to some critical systems". My thought<br>
was, if you've lost power then they aren't critical. And in the sense of ground related impacts<br>
causing death they weren't.<br>
<br>
So your system might not be critical. But without backups it might not qualify as useful either.<br>
Sure, I've worked in the defense business so I can understand that your hands might be tied. But you<br>
could at least put up an MOTD warning, couldn't you?<br>
<br>
Dave<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
_______________________________________________<br>
clue mailing list: <a href="mailto:clue@cluedenver.org">clue@cluedenver.org</a><br>
For information, account preferences, or to unsubscribe see:<br>
<a href="http://cluedenver.org/mailman/listinfo/clue" rel="noreferrer" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br>
</div></div></blockquote></div><br></div>