Quote:
Originally Posted by
hedkandi
..dont get me started on the 1st level support guy whom renamed a system to a single numeric value of "2" His excuse was that he wasn't aware what uname -S does in UNIX..last I checked he's still there
Well, in my last project i had such a colleague too: Once, the storage guy (also an AIX expert) wanted to do some performance tests. He created an empty LUN, imported it as hdisk device and wrote to this device directly using
dd. His point was to not let the file system drivers mess up his measurement.
So far, so logical and absolutely correct. Now, enter the idiot: he saw what the storage guy did and us discussing the results. Three days later a productive system broke with some strange errors and was unable to boot again. The disks in the rootvg were damaged to an extent that even the PVID and the LVCB (partition information) were missing. It transpired, that he did "performance tests" too. But because he didn't really understand what the storage guy was doing, he didn't get himself a new and empty disk for that, but used the system disk to overwrite the first physical GB with hexadecimal zeros. Well, the disk was mirrored and the system would have survived that - but doing thorough work he did it on the second system disk too. Guess what happens, when both copies of a mirrored disk are destroyed.
We
would have been able to restore the system pretty quickly using an mksysb from our central NIM server - unfortunately he had used not only the production system but this very system, our centralized software repository for all the AIX systems - for his "performance tests" too (along with a couple of other systems, but we found that out later). Most systems boot only very slowly from nulled out boot disks....
This guy is there in in systems administration for more then ten years now and this was not even the first time he did something this idiotic. Go figure.
bakunin