Duncan
Cadet
- Joined
- Nov 22, 2014
- Messages
- 3
I work in a particularly large AD environment, and the local user/group cache created by FreeNAS fills the full 2GB that is allocated by default for the /var/tmp/.cache memdisk.
Now, I can stop Directory Services, delete the memdisk using mdconfig, create a larger one, and restart directory servers; similar to what is mentioned in the following ticket: https://bugs.freenas.org/issues/991. However, this is a volatile change, and will be lost on reboot.
My question is, is there a permanent way to resize the memdisk allocated for /var/tmp/.cache, or a safe way to redirect it to a pool, that won't get randomly murdered due to it not being stored in the configuration database?
/var has a file in /conf/base/var/md_size that controls the memdisk size for /var, but I could find no such file for /var/tmp/.cache.
Code:
[root@freenas-test01 ~]# du -ach /var/tmp/.cache/ 512B /var/tmp/.cache/.snap 154M /var/tmp/.cache/.samba/gencache.tdb 512B /var/tmp/.cache/.samba/browse.dat 164k /var/tmp/.cache/.samba/netsamlogon_cache.tdb 154M /var/tmp/.cache/.samba 8.0k /var/tmp/.cache/.query/__db.001 12k /var/tmp/.cache/.query/__db.002 12k /var/tmp/.cache/.query/__db.003 12k /var/tmp/.cache/.query/__db.004 152k /var/tmp/.cache/.query/.cache.db 196k /var/tmp/.cache/.query 8.0k /var/tmp/.cache/.ldap/.activedirectory/.local/.users/UA/__db.001 12k /var/tmp/.cache/.ldap/.activedirectory/.local/.users/UA/__db.002 12k /var/tmp/.cache/.ldap/.activedirectory/.local/.users/UA/__db.003 12k /var/tmp/.cache/.ldap/.activedirectory/.local/.users/UA/__db.004 71M /var/tmp/.cache/.ldap/.activedirectory/.local/.users/UA/.cache.db 71M /var/tmp/.cache/.ldap/.activedirectory/.local/.users/UA 71M /var/tmp/.cache/.ldap/.activedirectory/.local/.users 0B /var/tmp/.cache/.ldap/.activedirectory/.local/.groups/UA/__db.001 512B /var/tmp/.cache/.ldap/.activedirectory/.local/.groups/UA 1.0k /var/tmp/.cache/.ldap/.activedirectory/.local/.groups 71M /var/tmp/.cache/.ldap/.activedirectory/.local 8.0k /var/tmp/.cache/.ldap/.activedirectory/.users/UA/__db.001 12k /var/tmp/.cache/.ldap/.activedirectory/.users/UA/__db.002 12k /var/tmp/.cache/.ldap/.activedirectory/.users/UA/__db.003 12k /var/tmp/.cache/.ldap/.activedirectory/.users/UA/__db.004 1.7G /var/tmp/.cache/.ldap/.activedirectory/.users/UA/.cache.db 1.7G /var/tmp/.cache/.ldap/.activedirectory/.users/UA 1.7G /var/tmp/.cache/.ldap/.activedirectory/.users 1.7G /var/tmp/.cache/.ldap/.activedirectory 1.7G /var/tmp/.cache/.ldap 1.9G /var/tmp/.cache/ 1.9G total
Code:
[root@freenas-test01 ~]# df -h /dev/md3 1.9G 1.9G -153M 109% /var/tmp/.cache
Now, I can stop Directory Services, delete the memdisk using mdconfig, create a larger one, and restart directory servers; similar to what is mentioned in the following ticket: https://bugs.freenas.org/issues/991. However, this is a volatile change, and will be lost on reboot.
My question is, is there a permanent way to resize the memdisk allocated for /var/tmp/.cache, or a safe way to redirect it to a pool, that won't get randomly murdered due to it not being stored in the configuration database?
/var has a file in /conf/base/var/md_size that controls the memdisk size for /var, but I could find no such file for /var/tmp/.cache.
Code:
[root@freenas-test01 ~]# find / -name 'md_size' /etc/md_size /mnt/md_size /var/md_size /conf/base/var/md_size /conf/base/etc/md_size /conf/base/mnt/md_size
