L2Arc settings not honoured from loader.conf?
Posted: 17 Jan 2014 13:25
Hi, I'm using an L2Arc with the Full version of N4F (9.2....925 build).
What i'd like to do is apply the following settings in my loader.conf so that the l2arc is populated more quickly than default:
However, the values are not honoured. Running sysctl -a | grep l2arc shows that the values are just their defaults of 8MB.
I've also tried in sysctl.conf with the same results (though I think it does need to be loader.conf).
Any ideas? The other settings in loader.conf are applied successfully. The entire file is here:
Thanks
edit:
is there a log for loader/loader.conf ? regarding this part of the man page:
What i'd like to do is apply the following settings in my loader.conf so that the l2arc is populated more quickly than default:
Code: Select all
vfs.zfs.l2arc_noprefetch="0"
vfs.zfs.l2arc_write_max="26214400"
vfs.zfs.l2arc_write_boost="52428800"
vfs.zfs.l2arc_feed_min_ms="100"I've also tried in sysctl.conf with the same results (though I think it does need to be loader.conf).
Any ideas? The other settings in loader.conf are applied successfully. The entire file is here:
Code: Select all
kernel="kernel"
bootfile="kernel"
kernel_options=""
kern.hz="100"
hw.est.msr_info="0"
hw.hptrr.attach_generic="0"
kern.maxfiles="65536"
kern.maxfilesperproc="50000"
kern.cam.boot_delay="8000"
autoboot_delay="5"
isboot_load="YES"
zfs_load="YES"
# ZFS kernel tune
#vm.kmem_size="31744M"
vm.kmem_size="65536M"
vfs.zfs.arc_min="4096M"
vfs.zfs.arc_max="26624M"
vfs.zfs.prefetch_disable="0"
vfs.zfs.txg.timeout="5"
#vfs.zfs.vdev.max_pending="10"
#vfs.zfs.vdev.min_pending="4"
vfs.zfs.vdev.max_pending="1"
vfs.zfs.vdev.min_pending="1"
vfs.zfs.write_limit_override="0"
vfs.zfs.no_write_throttle="0"
ahci_load="YES"
vfs.zfs.l2arc_noprefetch="0"
vfs.zfs.l2arc_write_max="26214400"
vfs.zfs.l2arc_write_boost="52428800"
vfs.zfs.l2arc_feed_min_ms="100"
edit:
is there a log for loader/loader.conf ? regarding this part of the man page:
BUGS
The loader(8) stops reading loader.conf when it encounters a syntax
error, so any options which are vital for booting a particular system
(i.e. ``hw.ata.ata_dma=0'') should precede any experimental additions to
loader.conf.