Posts

• RE: QCOW2 support on XOSTOR

  @TestForEcho No ETA for now. Even before supporting QCOW2 on LINSTOR, we have several points to robustify (HA performance, potential race conditions, etc.). Regarding other important points:

  • Supporting volumes larger than 2TB has significant impacts on synchronization, RAM usage, coalesce, etc. We need to find a way to cope with these changes.
  • The coalesce algorithm should be changed to no longer depend on the write speed to the SR in order to prevent potential coalesce interruptions; this is even more crucial for LINSTOR.
  • The coalesce behavior is not exactly the same for QCOW2, and we believe that currently this could negatively impact the API impl in the case of LINSTOR.

  In short: QCOW2 has led to changes that require a long-term investment in several topics before even considering supporting this format on XOSTOR.

  posted in XOSTOR

  R

  ronan-a
  
• RE: XOSTOR hyperconvergence preview

  @henri9813 said in XOSTOR hyperconvergence preview:

  of course, i checked, my SR was not full

  The visual representation of used space is for informational purposes only; it's an approximation that takes into account replication, disks in use, etc. For more information: https://docs.xcp-ng.org/xostor/#how-a-linstor-sr-capacity-is-calculated

  We plan to display a complete view of each physical disk space on each host someday to provide a more detailed overview. In any case, if you use "lvs"/"vgs" on each machine, you should indeed see the actual disk space used.

  posted in XOSTOR

  R

  ronan-a
  
• RE: SR_BACKEND_FAILURE_78 when trying to create VDI

  @cmanos No problem, glad I could helped.
  As Olivier also pointed above, it's not an issue anymore when using QCOW2 which is currently in beta, so hopefully it's only a short workaround

  posted in Management

  D

  dthenot