misc/129174: [nfs][zfs][panic] NFS v3 Panic when under high load
exporting ZFS file system
Weldon Godfrey
wgodfrey at ena.com
Tue Nov 25 05:30:02 PST 2008
>Number: 129174
>Category: misc
>Synopsis: [nfs][zfs][panic] NFS v3 Panic when under high load exporting ZFS file system
>Confidential: no
>Severity: critical
>Priority: low
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Tue Nov 25 13:30:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator: Weldon Godfrey
>Release: FreeBSD 7.1-PREPREASE (also happens under 8-CURRENT and 7.x)
>Organization:
ENA
>Environment:
FreeBSD store1.mail.ena.net 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #2: Thu Nov 20 10:41:36 CST 2008 root at store1.mail.ena.net:/usr/obj/usr/src/sys/GENERIC amd64
>Description:
This issue was origionally reported under another ticket that turned out to be unrelated. I am using 2 IBM EXP 3000 SAS Chasis with a total of 24 300GB 25K SAS drives using a 3ware 9690SE-8 controller on a Dell Poweredge 2950-iii with 2x4core Intel 2.5GHz CPU and 16GB of RAM. I am testing by running 9 instances of Postmark from Centos 5.2 x86_64 (was 3.x i386) NFS clients. I can run 1 on 9 machines or all on 1 machine, after about 2-4 hrs of running the benchmark, the system panics and reboots. From help with the freebsd-fs group, it was determined that the vnode is becoming invalid. I have tried several things including using FreeBSD 8-CURRENT and the ZFS v11 patch but nothing helps except if I force to use NFS v2, so it appears this is a bug with the v3 code.
This is my loader.conf, the commented out section are values I have tried but do not have an effect:
vm.kmem_size_max="16106127360"
vm.kmem_size="1073741824"
kern.maxvnodes="800000"
#vfs.zfs.debug="1"
#vfs.zfs.zil_disable="1"
#vfs.zfs.prefetch_disable="1"
#vfs.zfs.vdev.cache.bshift="13"
the raid is configured RAID 10, each chasis is one side of the mirror (the 1st 11 drives of each chasis, the final one of each is marked as spare).
>How-To-Repeat:
run multiple instances of postmark benchmark using NFS v3 from NFS clients for several hours.
>Fix:
workaround: don't use NFS v3, use -2 option with mountd.
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-bugs
mailing list