Semi-real-time space monitoring is pretty straightforward with
ECMAScript & XMLRPC. I've never really been a fan of using used
+ avail as a metric; it's simply too imprecise for this kind of
work. With XMLRPC, you can gauge costs down to the byte, and with
Javascript/ECMAScript you have some easy date handling for your
report.

I had some issues with my Garmin 910xt, but eventually I fixed the mock tri file. Woot! Next time, I'll disable all auto lap functionality before starting the tri, because apparently that's what interferes with the run data & corrupts the file.

A frequently-asked-question on ZFS Appliance-related mailing lists is "How often should I scrub my disk pools?" The answer to this is often quite challenging, because it really depends on you and your data.

Usually when asked a question I want to provide the answers to the questions they should have asked first, so that I'm certain our shared conversational contexts match up. So here's some background questions that we should have answers to before answering the "How often" question.

ZFS: Doing It Right

Imagine you're a system administrator, and an email arrives from your boss. It goes something like this:

"Hey, bud, we need some new storage for Project Qux. We heard that this [insert major company here] uses a product called the Oracle Sun ZFS Storage Appliance as the back-end for their [insert really popular app here]. We want to do something like that at similar scale; can you evaluate how well that compares to XYZ storage we already own?"

So you get in touch with your friendly local ZFS sales dudette, who arranges a meeting that includes a Sales Engineer to talk about technical stuff related to your application. The appliance, however, has an absolutely dizzying array of options. Where do you start?