>Last week, we experienced an extended power failure that crashed our
>HP 9000/817 running HPUX 8.02. When power returned and the system rebooted,
>fsck detected corruption in the root file system. Needless to say, I was not
>amused. This was my first corruption after about 1 year as a sysadmin. After
>devouring several manuals and my class notes from my HP sysadmin class, I was
>able to run fsck manually, answer it's questions intelligently (I hope), and
>check the lost+found directories for important missing files.
>My gripe is this: the brittleness of the Unix filesystem and the complexity of
>the recovery process is unacceptable for a mission-critical production
>environment. Come on! Corruption preventing reboot after a power failure???
should have an option (at least our SGI systems do) to automatically fsck(1)
the filesystems upon reboot. It's easy to slam Unix if you configure it
In spite of the configuration error, this is a good idea anyway.Quote:>Sheesh. And the recovery process asks some rather scary questions pertaining
>to data integrity. There's no way a typical computer-room operator is going
>to be able to do this. Highly skilled Technical Support personnel (me) must
>be in control. And what about those lost+found directories? You have to have
>extensive knowledge about what's going on in your system to re-unite the
>I-node named orphaned files with their original locations. In a large
>production system with gigabytes of files, this could be impossible!
>I think I'm going to recommend to Management that they invest in some UPS
>systems that will keep our Unix systems alive long enough during power
>failures so they can be shutdown in a clean manner...
>OS has a very robust Transaction Manager (XM) to insure data integrity. It sure
>would be nice to have an XM-level of integrity under HPUX. Can anybody at
>HP comment if HPUX will have better filesystem integrity in the future?
>IMHO, HPUX is never going to make it in the Real World of mission critical
>applications without some serious enhancement...
>Coast Community College District 1370 Adams Avenue
>District Information Services Costa Mesa, CA, USA 92626
>Technical Support (714) 432-5064
>"You can tune a file system, but you can't tune a fish." - tunefs(1M)
Georgia State University (404) 651-2648 ksh: matter: cannot create
Wells Computer Center $