Resolved: nmount() issues
Peter Jeremy
peterjeremy at optushome.com.au
Sun Jun 4 09:27:54 UTC 2006
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
More information about the freebsd-current
mailing list