Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.hawaii.edu!ames!agate!howland.reston.ans.net!gatech!newsfeed.internetmci.com!mr.net!winternet.com!news.minn.net!mpp.minn.net!mpp From: mpp@mpp.minn.net (Mike Pritchard) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: panic : ufs_lock Date: 11 Mar 96 01:02:43 GMT Organization: Minn Net Lines: 39 Message-ID: <mpp.826506163@mpp.minn.net> References: <4hnml5$3ca@news.fsu.edu> <4hp639$31f@bell.maths.tcd.ie> <4hue90$1ca@uriah.heep.sax.de> NNTP-Posting-Host: mpp.minn.net X-Newsreader: NN version 6.5.0 #1 (NOV) In <4hue90$1ca@uriah.heep.sax.de> j@uriah.heep.sax.de (J Wunsch) writes: >dwmalone@maths.tcd.ie (David Malone) writes: >> zateslo@geomag.gly.fsu.edu (Ted Zateslo) writes: >> >> >> >panic : ufs_lock: recursive lock not expected pid: xxx >> >> >where "xxx" is some pid. I don't know what process was running >> >to cause this. The system reboots after the message comes up. Any >> >ideas? Thanks. >> >> I've produced this crash by doing "mount /directory /directory". Its >> been submitted as a problem report, though I don't know if there is >> a fix. >Do you mean a fix for your pilot error? :-) >Somebody has been fixing mount(8) today to not accept two identical >names for mount device and mount point. The actual fix in the kernel >is more complicated. >-- >cheers, J"org That somebody is me :-). As a temporary fix, I changed mount(8) to not accept the same pathname for the special device file and the mount point (e.g. mount /mnt /mnt) for those file systems types that are broken. That list currently is: ufs, msdos, cd9660. The correct kernel fix is waiting on some planned reworking of the file system code. At that point I'll remove the kludge fix in mount(8) and fix the kernel mount call the right way. -Mike -- Mike Pritchard The Dart Shop - Darts & Supplies mpp@minn.net "Go that way. Really fast. If something gets in your way, turn"