On Thu, Jun 5, 2008 at 2:27 PM, Pawel Jakub Dawidek <[EMAIL PROTECTED]> wrote: > On Thu, Jun 05, 2008 at 01:53:37AM +0800, Tz-Huan Huang wrote: >> On Thu, Jun 5, 2008 at 12:31 AM, Dag-Erling Sm??rgrav <[EMAIL PROTECTED]> >> wrote: > I'm don't think the panics are related to pool size. More to the load > and characteristics of your workload.
I see. Our server exports all zfs filesytem via nfs to other 10 machines, which run the svm (http://en.wikipedia.org/wiki/Support_vector_machine) day and night to classify the video data ... > If we're comparing who has bigger... :) > > beast:root:~# zpool list > NAME SIZE USED AVAIL CAP HEALTH ALTROOT > tank 732G 604G 128G 82% ONLINE - > > but: > > beast:root:~# zfs list | wc -l > 1932 > > No panics. > > PS. I'm quite sure the ZFS version I've in perforce will fix most if not > all 'kmem_map too small' panics. It's not yet committed, but I do want > to MFC it into RELENG_7. That's great news! Thanks, Tz-Huan _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
