Date: Sun, 4 Jun 2006 19:27:49 +1000 From: Peter Jeremy <peterjeremy@optushome.com.au> To: "Matthew D. Fuller" <fullermd@over-yonder.net> Cc: current@freebsd.org Subject: Re: Resolved: nmount() issues Message-ID: <20060604092749.GE713@turion.vk2pj.dyndns.org> In-Reply-To: <20060604083725.GD76919@over-yonder.net> References: <20060108070915.GA98507@over-yonder.net> <20060604083725.GD76919@over-yonder.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060604092749.GE713>