On Tue, Aug 10, 2021 at 7:19 AM Gilboa Davara <[email protected]> wrote: > > > On Mon, Aug 9, 2021 at 4:13 PM Gilboa Davara <[email protected]> wrote: >> >> >> >> On Mon, Aug 9, 2021 at 2:46 PM Yedidyah Bar David <[email protected]> wrote: >>> >>> On Mon, Aug 9, 2021 at 1:56 PM Gilboa Davara <[email protected]> wrote: >>> > >>> > >>> > >>> > On Mon, Aug 9, 2021 at 12:16 PM Gilboa Davara <[email protected]> wrote: >>> >> >>> >> Hello, >>> >> >>> >> On Mon, Aug 9, 2021 at 11:50 AM Yedidyah Bar David <[email protected]> >>> >> wrote: >>> >>> >>> >>> On Mon, Aug 9, 2021 at 11:43 AM Strahil Nikolov via Users >>> >>> <[email protected]> wrote: >>> >>> > >>> >>> > Corrupted metadata is the problem you see. >>> >>> > >>> >>> > I think there was a command to fix it, but I can't recall it right >>> >>> > now. >>> >>> >>> >>> I think you refer to 'hosted-engine --clean_metadata'. Gilboa - I >>> >>> suggest to search the net/archives for docs/mentions/discussions of >>> >>> this option - it's rather drastic. Good luck. >>> >>> >>> >>> That said, I must say that if your metadata is corrupted, I wonder >>> >>> what else is - so would continue using this setup with great care. >>> >>> Ideally restore from backups, after testing/replacing the hardware. >>> >>> >>> >>> Best regards, >>> >>> >>> >> >>> >> Thanks for the pointer. >>> >> This is a side setup that's about to replaced by a real setup (3 host >>> >> Gluster). >>> >> That said, beyond the corrupted meta data, everything else seems to be >>> >> working just fine, host boot just fine, RAID sync showed no issues. XFS >>> >> partitions mounted OK, etc. >>> >> The only thing that seems damaged is the hosted engine meta data. >>> >> >>> >> I'll test it and report back. >>> >> >>> >> - Gilboa >>> >> >>> > >>> > >>> > Stupid question: >>> > Won't clean meta data remove the host from the "cluster" and given the >>> > fact that its a single host configuration, require a clean redploy? >>> >>> It's not stupid. >>> >>> Generally speaking, the metadata is populated by the HA daemons >>> themselves, not something "external". If a specific host's entry is >>> missing, they should write it. >>> >> >> OK. Thanks again for the prompt answer. >> >> - Gilboa > > > Sadly enough, it seems that --clean-metadata requires an active agent. > E.g. > $ hosted-engine --clean-metadata > The hosted engine configuration has not been retrieved from shared storage. > Please ensure that ovirt-ha-agent > is running and the storage server is reachable.
Did you try to search the net/list archives? > > Can I manually delete the metadata state files? Yes, see e.g.: https://lists.ovirt.org/pipermail/users/2016-April/072676.html As an alternative to the 'find' command there, you can also find the IDs with: $ grep metadata /etc/ovirt-hosted-engine/hosted-engine.conf 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/P53KOF24SBCIPMQ2QVKP6UN2TU45U2NP/
