No, the edge was running and we have crashed the engine with reboot hard or setup a server with the same IP address to see what happens.

all tests will be solved well but the .shred folder of the gluster will be bigger and bigger.

the engine it selve has round 5 GB but the .shred has 60 up to 90 GB.

so I want to let the engine like it is but the .shred folder I want to clean. or will the oldest files delete by gluster and I don't need to do anything?

br
marcel

Am 5. November 2020 22:11:51 MEZ schrieb Strahil Nikolov <hunter86_bg@yahoo.com>:
Well,

cleanup for me means to just mount the volume and delete any data there.
Yet, this means that you are willing to loose the data there and you should do it only if you plan to reuse the volume (for example for redeploying the engine).

Let's summarize . Your engine failed, so you tried to rebuild it from scratch but it is complaining as it has too few space on the volume - right ?

Best Regards,
Strahil Nikolov






В четвъртък, 5 ноември 2020 г., 20:44:48 Гринуич+2, Marcel <marcel@deheureu.se> написа: 






Moin,

Thats sounds interessing. How you can cleanup a gluster volume of the 
hosted engine.

We had an engine running with round 200 VMs on a big systems and every 3 
days we los 1 % of the engine storage. the devices has 150 GB and is a 
replicated over 6 bricks.
as this systems has reached the 90 % of the storage we have decide to 
restart from 0 and have completely rebuild the system..

We have nothing found to clean-up the meta files from the glusterfs.

Thanks
Marcel


------ Originalnachricht ------
Von: "Strahil Nikolov via Users" <users@ovirt.org>
An: "users@ovirt.org" <users@ovirt.org>; "hjadavalluva@ukaachen.de" 
<hjadavalluva@ukaachen.de>
Gesendet: 05.11.2020 17:10:35
Betreff: [ovirt-users] Re: Issue with ovirt self hosted engine 
instalaltion 4.4

The engine volume has to be cleaned up .
Here is mine:


[root@ovirt1 ~]# df -h /rhev/data-center/mnt/glusterSD/gluster1\:_engine/
Filesystem        Size  Used Avail Use% Mounted on
gluster1:/engine  100G  19G  82G  19% /rhev/data-center/mnt/glusterSD/gluster1:_engine

It seems that https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_command_line/#hardware-requirements_SHE_cli_deploy clearly states that 25G is enough.

Best Regards,
Strahil Nikolov










В четвъртък, 5 ноември 2020 г., 15:44:19 Гринуич+2, hjadavalluva@ukaachen.de <hjadavalluva@ukaachen.de> написа:





Dear Mr.Strahil Nikolov,

Thank you once again!

"cleanup the share and extend it to 65G ? "- You mean in target server (where the ovirt gets installed)? if so, the target server is in production side (but now its in testing side to test the ovirt deployment) so this needs to be cleaned up?


Best Reagrds,

Hariharan
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/3KQXNNAORQ7ZZN2KMLMA3FSFZYQYR2K7/

Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/QBGH255AZDLRXS5XBHV5QLP5CJGCJDDH/