If the machines were awake for 12 extra hours a day, and drew 100 watts, that's 0.1kW * 5000machines * 12hours = 6000kWh per day.

Where I live, electricity costs about 20 cents per kWh. 0.2dollars * 6000kWh * 365days * 9years = $3.94 million.

reminds me a lot of an old multiplayer network game called "liquid war"

http://www.ufoot.org/liquidwar

http://www.youtube.com/watch?v=nj65vUy3rK8

I loved that game! I must've sunk countless hours playing against the AI's. For being so simple, it's remarkably fun.

Also reminds of another old game called 'Colors of War' http://colors-of-war.webs.com/

What does "scrub repaired 1.58M in 201h47m with 0 errors on Fri Feb 21 13:37:24 2014" mean?

I have a much smaller zfs setup at home, as well as a few at work, and I would be super concerned if the scrubs were repairing data. Am I overreacting?

It means I ran a scrub that completed on February 21, 2014 after almost 202 hours, and there were no errors, but there were some corrupt data blocks that were repaired from mirrors, adding up to 1.58MB of data that was repaired.

See http://docs.oracle.com/cd/E23823_01/html/819-5461/gbbwa.html... for more information.

Sorry, I should have worded that better. I know what the message means, but what do you make of the fact that it found & repaired corrupt data? If I understand right (and correct me if I'm wrong), corrupt data should only occur if some bit of hardware is failing or possibly after improper shutdown. Am I wrong? Is it no big deal to see scrubs repairing data?

My understanding is that some significant (thousands of bytes) silent corruption is inevitable when you start reaching huge capacities over long-ish periods of time; even cosmic radiation has the potential to flip a few bits here and there every once in a while.

http://en.wikipedia.org/wiki/Data_corruption#Silent_data_cor...

So, yes, I think even with the best hardware, and proper maintenance, seeing some data repaired in a scrub is to be expected.

(That said, I did spend way too long using technology [SATA PM] that often failed and made it impossible for me to run a scrub. It's very possible that normal error rates are more like what I'm seeing now, a single byte every month or so, and that the megabyte figure is representative of errors from the days of my arrays dropping out unexpectedly.)

The parts that generate the lion's share of heat in an LED bulb are tiny tiny tiny, and so they can get very hot with much less energy. They generally have chunky heatsinks, but still you can only draw heat away from a point the size of a head of a pin so fast.

I like to use elements. Bonus if you're working with the first half of a /24, last octet = atomic weight. 10.0.0.1 = hydrogen, etc.

In your background image, the screws at the top are threaded anticlockwise, but have a clockwise rotation arrow. Vice versa for the screw at the bottom by the robot head.