Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!spool.mu.edu!newspump.sol.net!www.nntp.primenet.com!nntp.primenet.com!howland.erols.net!news.mathworks.com!news.sgi.com!olivea!quack!quack.kfu.com!nsayer From: nsayer@quack.kfu.com (Nick Sayer) Subject: Strange root fs corruption ? Message-ID: <nA8MX3a@quack.kfu.com> Sender: news@quack.kfu.com (0000-News(0000)) Organization: The Duck Pond public unix, +1 408 249 9630, log in as guest. Date: Thu, 3 Oct 1996 21:47:49 UTC Lines: 29 I have a Gateway P-Pro 200 with root on an EIDE disk along with a DOS partition and Solaris 2.x. I am reinstalling 2.2-960801-SNAP on the SCSI drive because for the second time since I installed it all the root fs has taken a monsterous hit of some sort. I can't really describe it very well, except that everything was fine, I did a reboot and when it came back it couldn't find /bin/sh anymore. Booting with fixit and doing an fsck -n shows symptoms almost as if the inode table had been overwritten with crud -- lots of disconnected inodes, stuff like that. The first time it happened I sort of blamed it on cosmic rays or something. The second time... Well, it's not just a coincidence anymore. On other occasions, playing with both the DOS partition and the FreeBSD one at the same time has led to bizzare sorts of file corruption, but fscking afterwards (and I mean _real_ fsck, not just -p) has not shown any big problems. I have 3 other FreeBSD machines that I play with. All run 960801 and all are fine, so I don't think I can blame the OS for this, unless it's an EIDE-PPro sort of thing. Is it just me or has anyone else seen anything strange like this? -- Nick Sayer <nsayer@quack.kfu.com> | "Say, Stimpy, what's that on your N6QQQ @ N0ARY.#NORCAL.CA.USA.NOAM | tongue?" +1 408 249 9630, log in as 'guest' | -- Ren URL: http://www.kfu.com/~nsayer/ |