Erro zfs
-
Lock 4 in 4 hours, to the internet, and I have to restart to work, someone help me put the pfsense has two days in the air.
pfsense 2.1.5 amd64
HP Proliant DL360 G5 sas hd 4 gb memory 2 processors
follows the loader.conf file and dmesg.boot to have a better definition
10mega link connections and 200 captive portalerror:
ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is present;
to enable, add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf.
ZFS WARNING: Recommended minimum kmem_size is 512MB; expect unstable behavior.
Consider tuning vm.kmem_size and vm.kmem_size_max
in /boot/loader.conf.
ZFS filesystem version 5
ZFS storage pool version 28![erro vfs.jpg](/public/imported_attachments/1/erro vfs.jpg)
![erro vfs.jpg_thumb](/public/imported_attachments/1/erro vfs.jpg_thumb)
loaderconf.txt
dmesgboot.txt -
ZFS is not fully active in pfSense so those messages are safe to ignore.
-
I just did a fresh install of 2.1.5 (full install) to an mSATA SSD on an APU1C4 system and am getting those same ZFS messages. I understand they are safe to ignore (not having the OP's problem, yet) but I was wondering if we should follow the advice of the warning messages and add the vfs.zfs.prefetch_disable="0" as well as tweaking the vm.kmem_size and vm.kmem_size_max in loader.conf ?
-
I just did a fresh install of 2.1.5 (full install) to an mSATA SSD on an APU1C4 system and am getting those same ZFS messages. I understand they are safe to ignore (not having the OP's problem, yet) but I was wondering if we should follow the advice of the warning messages and add the vfs.zfs.prefetch_disable="0" as well as tweaking the vm.kmem_size and vm.kmem_size_max in loader.conf ?
No.