On Thu, Feb 3, 2022 at 2:48 PM Ayansh Rocks <shashank123rastogi@gmail.com> wrote:
Do I need to clean it from every host which has the hosted engine ? Sinc the other host still can see it.
Are you sure it's reading the same space? Perhaps there is some misconfiguration or something? Caching?
On Thu, Feb 3, 2022 at 6:02 PM Ayansh Rocks <shashank123rastogi@gmail.com> wrote:
Hi Yedidyah,
Thanks, After cleaning it from one host i am getting below error messages on /var/log/messages
Feb 3 18:01:02 iondelsvr14 vdsm[11893]: ERROR Malformed metadata for host 3: received 0 of 512 expected bytes Feb 3 18:01:03 iondelsvr14 vdsm[11893]: ERROR Malformed metadata for host 3: received 0 of 512 expected bytes Feb 3 18:01:03 iondelsvr14 vdsm[11893]: ERROR Malformed metadata for host 3: received 0 of 512 expected bytes Feb 3 18:01:03 iondelsvr14 vdsm[11893]: ERROR Malformed metadata for host 3: received 0 of 512 expected bytes Feb 3 18:01:13 iondelsvr14 vdsm[11893]: ERROR Malformed metadata for host 3: received 0 of 512 expected bytes Feb 3 18:01:13 iondelsvr14 vdsm[11893]: ERROR Malformed metadata for host 3: received 0 of 512 expected bytes Feb 3 18:01:17 iondelsvr14 vdsm[11893]: ERROR Malformed metadata for host 3: received 0 of 512 expected bytes Feb 3 18:01:18 iondelsvr14 vdsm[11893]: ERROR Malformed metadata for host 3: received 0 of 512 expected bytes Feb 3 18:01:23 iondelsvr14 vdsm[11893]: ERROR Malformed metadata for host 3: received 0 of 512 expected bytes Feb 3 18:01:23 iondelsvr14 vdsm[11893]: ERROR Malformed metadata for host 3: received 0 of 512 expected bytes
Not sure. Perhaps try to restart the ha broker, agent or both. If you do this in global maintenance, I think it should be safe - wait until everything looks ok before exiting global maint. Check also vdsm and ha logs. Good luck and best regards, -- Didi