From owner-freebsd-hackers Wed Aug 12 00:32:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA09731 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 00:32:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gw-nl1.philips.com (gw-nl1.philips.com [192.68.44.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA09711 for ; Wed, 12 Aug 1998 00:32:36 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl1.philips.com with ESMTP id JAA22393 for ; Wed, 12 Aug 1998 09:32:10 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.8.5/8.6.10-1.2.2m-970826) with SMTP id JAA25850 for ; Wed, 12 Aug 1998 09:32:10 +0200 (MET DST) Received: (qmail 4276 invoked by uid 666); 12 Aug 1998 07:30:08 -0000 Message-ID: <19980812093008.A4232@hal.mpn.cp.philips.com> Date: Wed, 12 Aug 1998 09:30:08 +0200 From: Jos Backus To: Tor.Egge@fast.no Cc: hackers@FreeBSD.ORG Subject: Re: system shitdown using mount References: <199806101453.QAA09941@pat.idi.ntnu.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199806101453.QAA09941@pat.idi.ntnu.no>; from Tor.Egge@fast.no on Wed, Jun 10, 1998 at 04:53:44PM +0200 X-Files: The Truth is out there! Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Tor, all, On Wed, Jun 10, 1998 at 04:53:44PM +0200, Tor.Egge@fast.no wrote: > /mnt was locked while ffs_mount tried to lookup /mnt/foo. This probably > caused a panic in ufs_lock, since a recursive lock on /mnt was not expected. > > This behavior is also present in 3.0-CURRENT. I'm using the following > patch (for 3.0-CURRENT), after having made a similar mistake with > the mount command (I forgot to specify the '-t null' option). [patch elided] I am trying to move my FreeBSD partition from sd1 to sd0. Before applying this patch, when creating the slice and labeling and newfsing it using sysinstall the system would die with a 'locking against myself' type panic. Upon inspection the slice definition would be OK but the label would be invalid (I tried this using a boot floppy, too). Therefore I wasn't able to proceed any further with the migration. However, after applying this patch, the label at least survives the ensuing 'vrele: negative ref cnt' panic (sys/kern/vfs_subr.c(1348))), and while the filesystems apparently aren't set up properly (fsck complains about a bad magic number in the superblock), I can newfs the partitions without problems. So it looks like I will be able to migrate to sd0 after all *grin* Of course, I guess the panic happening is Bad Thing. If there's anything I can do to help fix this problem, please let me know. I can summon it at will :) In the meantime, thank you for the patch! Groetjes, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message