And also I found several parts in den rel-notes talking about PostgreSQL should also be patched to 24.4. But there is no option to path it to this version. My current version is

Please first run a top and check if btrfs is there with 100 % load. then please run a df -h and check if the disk space is occupied because of snapshots.
In our company there is no issue, not even the one described here.

Hi,

first: I just went back to snapshot prior patch and with this 24.3.1 I'm able to manage shares again.

space available status is good /root 16GB, vastorage 72GB

Top shows most time java

I remember that there was a problem with btrfs and sles in the past ( didnt remember exactly ) but seems already fixed here

What'sthe version of PostgreSQL on your system?

same

 rpm -qa | grep -i  postgres
postgresql13-llvmjit-13.16-150200.5.61.1.x86_64
postgresql15-contrib-15.8-150200.5.30.1.x86_64
postgresql14-contrib-14.13-150200.5.47.1.x86_64
postgresql-jdbc-42.2.25-150400.3.12.1.noarch
postgresql-llvmjit-16-150400.4.12.1.noarch
postgresql15-15.8-150200.5.30.1.x86_64
postgresql13-13.16-150200.5.61.1.x86_64
postgresql14-14.13-150200.5.47.1.x86_64
postgresql15-server-15.8-150200.5.30.1.x86_64
postgresql13-server-13.16-150200.5.61.1.x86_64
postgresql-16-150400.4.12.1.noarch
postgresql-contrib-16-150400.4.12.1.noarch
postgresql14-server-14.13-150200.5.47.1.x86_64
vamodule-postgresql-2.2.1.3-150400.2.4.1.noarch
postgresql-server-16-150400.4.12.1.noarch

how much RAM for the VM and how much for Java ?

16 GB in / may be too little for an all-in-one DB migration. At least 2 times DB size is required

VM:64 Java 47

The Postgres version in our system is 15.8, the release notes speak of 15.7 and 16.3

the Java heap size could be a little too high for the VM's memory. I can have a look tomorrow in documents that I don't have to hand at the moment

sorry, not 47, it's 42