loader.conf settings appear not to work.

[joshland]

We are using an older system for holding disk to disk backups of our SQL databases. The load is minimal. We increased RAM to 2GB, and tried to tune the vm.kmem_size, but nothing seems to work.

I have followed as many threads as I can, and I cannot see the problem.


Here is my loader.conf

#
# Boot loader file for FreeNAS. This relies on a hacked beastie.4th.
#
autoboot_delay="2"
loader_logo="freenas"
#Fix booting from USB device bug
kern.cam.boot_delay=10000
vm.kmem_size_max="1536M"
vm.kmem_size="1024M"


# GEOM support
geom_mirror_load="YES"
geom_stripe_load="YES"
geom_raid3_load="YES"
#geom_raid5_load="YES"
ntfs_load="YES"
smbfs_load="YES"

Here is the relevent line from /boot/defaults/loader.conf

loader_conf_files="/boot/device.hints /boot/loader.conf /boot/loader.conf.local"

Here is the output from sysctl:

[joshua@backup ~]$ sysctl -a|grep kmem_size
vm.kmem_size_scale: 3
vm.kmem_size_max: 335544320
vm.kmem_size_min: 0
vm.kmem_size: 335544320

I just upgraded to 8.0.1-RC1. It was the only disk I had on hand and I had to reinstall because of a boot-disk failure. Can anyone give me some guidance?

 

[Durkatlon]

Which version are you running: i386 or amd64 ?

 

[joshland]

i386, sorry.

 

[Durkatlon]

On i386 you will not be able to tweak kmem to the extend you are trying. In fact I'm surprised you're not getting "suballoc failure" during boot with the settings you picked.

The maximum safe kmem_size and kmem_size_max settings for i386 are 512M. If you want more you will need to build a custom kernel with "options KVA_PAGES=512" set in the kernel config.

I have the same problem you do and I've been trying to play with building a custom version from scratch for a while off and on. The last few days I'm having all kinds of problems though, but I think they're on my end.

 

[matthewowen01]

if your cpu supports 64 bit, run 64 bit.

what kind do you have?