Is /var/log on ZFS or tmpfs after applying exisiting 2.5.2 config?
-
I wonder whether there is a slight problem migrating a 2.5.2 configuration to the new zfs and handling of /var/log.
I did a fresh install of 2.6.0 on my backup unit, and loaded the existing configuration from production (2.5.2).
During the first boot there was this error message:'/var/log': not a ZFS filesystem
but it is listed with 'zfs list':
pfSense/var/log 112K 11.0G 112K /var/log
df -h /var /var/log shows both on tmpfs (no separate mount for /var/log)
tmpfs 200M 47M 153M 24% /var tmpfs 200M 47M 153M 24% /var
but 'mount' shows:
pfSense/var/log on /var/log (zfs, local, noatime, noexec, nosuid, nfsv4acls) tmpfs on /var (tmpfs, local)
so, where is it?
My existing configuration specified a memory file system for /tmp and /var.is a ramdisk for /var no longer recommended?
-
I think the mount entries is processed according to the order. So the tmpfs mounted at /var at a lower position masks (or overlay) the zfs /var/log. The system is actually using tmpfs for the whole /var.
-
J jimp moved this topic from Problems Installing or Upgrading pfSense Software on
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.