After a severe crash one of my alpha 3000/300's running OSF/1 v2.0 choked
coming back up with errors about the dump file not having enough space
and to run "rcmgr set SAVECORE_FLAGS M". So far so good, I could get
back up to multiuser mode but I kept getting errors on boot about a partial
dump not being able to be saved. I blew away the adm/crash files but,
alas, to no avail... How can I clean the crash/dump info to avoid this
attempted recovery?
But! thats not my problem! This occurred after a long winded install and
customizing of Unigraphics software (which incidently triggered the crash
somehow when accessed from another node) so I immediately ran a dump of the
modified file system and got the following errors...
dump: Dumping from host ucad1.uccb.ns.ca
dump: Date of this level 0 dump: Wed Apr 27 14:04:12 1994 ADT
dump: Date of last level 0 dump: the start of the epoch
dump: Dumping /dev/rrz0g (/usr) to /dev/nrmt0h
dump: Mapping (Pass I) [regular files]
dump: Corrupted directory, i-node: 2
Terminated
# dump: SIGTERM received -- Try rewriting
dump: Unexpected signal -- cannot recover
dump: The ENTIRE dump is aborted
I tried cloning the /usr to another disk with tar but apparently dragged the
garbage with it. Well, I'm ready for one more trip to the dump... Any
suggestions on how I might recover? fsck didn't help. Any advice will be
very appreciated!
Brian McMahon, CAD/CAM System Analyst | voice: (902)539-5300
UCCB CAD/CAM Center | fax: (902)562-0119
P.O. Box 5300 | mcmahon_at_cad.uccb.ns.ca
Sydney, Nova Scotia |
Canada, B1P 6L2 |
Received on Thu Apr 27 1995 - 13:58:37 NZST