2.5.2 System Info still showing multiple /var paths with ufs in ram
-
Did not occur under 2.5.1 and only started after I upgraded to 2.60 dev path.
Can't say if it was introduced in 2.5.2 or 2.60, but as I have downgraded to 2.5.2 it hasn't changed. I have a zfs boot drive and moved tmp to ram.
I have 7x /var ufs in ram
-
Without seeing more details about exactly what you have in the dashboard it's almost certainly normal. 2.5.2 and later make use of more ZFS datasets which the dashboard sees as different filesystems.
And RAM disks are always UFS the way they are setup now, so that's also normal.
-
@gwaitsi see below. as i say, this only started showing multiple /var after i upgraded from 2.5.1 to 2.6.0
image url)
-
@jimp any ideas?
-
That is a bit unusual, what shows up at the CLI if you run
mount
?What about if you run
df -h
?Also, what is in
/etc/fstab
?And finally: What packages do you have installed?
-
@jimp as I say Jim, it was fine under 2.5.1 and only appeared after upgrading to 2.6.0.
From those commands, it appears to be gui specific
Filesystem Size Used Avail Capacity Mounted on pfSense/ROOT/default 27G 831M 26G 3% / devfs 1.0K 1.0K 0B 100% /dev pfSense/cf 26G 96K 26G 0% /cf pfSense 26G 96K 26G 0% /pfSense pfSense/var 26G 3.3M 26G 0% /var pfSense/home 26G 96K 26G 0% /home pfSense/cf/conf 26G 12M 26G 0% /cf/conf pfSense/var/cache 26G 96K 26G 0% /var/cache pfSense/var/tmp 26G 104K 26G 0% /var/tmp pfSense/var/log 26G 6.5M 26G 0% /var/log pfSense/var/empty 26G 96K 26G 0% /var/empty pfSense/var/db 26G 3.2M 26G 0% /var/db /dev/md0 496M 1.0M 455M 0% /tmp /dev/md1 1.9G 198M 1.6G 11% /var devfs 1.0K 1.0K 0B 100% /var/dhcpd/dev
cat fstab # Device Mountpoint FStype Options Dump Pass# /dev/ada0p3 none swap sw 0 0
-
Curious why it's not showing up right on yours, it works as expected here and shows the full ZFS dataset path:
My
df
output looks identical, but my widget has: -
Can you show the output of the following two commands:
-
/bin/df -Tht ufs,zfs,cd9660
-
/bin/df -Tht ufs,zfs,cd9660 | /usr/bin/awk '{print $1, $2, $3, $6, $7;}'
-
-
@jimp said in 2.5.2 System Info still showing multiple /var paths with ufs in ram:
/bin/df -Tht ufs,zfs,cd9660
/bin/df -Tht ufs,zfs,cd9660 Filesystem Type Size Used Avail Capacity Mounted on pfSense/ROOT/default zfs 27G 831M 26G 3% / pfSense/cf zfs 26G 96K 26G 0% /cf pfSense zfs 26G 96K 26G 0% /pfSense /dev/md1 ufs 1.9G 198M 1.6G 11% /var pfSense/home zfs 26G 96K 26G 0% /home pfSense/cf/conf zfs 26G 12M 26G 0% /cf/conf /dev/md1 ufs 1.9G 198M 1.6G 11% /var /dev/md1 ufs 1.9G 198M 1.6G 11% /var /dev/md1 ufs 1.9G 198M 1.6G 11% /var /dev/md1 ufs 1.9G 198M 1.6G 11% /var /dev/md1 ufs 1.9G 198M 1.6G 11% /var /dev/md0 ufs 496M 1.0M 455M 0% /tmp /dev/md1 ufs 1.9G 198M 1.6G 11% /var
/bin/df -Tht ufs,zfs,cd9660 | /usr/bin/awk '{print $1, $2, $3, $6, $7;}' Filesystem Type Size Capacity Mounted pfSense/ROOT/default zfs 27G 3% / pfSense/cf zfs 26G 0% /cf pfSense zfs 26G 0% /pfSense /dev/md1 ufs 1.9G 11% /var pfSense/home zfs 26G 0% /home pfSense/cf/conf zfs 26G 0% /cf/conf /dev/md1 ufs 1.9G 11% /var /dev/md1 ufs 1.9G 11% /var /dev/md1 ufs 1.9G 11% /var /dev/md1 ufs 1.9G 11% /var /dev/md1 ufs 1.9G 11% /var /dev/md0 ufs 496M 0% /tmp /dev/md1 ufs 1.9G 11% /var
-
@jimp sorry, forgot the packages Jim
Cron sysutils 0.3.7_5 Filer sysutils 0.60.6_5 nut sysutils 2.7.4_8 pfBlockerNG-devel net 3.0.0_16 suricata security 6.0.0_11 System_Patches sysutils 1.2_6
-
How about the output of
mount
?It's quite odd that you're seeing that but one of our devs says we've seen it before.
-
@jimp I have tried turning off tmp to ram and back on, but didn't make any difference
mount pfSense/ROOT/default on / (zfs, local, noatime, nfsv4acls) devfs on /dev (devfs, local) pfSense/cf on /cf (zfs, local, noatime, noexec, nosuid, nfsv4acls) pfSense on /pfSense (zfs, local, noatime, nfsv4acls) pfSense/var on /var (zfs, local, noatime, nfsv4acls) pfSense/home on /home (zfs, local, noatime, nfsv4acls) pfSense/cf/conf on /cf/conf (zfs, local, noatime, noexec, nosuid, nfsv4acls) pfSense/var/cache on /var/cache (zfs, local, noatime, noexec, nosuid, nfsv4acls) pfSense/var/tmp on /var/tmp (zfs, local, noatime, nosuid, nfsv4acls) pfSense/var/log on /var/log (zfs, local, noatime, noexec, nosuid, nfsv4acls) pfSense/var/empty on /var/empty (zfs, local, noatime, nfsv4acls) pfSense/var/db on /var/db (zfs, local, noatime, noexec, nosuid, nfsv4acls) /dev/md0 on /tmp (ufs, local) /dev/md1 on /var (ufs, local) devfs on /var/dhcpd/dev (devfs, local)
-
I was able to reproduce it here easily with a fresh ZFS VM and RAM disks.
It looks to be like a problem with
df -t <type>
unfortunately.The full list is OK:
: df -Th Filesystem Type Size Used Avail Capacity Mounted on pfSense/ROOT/default zfs 29G 670M 28G 2% / devfs devfs 1.0K 1.0K 0B 100% /dev pfSense/cf zfs 28G 96K 28G 0% /cf pfSense/var zfs 28G 3.2M 28G 0% /var pfSense/home zfs 28G 96K 28G 0% /home pfSense zfs 28G 96K 28G 0% /pfSense pfSense/cf/conf zfs 28G 616K 28G 0% /cf/conf pfSense/var/log zfs 28G 188K 28G 0% /var/log pfSense/var/empty zfs 28G 96K 28G 0% /var/empty pfSense/var/cache zfs 28G 96K 28G 0% /var/cache pfSense/var/db zfs 28G 1.1M 28G 0% /var/db pfSense/var/tmp zfs 28G 104K 28G 0% /var/tmp /dev/md0 ufs 38M 76K 35M 0% /tmp /dev/md1 ufs 58M 9.5M 44M 18% /var devfs devfs 1.0K 1.0K 0B 100% /var/dhcpd/dev
Filtering to just UFS is OK:
: df -Tht ufs Filesystem Type Size Used Avail Capacity Mounted on /dev/md0 ufs 38M 76K 35M 0% /tmp /dev/md1 ufs 58M 9.5M 44M 18% /var
Trying to filter just ZFS gets the wrong info about
/var
:: df -Tht zfs Filesystem Type Size Used Avail Capacity Mounted on pfSense/ROOT/default zfs 29G 670M 28G 2% / pfSense/cf zfs 28G 96K 28G 0% /cf /dev/md1 ufs 58M 9.5M 44M 18% /var pfSense/home zfs 28G 96K 28G 0% /home pfSense zfs 28G 96K 28G 0% /pfSense pfSense/cf/conf zfs 28G 616K 28G 0% /cf/conf /dev/md1 ufs 58M 9.5M 44M 18% /var /dev/md1 ufs 58M 9.5M 44M 18% /var /dev/md1 ufs 58M 9.5M 44M 18% /var /dev/md1 ufs 58M 9.5M 44M 18% /var /dev/md1 ufs 58M 9.5M 44M 18% /var
I'll work on a Redmine for it, not sure if it's something we can fix and push upstream or will have to wait for a FreeBSD fix on.
-
@jimp as always, brilliant. thanks Jim
-
Added in Redmine here:
-
@jimp thanks jim