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). _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"