From owner-freebsd-current@FreeBSD.ORG Sun Jun 4 09:34:39 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F61016A4CF for ; Sun, 4 Jun 2006 09:34:39 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from mail.localelinks.com (web.localelinks.com [64.39.75.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id C524543D46 for ; Sun, 4 Jun 2006 09:34:38 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-072-148-013-213.sip.jan.bellsouth.net [72.148.13.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localelinks.com (Postfix) with ESMTP id 12EEA3E1; Sun, 4 Jun 2006 04:34:38 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id 46C5C61C32; Sun, 4 Jun 2006 04:34:37 -0500 (CDT) Date: Sun, 4 Jun 2006 04:34:37 -0500 From: "Matthew D. Fuller" To: Peter Jeremy Message-ID: <20060604093437.GE76919@over-yonder.net> References: <20060108070915.GA98507@over-yonder.net> <20060604083725.GD76919@over-yonder.net> <20060604092749.GE713@turion.vk2pj.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060604092749.GE713@turion.vk2pj.dyndns.org> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.11-fullermd.3 Cc: current@freebsd.org Subject: Re: Resolved: nmount() issues X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jun 2006 09:34:40 -0000 On Sun, Jun 04, 2006 at 07:27:49PM +1000 I heard the voice of Peter Jeremy, and lo! it spake thus: > > I don't suppose you tried doing an ls on the directory or creating a > file in it or fscking the filesystem before deleting it. I did ls the directory, and it worked. The filesystems all went through numberous full fsck's on both the Jan and Jun -CURRENT's without a hint of trouble. > Do you happen to know if the directories were re-created with the > same inode number? Maybe you hit a bug that depends on the inode or > block number of the directory. That, I don't know, but there were 3 of them on /usr (/usr/src, /usr/obj, and /usr/ports all had the trouble), so I'm a little doubful that three of those inodes/blocks that happened to be mountpoints went wonky. /usr/local kept working just fine, though. It's pretty wacky. At least it's wacky and in the past now; having to unmount and remount all the time instead of just mount -u'ing was driving me battier. 8-} -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.