Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!uunet!in3.uu.net!144.212.100.12!news.mathworks.com!fu-berlin.de!irz401!orion.sax.de!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: panic doing "dump" on /usr to st0(8mm) Date: 27 Dec 1996 16:53:54 GMT Organization: Private BSD site, Dresden Lines: 20 Message-ID: <5a0uv2$df1@uriah.heep.sax.de> References: <596umn$jeg@cronkite.cisco.com> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.6 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:33294 fty@cisco.com (Frank Terhaar-Yonkers) wrote: > The system is coming up with some totally bogus value for bp->b_bcount .. > This happens in single-user mode and is repeatable every time. > Is the filesystem corrupt? It fsck-s cleanly ... It looks as if the fs were corrupt. If you can figure out the i-node number, you might try if you could correct this with fsdb. The disk driver should probably be more careful, or the interface to the bounce buffers be changed so that vm_bounce_alloc() could return an error status, which in turn aborts the attempted transfer, instead of panicing. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)