Path: utzoo!utgpu!watmath!clyde!att!ucbvax!husc6!rice!sun-spots-request From: dieter@titan.nmt.edu Newsgroups: comp.sys.sun Subject: bit rot! Message-ID: <8811222354.AA20642@titan.nmt.edu> Date: 3 Dec 88 17:19:23 GMT Sender: usenet@rice.edu Organization: Rice University, Houston, Texas Lines: 24 Approved: Sun-Spots@rice.edu Original-Date: Tue, 22 Nov 88 16:54:19 MST X-Sun-Spots-Digest: Volume 7, Issue 35, message 4 of 18 The symptoms: We've been noticing that /lib/ccom on one of our 3/280s (titan) will start core dumping almost instantly upon start up. Doing a "diff" with the same file on our other 3/280 (jupiter) doesn't report any problems. Once it starts happening, the odds of getting a successful compile rapidly approach zero. If we rcp /lib/ccom from jupiter, everything works again. This seems to recur on about a 6 month cycle. /lib/ccom has only died on titan, never on jupiter. The questions: Does this sound like a familiar problem to anyone? If so, anyone have a fix? BTW, the inode number for /lib/ccom is 79. Ideas? Dieter Muller -- dieter%nmt@relay.cs.net dieter@jupiter.nmt.edu [[ I like the machine's name! :-) --wnl ]]