Hi, We have generate a Script with the following prozedere:
https://lists.ovirt.org/pipermail/users/2017-August/083665.html Hosted-storage will be not touched. Br Marcel Am 5. Mai 2021 10:40:25 MESZ schrieb Yedidyah Bar David <[email protected]>: >On Wed, May 5, 2021 at 10:59 AM marcel d'heureuse <[email protected]> >wrote: >> >> Hi, >> >> Sorry, haven't write it. Yes it is a self hosted engine. >> >> Br >> Marcel >> >> Am 5. Mai 2021 07:42:35 MESZ schrieb Yedidyah Bar David ><[email protected]>: >>> >>> On Wed, May 5, 2021 at 8:32 AM marcel d'heureuse ><[email protected]> wrote: >>>> >>>> >>>> Hi, >>>> >>>> We shutdown the complete ovirt system, if a poweroutage occurs and >we don't want to make an hard power off. >>>> >>>> So we stop all vms, put the storages in maintenance and shut down >the engine, disconnect storages and shut down the nodes. > >Can you please provide more details? > >Do you follow some existing procedure/document? > >Why do you put storage to maintenance? > >Do you also put the hosted_storage domain to maintenance? If so, this >can explain your fs corruption. If you have valid reasons to put all >other storage to maintenance, perhaps filter out this one. > >You might want to also check this, although I do not know of many >people that use it: > >https://github.com/oVirt/ovirt-ansible-collection/tree/master/roles/shutdown_env > >Best regards, > >>>> >>>> On power up, sometimes it works fine but in some cases the engine >need a xfs_repair session to start. >>>> >>>> What we make wrong? Have you an idea? >>> >>> >>> Is this a hosted-engine? Or standalone? >>> >>> Best regards, > > > >-- >Didi
_______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected]/message/LZBYZJYF7BAZRPNZM5CIBGEL33KFKLWK/
