/var/db/system utilization and recover space

psoni

Dabbler
Joined
Mar 5, 2019
Messages
13
Hello,

We are intermittently seeing /var/db/system path full.

The sub-directory that's taking up the space is configs-f1ae6c68bbe041c7bb38cadeec088781

System is currently running FreeNAS-11.0-U4 (54848d13b)
There are previous builds listed under configs-f1ae6c68bbe041c7bb38cadeec088781 (see below).

Is it safe to delete those files to free up space?
Is there anything else I can do to prevent this from happening in the future?


root@freenas:~ # df -h
Filesystem Size Used Avail Capacity Mounted on
freenas-boot/ROOT/11.0-U4 2.9G 754M 2.2G 25% /
devfs 1.0K 1.0K 0B 100% /dev
tmpfs 32M 9.4M 23M 30% /etc
tmpfs 4.0M 8.0K 4.0M 0% /mnt
tmpfs 4.0G 195M 3.8G 5% /var
freenas-boot/grub 2.2G 6.3M 2.2G 0% /boot/grub
fdescfs 1.0K 1.0K 0B 100% /dev/fd
freenas 21T 21T 17M 100% /mnt/freenas
freenas/jails 17M 53K 17M 0% /mnt/freenas/jails
freenas/.system 467M 450M 17M 96% /var/db/system
freenas/.system/cores 30M 13M 17M 44% /var/db/system/cores
freenas/.system/samba4 23M 5.8M 17M 26% /var/db/system/samba4
freenas/.system/syslog-f1ae6c68bbe041c7bb38cadeec088781 23M 6.4M 17M 28% /var/db/system/syslog-f1ae6c68bbe041c7bb38cadeec088781
freenas/.system/rrd-f1ae6c68bbe041c7bb38cadeec088781 17M 54K 17M 0% /var/db/system/rrd-f1ae6c68bbe041c7bb38cadeec088781
freenas/.system/configs-f1ae6c68bbe041c7bb38cadeec088781 192M 175M 17M 91% /var/db/system/configs-f1ae6c68bbe041c7bb38cadeec088781
root@freenas:~ #

root@freenas:/var/db/system/configs-f1ae6c68bbe041c7bb38cadeec088781 # ls -al
total 51
drwxr-xr-x 6 root wheel 6 Sep 29 2017 .
drwxr-xr-x 9 root wheel 11 Jun 1 03:54 ..
drwxr-xr-x 2 root wheel 50 Sep 28 2017 FreeNAS-11.0-U2 (e417d8aa5)
drwxr-xr-x 2 root wheel 1672 Jun 6 03:45 FreeNAS-11.0-U4 (54848d13b)
drwxr-xr-x 2 root wheel 91 Nov 23 2016 FreeNAS-9.10.1 (d989edd)
drwxr-xr-x 2 root wheel 262 Aug 11 2017 FreeNAS-9.10.1-U4 (ec9a7d3)

root@freenas:/var/db/system/configs-f1ae6c68bbe041c7bb38cadeec088781 #
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
Is there anything else I can do to prevent this from happening in the future?
It looks like you've got a quota on your .system dataset, which isn't normally the case. What's the output of zfs get quota freenas/.system?

Edit: as a side note, you're running a very old version of FreeNAS that's long since EOL--the last 11.1 release is five years old, and yours is older than that. It's recommended to run the most current version, or at least a recent version, to make sure you have the latest security updates.
 

psoni

Dabbler
Joined
Mar 5, 2019
Messages
13
I don't see any quota on the system.

root@freenas:~ # zfs get quota freenas/.system
NAME PROPERTY VALUE SOURCE
freenas/.system quota none default
root@freenas:~ #
 

psoni

Dabbler
Joined
Mar 5, 2019
Messages
13
It looks like you've got a quota on your .system dataset, which isn't normally the case. What's the output of zfs get quota freenas/.system?

Edit: as a side note, you're running a very old version of FreeNAS that's long since EOL--the last 11.1 release is five years old, and yours is older than that. It's recommended to run the most current version, or at least a recent version, to make sure you have the latest security updates.
I don't see any quota on the system


root@freenas:~ # zfs get quota freenas/.system
NAME PROPERTY VALUE SOURCE
freenas/.system quota none default
root@freenas:~ #
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
OK, taking a bit closer of a look at it (code tags would really have helped)... You've got a pool of 21 TB that's (almost) completely full. The .system dataset, in total, is consuming 450 MB. It isn't your problem, and I'm a little confused why you would have thought it was. Yes, you can safely delete the directories for older releases you're talking about (they're backups of the config databases from when you were using those versions), but the configs-(foo) dataset is only taking 175 MB--that's less than 0.01% of the space your pool is using. You need to free, minimally, about 4 TB, or you need to expand the pool.

Delete the old config files if you like, but your problem is elsewhere.
 
Top