> Has the place you're getting the odd EBADF errors been created after > you deleted the former mystery? Probably yes (fsdb didn't give me the birth time, but ctime and mtime are identical and later than the last fsck/deletion of the missing-dot/dotdot dirctory.
> I'm wondering if perhaps it got the same inode or the same disk block > or some such. No. The directory that twice caused a panic because of missing dot/dotdot was inode 463357837, the one with the two entries pointing to unallocated inodes is inode 158304666, the two unallocated inodes being 158304792 and 158304678.