What Tony said: "Uh....yeah."
Leave a comment of what Tony would have liked to have said!
Yesterday morning I grabbed the 2.2 litre polycarbonate water bottle my wife gave me to ensure I drink plenty of water at work and began my trek to one of the further water fountains, as it is the coolest, and has the highest arc - required for filling bottles! As I was 3/4 done this largish woman stands behind me with an empty glass in her hand. I say, "2.2 liters, 70 second to fill, and I'm 75% done." She replies, "You know, there is a sink down the hall."
What I said: "Thank you."
Leave a comment of what I should have said!
There was an accident in Fort Worth at approximately 2200 last night. The driver apparently hit, or caused to be knocked down, a pole. This particular pole was a power pole and knocked power out of more than a block. Our building lost power. Our generator kicked in as it was supposed to, but the battery the generator feeds, failed. Every server went down. I've been bringing them up one at a time. I got here late today, even. My boss had most of the important ones up bright and early. "Monitor every box we back up!" He tells me. So....some workstations on users desks are powered off and they're gone for the holiday weekend and the doors are locked. You're thinking, "Brilliant," right? What a pain in my balls this is:
Added bb start script to v480e, launched blade11, couldn't get access to blade1 so removed it from monitoring, fixed blade31, fixed callie, fsck'd blade9, fixed top on ncgcasm01, added bb startup to blade2502, updated vmewdevweb's bb start script...
Leaving for Kansas in three hours. It looks like a stormfront is going to cover I-35 from Dallas to Wichita. Fantastic.
Updated every package on my primary Solaris box at the ADC, quark.xirr.com <-- this took forever too!
docs.sun.com: If a system fails power-on diagnostics, then auto-boot? is ignored and the system does not boot unless the user does it manually. This behavior is obviously not acceptable for a degraded boot scenario, so the Enterprise 250 OBP provides a second NVRAM‐controlled switch called auto-boot-on-error?. This switch controls whether the system will attempt a degraded boot when a subsystem failure is detected. Both the auto-boot? and auto-boot-on-error? switches must be set to true to enable a degraded boot.
So on my last system, a v100, I get the error, "bad inode number 0 to ginode" when I fsck. Same error when I do a superblock fsck. Sun says, "Contact your service provider or another qualified person." WTF? It appears irreparably damaged. So I call a qualified person, Steve Price who, after laughing, explains that I have to low-level format this ATA drive, replace the standard Sun cable with an 80-pin, and restore the data. Fortunately, it's mirrored, so after I pull the drive to format it, I'll whing-ding the sync and may still get outta here on time! Thanks Steve. Still, I don't understand if its a missing inode on a mirrored filesystem, which drive do I pull...and how is resyncing going to fix it? I think I'll just start pulling drives.