Due to the unfortunate ability of the SATABeast to receive and process requests on all four controllers, failing the NFS array over to the second controller makes no discernible difference to the host: it can still talk to c0, alas.
So the only way we’re going to test this is with some brutal combination of FC zone modification and/or controller shutdown.
This is looking better. Note in the previous post, the scsi_vhci.conf entry conforms to the scsi_inquiry format: that is, eight characters are used for the vendor ID (NEXSAN followed by two spaces), with the product ID appended.
Now the scsi devices appear under /devices/scsi_vhci. However, cfgadm still only shows the first path (ie, the first controller) as configured for each SATABeast; “cfgadm -c configure c4″ still fails.
Read the rest of this entry »
Looks like multipathing via the generic scsi_vhci may be possible. Thus far:
Add this to /kernel/drv/scsi_vhci.conf:
device-type-scsi-options-list = "NEXSAN SATABeast", "symmetric-option";
symmetric-option = 0x1000000;
Currently cfgadm -c configure c4 is failing, complaining about being unable to create device nodes.
Having said that, the single-pathed zpool create Just Works.
Work progresses…
/* Not true */
/* verbs */
/* Skip over this string; it’s too short */
/* Do the fork */
/* Sending text */
/* Do nothing */
/* Heh heh */
/* Call me again if you’ve anything in mind */
/* Not true */
/* There _won’t_ be circular refs */
/* val_deref(VALUE*targ); (targ becomes 0) */
/* String space ————————————————————*/
/* There had better not be any instances */
/* Global variables */
/* This brings together all the scanner bits */
/* Pop something off the stack */
/* It’s a variable */
Abandoning Elgg for the following reasons:
1. It’s very clunky.
2. It took me an hour to figure out how to do something that should be trivial.
3. Every time I go looking to find out why something’s broken, I find more bugs.
It still is sluggish, but see http://elgg.org/mod/vanillaforum/vanilla/comments.php?D
I’ve disabled the explodeping module, we’ll see if this goes any faster now.
This’ll need (a) configuring, and (b) integrating with Elgg. At the moment, it’s simply available to apache instances.
… at the moment, it’ll claim to be from me. This uses the php.ini in the mod-php/conf directory, which means that it can be done separately from the tomcat/Quercus- hosted instance.
“You’ve forgotten your password” etc. stuff looks like it works.
I’ve opened up the top-level apache instance a bit to let users on the 12 subnet see this (although I’ve not advertised it at all).
It seems to me to be very sluggish. I’ve not turned on any PHP speedups; looks like they’ll be necessary, however.
Next obvious question: if people are emitting a series of blog posts with various tags,
1. do those tags show up i a tag cloud somewhere?
2. can views be presented onto a blog stream filtering by keyword?