# SUSE Trento Server: filesystem sizing

**URL:** <https://forums.suse.com/t/suse-trento-server-filesystem-sizing/43770>\
**Category:** SLES SAP Applications\
**Created:** [August 1, 2024, 3:21pm UTC](https://forums.suse.com/t/suse-trento-server-filesystem-sizing/43770 "2024-08-01T15:21:11Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![davide.poletto](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/davide.poletto/32/11440_2.png) [@davide.poletto](https://forums.suse.com/u/davide.poletto)\
**Post date:** [August 1, 2024, 3:21pm UTC](https://forums.suse.com/t/suse-trento-server-filesystem-sizing/43770/1 "2024-08-01T15:21:11Z")

</div>

Hi all, I’m looking for any advice about **how to correctly size** a production VM’s disk subsystem (_mostly reasoning about an additional data disk and its relevant mountpoint(s) sizing_) dedicated to host the **SUSE Trento** application installed manually via RPM (so no Docker but as a regular systemd stack) as per GitHub instructions [here](https://github.com/trento-project/docs/blob/main/guides/manual-installation.md).

Apart the below sentence on the official documentation available [here](https://documentation.suse.com/sles-sap/trento/html/SLES-SAP-trento/index.html):

“_Trento is powered by event driven technology. Registered events are stored in a PostgreSQL database with a retention period of 10 days. For each host registered with Trento, you need to allocate at least 1.5GB of space in the PostgreSQL database._”

which is relevant to the PostgreSQL sizing (and so, I suppose, it also refers to /var/lib/pgsql/ path which is the default location for the data directory), I’m not able to find other specific suggestions, if any.

Any advice is really appreciated! Thank you!

---

<div class="post-metadata">

**Author:** ![stefanotorresi](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/stefanotorresi/32/11803_2.png) [@stefanotorresi](https://forums.suse.com/u/stefanotorresi)\
**Post date:** [December 13, 2024, 10:42am UTC](https://forums.suse.com/t/suse-trento-server-filesystem-sizing/43770/2 "2024-12-13T10:42:24Z")

</div>

Hey there!

Other than the significant PostgreSQL storage requirement, there are no other specific suggestions that we could preventively identify so far, so you can assume generic recommendations for a SLES system.

---

<div class="post-metadata">

**Author:** ![davide.poletto](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/davide.poletto/32/11440_2.png) [@davide.poletto](https://forums.suse.com/u/davide.poletto)\
**Post date:** [December 13, 2024, 11:37am UTC](https://forums.suse.com/t/suse-trento-server-filesystem-sizing/43770/3 "2024-12-13T11:37:55Z")

</div>

Ciao/Hi Stefano! yep, in the end I deployed the SUSE Trento 2.3.2 (not yet updated to 2.4.0…) in systemd mode with this filesystems partitioning scheme, nothing too fancy:

```auto
trento:~ # lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 32G 0 disk 
├─sda1 8:1 0 512M 0 part /boot/efi
└─sda2 8:2 0 31.5G 0 part 
  └─system-root 254:0 0 31.5G 0 lvm /
sdb 8:16 0 16G 0 disk 
└─sdb1 8:17 0 16G 0 part 
  └─data-pgsql 254:1 0 16G 0 lvm /var/lib/pgsql/data
sr0 11:0 1 13.5G 0 rom  

trento:~ # df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 4.0M 0 4.0M 0% /dev
tmpfs 7.9G 1.1M 7.9G 1% /dev/shm
tmpfs 3.2G 305M 2.9G 10% /run
tmpfs 4.0M 0 4.0M 0% /sys/fs/cgroup
/dev/mapper/system-root 32G 4.0G 28G 13% /
/dev/sda1 511M 5.0M 507M 1% /boot/efi
/dev/mapper/data-pgsql 16G 4.9G 12G 31% /var/lib/pgsql/data
tmpfs 1.6G 0 1.6G 0% /run/user/1000

trento:~ # pvs
  PV VG Fmt Attr PSize PFree
  /dev/sda2 system lvm2 a-- 31.50g 0 
  /dev/sdb1 data lvm2 a-- 16.00g 0 

trento:~ # vgs
  VG #PV #LV #SN Attr VSize VFree
  data 1 1 0 wz--n- 16.00g 0 
  system 1 1 0 wz--n- 31.50g 0 

trento:~ # lvs
  LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
  pgsql data -wi-ao---- 16.00g                                                    
  root system -wi-ao---- 31.50g                                                    

```

and it is running quite well.

The above just as future reference for anyone that will may have my very same doubts (YMMV).

Using LVM and assigning a LV to /var/lib/pgsql/data to a dedicated disk (sdb) on which VG data and LV pgsql are defined will let us to accomodate any future extension related to PostgreSQL used space, if required.

Actually we are in test mode so, sadly, we added just one SUSE Trento Agent only.

Cheers, Davide.