-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23 Nov, 2008, at 01:05 , Pawel Jakub Dawidek wrote: > On Fri, Nov 21, 2008 at 05:25:18PM +0100, Pawel Jakub Dawidek wrote: >> On Wed, Nov 19, 2008 at 01:58:49PM +0200, Nikolay Denev wrote: >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> >>> On 19 Nov, 2008, at 11:48 , Nikolay Denev wrote: >>>> >>>> Well, it looks like that on -current and a 4G amd64 machine >>>> probably >>>> there is no need >>>> to tune anything. Here are my defaults with everything vm and zfs >>>> related in loader.conf commented : >>>> >>>> vm.kmem_size_max: 4509713203 >>>> vfs.zfs.arc_max: 863907840 >>>> >>> >>> I was able to panic it again with "kmem_map too small" with these >>> settings (defaults). >>> >>> This are the bonnie++ arguments that i've used: >>> bonnie++ -d /tank -c 4 -r 4096 -x 9999999 -u 0:0 >> >> I wasn't able to panic my test machine running this command on i386 >> machine with this in /boot/loader.conf: >> >> vm.kmem_size=1073741824 >> vm.kmem_size_max=1073741824 >> >> (1GB) >> >> Although I now found that you were trying raidz2 and I had two two- >> way >> mirrors. I'm retrying now. > > Ok, I tried RAIDZ2 on top of five disks - no panics. > > -- > Pawel Jakub Dawidek http://www.wheel.pl > pjd_at_FreeBSD.org http://www.FreeBSD.org > FreeBSD committer Am I Evil? Yes, I Am! My test machine is still running the bonnie++ loop that i've started on friday, with only vfs.zfs.arc_max=512M in loader.conf. Seems pretty stable. I'll retry just one more time without the vfs.zfs.arc_max tunable to see if it's going to panic again. - -- Regards, Nikolay Denev -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (Darwin) iEYEARECAAYFAkkqc3EACgkQHNAJ/fLbfrn3uQCeIBwfLIRYcA1/BaR8mxAy5yX0 pW4AoIhH93PIUhTN+cnqTXMHJY0OnAoU =KpHs -----END PGP SIGNATURE-----Received on Mon Nov 24 2008 - 08:27:19 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:38 UTC