From owner-freebsd-current@FreeBSD.ORG Sun Jun 4 09:27:52 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 7A76416A4D4 for ; Sun, 4 Jun 2006 09:27:52 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail12.syd.optusnet.com.au (mail12.syd.optusnet.com.au [211.29.132.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id D4C3743D46 for ; Sun, 4 Jun 2006 09:27:51 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail12.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k549RnGv016360 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 4 Jun 2006 19:27:50 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.6/8.13.6) with ESMTP id k549Rn3C004938; Sun, 4 Jun 2006 19:27:49 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.6/8.13.6/Submit) id k549RnEL004937; Sun, 4 Jun 2006 19:27:49 +1000 (EST) (envelope-from peter) Date: Sun, 4 Jun 2006 19:27:49 +1000 From: Peter Jeremy To: "Matthew D. Fuller" Message-ID: <20060604092749.GE713@turion.vk2pj.dyndns.org> References: <20060108070915.GA98507@over-yonder.net> <20060604083725.GD76919@over-yonder.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060604083725.GD76919@over-yonder.net> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 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:27:54 -0000 On Sun, 2006-Jun-04 03:37:26 -0500, Matthew D. Fuller wrote: >And so it was. Strangely, if I unmounted the filesystems that >wouldn't mount -u, delete the dir they're mounted over, and recreated >it, they picked back up and worked just peachy. If the system had been up, I would have suggested that the vnode entry for the covered directory have been corrupted somehow but that wouldn't have survived a reboot. 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. 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. -- Peter Jeremy