pool: exportpool
state: ONLINE
status: The pool is formatted using an older on-disk format. The pool can
still be used, but some features are unavailable.
action: Upgrade the pool using 'zpool upgrade'. Once this is done, the
pool will no longer be accessible on older software versions.
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
exportpool ONLINE 0 0 0
c0t0d0s7 ONLINE 0 0 0
c0t1d0 ONLINE 0 0 0
errors: No known data errors
So, for a verbal explanation, it’s a striped pool made up of one whole disk, plus one partition on c0t0d0, which also happens to be the root disk, where there are numerous other partitions housing the ufs filesystems. Those partitions are completely unmirrored. Oh, and it’s out of date, to boot.
If either disk goes, the whole system goes. The performance for the zpool will be completely weird depending on which disk it hits. And to top it all off, they are forever entangled now. This is set in stone, unless a complete system wipe can be performed.
Good job.
It may be a day late and a dollar short, since I replaced the bad cat 5 cable that kept causing my colo’ed server to get disconnected, but it’d be a shame to let that extra interface go to waste.
May 13 14:39:54 holcasaur.us in.mpathd[25625]: [ID 832587 daemon.error] Successfully failed over from NIC bge0 to NIC bge1
May 13 14:40:20 holcasaur.us in.mpathd[25625]: [ID 620804 daemon.error] Successfully failed back to NIC bge0
So I say, go ahead, treat my cables roughly. Jiggle the connections, come what may! Let me not bother the poor support staff any longer.
It was so easy to set up I’m not even going to write about it. Just go to the docs.
So regarding my previous post on generating pretty links with wordpress. After reexamining the Apache way, and reading a bit more about how sun web server does rewriting and expressions, I finally figured out the “right” way to do it.
Behold the true form:
<If not -e"$path">
PathCheck fn="restart" uri="/index.php"
</If>
No wacky server.xml variables, no regular expressions, and no rewriting before we should.
First of all, I got rid of the expensive (?) ~= that matched everything after the first / in the uri. In this case we don’t need it, because secondly, we always just want to redirect to /index.php. Wordpress figures out the rest of the arguments from other magic variables that I don’t fully understand yet (probably PATH_INFO). Thirdly, I changed it to a PathCheck fn=restart since at the PathCheck stage it is possible to determine if $path exists as a physical file. We just restart the whole shebang with a new uri if it’s not. And for cleanliness sake, fourthly, I switched from not -f and not -d to one simple not -e which accomplishes the same thing.
Hope this helps someone besides me. I’m planning a follow up post describing some of the performance characteristics. I’ve tried fastcgi vs the nsapi plugin with php and as a preview: the plugin is hella fast, but hella leaky as well, whereas the fastcgi is rock solid but can’t scale past the number of child processes I give it. Also APC makes a HUGE difference, especially with the nsapi plugin. Too bad about those leaks…
Sugar? Cream? Whiskey? Heroin?
If anything, you’re solving the wrong problem. The problem isn’t a lack of something in your coffee, it’s that your coffee tastes like shit. You should try some real coffee.
And not to be accusitory, but you probably solve the wrong problem elsewhere in your life. There is a lot of that going on right now and it’s pretty frustrating. Here’s a simple example from work: we have some ancient, unsupported devices that are causing network problems. Right now a good portion of the team is busy hacking away and trying to figure out how to get to the logs, what the procedures should be for when problems arise, how to get replacements off ebay, etc.
But that’s not the right problem. There isn’t a problem with the devices, the problem is the devices. They should be replaced. Their functionality, while maybe novel when they were purchased, is readily available elsewhere. There are industry standards in place, and with good reason.
But this brings up further problems. What about the things that rely on the particular way those devices work? How can we reconfigure them to use the new way. Uhmm… I think you know where I am going with this.
Take the time. Make your coffee well so that you can enjoy it. If you are having an accute caffeine fit, well that’s another problem, fix that one instead. Bad coffee is hurting us all.
People still use NIS+?
Keep reading and think about that last line. This means you.