ZFS on AMD64 - any recent crashes?
ender at enderzone.com
Sun Jan 6 14:14:16 PST 2008
Ivan Voras wrote:
> In light of the recent discussion about ZFS stability, does anyone
> still have kmem_map_too_small panics on AMD64 after tuning it (as
> presented in http://wiki.freebsd.org/ZFSTuningGuide)?
> I'm interested in reports like this:
> (note that this report is for an untuned system).
I have vm.kmem_size="1073741824"
I used to have vm.kmem_size_max=1073741824 as well but heard it was not
needed to have both. (it made no change)
I never see my vfs.numvnodes over 60,000 but i have the limit at 400,000
FreeBSD 7.0-BETA4 #0: Sat Dec 15 06:40:09 EST 2007
graff at nfsd.com:/usr/obj/usr/src/sys/NFSD
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Dual-Core AMD Opteron(tm) Processor 2218 (2593.52-MHz K8-class CPU)
Origin = "AuthenticAMD" Id = 0x40f12 Stepping = 2
Cores per package: 2
usable memory = 8580689920 (8183 MB)
avail memory = 8257769472 (7875 MB)
ACPI APIC Table: <091107 APIC1523>
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
All this server does is run nfsd, no apache, no mysql, no rsync, no zfs
Jan 1 15:48:09 nfsd kernel: ZFS filesystem version 6
Jan 1 15:48:09 nfsd kernel: ZFS storage pool version 6
Jan 1 15:48:09 nfsd savecore: reboot after panic: kmem_malloc(131072):
kmem_map too small: 864546816 total allocated
In fact i was going to paste the zpool status here, but typing it in
caused the server to crash. In short i have 4 drives paired in 2
mirrors, for a raid 0 + 1 effect, normal SATA drives directly connected
I have tested this hardware thoroughly without zfs, memory test, make
buildworld tests, etc so i know it is stable hardware.
I hate to report bad news but i hope this leads to a fix
More information about the freebsd-current