Tue, 3 Apr 2007

Aphids & Immune Systems

— SjG @ 1:23 pm

The lupine in the front yard is tall and happy, with vast swaths of blue and blue-white flowers.

In one corner, however, closest to the street and driveway, a few plants have been overwhelmed by aphids. Not just your usual annoying aphids, the kinds you find attacking your roses, but massive, evil, green aphids that are larger than half the children that wander our neighborhood streets.

“So where are the aphid predators?” you may ask. Well, there are lots of ladybugs. But while they’re all hanging out in the lupine, the majority of the ladybugs seem much more interested in mating than eating.

Dr. Weil has a model for medicine and the human system, which can be summarized as

  • Our immune system keeps us healthy by keeping a homeostatic equilibrium.
  • When the immune system gets seriously overwhelmed by something, it cannot maintain equilibrium, which manifests as chronic sickness.
  • Medical intervention should attempt to mitigate whatever is overwhelming the immune system, so it can succeed in its task of maintaining equilibrium.

In other words, the medicine doesn’t cure us, it balances things to the point where we can cure ourselves.

So what does this have to do with aphids? My theory is that the garden as a whole resembles a semihomeostatic organism under attack. Or rather, that I needed to restore an equilibrium where the predators were numerous enough to fight off the aphid plague. The predators were doing the population increase part themselves. It was up to me to reduce the plague population. So it was don the gloves, and go a-squishin’.

After fifteen minutes, vast gouts of green liquid flowed down my arms. It was a bleak day in aphid-dom.

That was two days ago. Today, there are twice as many ladybugs on the lupine, and the aphid population is smaller. It remains to be seen if equilibrium has been restored.

Filed in:

Mon, 2 Apr 2007

Buffalo Terastation Problems

— SjG @ 4:20 pm

I’ve written here numerous dull tirades on the subject of backups. Well, here’s more.

We had my brand new shiny backup script working on the LAN to backup all the servers to a Linux box with a 300GB hard drive. For extra security, we copied it out to a Buffalo Terastation, which also serves as our office fileserver. For that extra bit of security, the Terastation is formatted as two shares, each of 250GB (using RAID-1). One of those shares is the office fileshare, the other is for server backups.

Well, there was a slight *cough* stupid *cough* problem with one of my backup scripts over a weekend, which resulted in a recursive backup of a directory (doh!). This filled up the disk on the Linux box, but it didn’t prevent it from happily trying to copy it all to the Terastation (using lftp).

When I came in on Monday, the Terastation was not happy. It simultaneously said the drives were ~30% full, and said that it couldn’t find any disks at all. FTP connections were dropped immediately. We were able to copy a few files off of it from machines that had kept the drive mounted via SMB, but then it would disconnect and vanish from that machine’s network visibility. This was not good. At some point, we thought it might be a good idea to try enabling another protocol to access the data, which had the unfortunate side effect of switching the Teraserver admin into Japanese.

Tech support took about 20 minutes to answer the call, but they were courteous and helpful. Eventually, they concluded that the controller board was bad. To get a replacement, they charged our credit card the price of a new unit, and shipped it out, with the understanding that we’d swap the drives into the new unit, send back the old one, and get credited back the money. While this is not ideal, I can understand why they do it that way.

In any case, the new unit arrived today. I went through the effort of swapping the drives from one unit to the other (which is a lot more complicated than it should be, requiring a lot of screws). And voila! Still a Japanese admin, and no ability to access the data.

My working theory now is that the Teraserver stores configuration data on the drives, and when the one share filled up, it corrupted the config data somehow. I’ll call tech support tomorrow and see what I can learn. *sigh*