Remove Sensei swap

[Nikotine]

Does anyone know how to remove the swap that Sensei created?
I had a situation last week where it used up all my RAM.
Now that I've fixed that issue, how do I remove the swap?



Should I remove these files, or the whole folder?

Code: [Select]

root@opnsense:~ # df -h
Filesystem         Size    Used   Avail Capacity  Mounted on
/dev/gpt/rootfs     13G    6.9G    5.5G    56%    /
devfs              1.0K    1.0K      0B   100%    /dev
fdescfs            1.0K    1.0K      0B   100%    /dev/fd
procfs             4.0K    4.0K      0B   100%    /proc
devfs              1.0K    1.0K      0B   100%    /var/dhcpd/dev
devfs              1.0K    1.0K      0B   100%    /var/unbound/dev
/dev/md43           48M     56K     44M     0%    /usr/local/sensei/output/active/temp

[athurdent]

Looks like a memory device.
https://www.freebsd.org/cgi/man.cgi?query=mdconfig&apropos=0&sektion=8&manpath=FreeBSD+13.0-RELEASE+and+Ports&arch=default&format=html

[sy]

Hi @Nikotine,

It is a temporary Ramdisk that Zenarmor writes IPDR files and just 50 MB. It just uses max. 50 MB of Ram.

[Nikotine]

Hi @sy,
Temporary, but persistent after a reboot.
I know it doesn't harm that it's there, just... nice if it were gone 

[dinguz]

The Sensei swap area is created at install time, and so has always been there; you probably just didn't notice it before. As it is supposed to be there, I would suggest not trying to delete it ;-)

[sy]

Hi Nikotine,

I mean Zenarmor uses it for temporary purpose. IPDR files are created there then removes after streamed to the DB. It is creating during installation.

[Nikotine]

Oh ok, I really thought it wasn't there until I made that mistake.
Must not have noticed it then before.

[benyamin]

I'd say the memory disk is most likely a malloc backed device created every time Sensei starts.

If the files on the memory disk hold potentially sensitive information they will not survive system halt and cannot be recovered. Also, if data in files on the memory disk are corrupted or contain an exploit or malware, a process stop or panic will delete them when the device is recreated, and a system panic or restart will likely delete them upon halt.

Best to leave it be methinks. 

@Nikotine, you might want to post a link to this topic in the other thread so people coming across it can benefit from the expertise on this board.

[sy]

Hi @benyamin,

There are just last seconds IPDR data in this memory disk. They are injected to the DB then the engine writes new ones. So if anything happens to be able to lose data, it will be just the last seconds' session info. The reason to use mem disk is to prevent intensive I/O operations on the disk.

[benyamin]

Yep, faster than most disk too... 

[athurdent]

Hi @benyamin,

There are just last seconds IPDR data in this memory disk. They are injected to the DB then the engine writes new ones. So if anything happens to be able to lose data, it will be just the last seconds' session info. The reason to use mem disk is to prevent intensive I/O operations on the disk.

Nice, thank you for the insight! 👍