*BSD News Article 63268


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!zombie.ncsc.mil!news.mathworks.com!fu-berlin.de!zrz.TU-Berlin.DE!cs.tu-berlin.de!uni-erlangen.de!news.tu-chemnitz.de!narses.hrz.tu-chemnitz.de!irz401!uriah.heep!news
From: j@uriah.heep.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: panic : ufs_lock
Date: 10 Mar 1996 11:26:24 GMT
Organization: Private BSD site, Dresden
Lines: 26
Message-ID: <4hue90$1ca@uriah.heep.sax.de>
References: <4hnml5$3ca@news.fsu.edu> <4hp639$31f@bell.maths.tcd.ie>
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.3

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

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. ;-)