I reported this yesterday on freebsd-fs. Reducing kern.maxvnodes to about 3/4th its current value gets rid of this panic. See Pawel's response to my message on freebsd-fs list (assuming it has shown up by now).