Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!europa.clark.net!dispatch.news.demon.net!demon!baron.netcom.net.uk!netcom.net.uk!news.clara.net!not-for-mail From: steve@clara.net (Steve Rawlinson) Newsgroups: comp.unix.bsd.bsdi.misc Subject: bsdi 3.0 kernel panic Date: Mon, 16 Jun 1997 20:57:09 GMT Message-ID: <33a5a669.645802784@news.clara.net> NNTP-Posting-Host: 194.164.41.15 X-Newsreader: Forte Free Agent 1.1/32.230 Lines: 27 Xref: euryale.cc.adfa.oz.au comp.unix.bsd.bsdi.misc:7001 BSD/OS 3.0, I am getting this kernel panic a few times a day: panic: checkblk: bad block -1 panic: lockmgr: locking against myself dumping [...etc] I would be interested to know what the 'checkblk: bad block -1' actually means. FWIW the hardware is a P133, buslogic 958 and 2 IBM wide scsi drives both of which pass diskdefect without problems. I was alarmed to note that you can generate a kernel panic by doing a mount_mfs on a node whose path contains a symlink and I suspect that this panic (though not caused by mount_mfs) is being caused by a script calling a command with come similar problem. Exactly what is hard to guess without knowning what this bad block -1 stuff is about. steve ------ Steve Rawlinson ClaraNet Ltd steve@clara.net 0171 647 1000