<div dir="auto">Thanks for Your detailed answare. But before new linstor version this mixing goes without error. I was successfully migrate or sync volumes between this servers. Can e turn off this feature temporary for one or more volume/resource?</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jan 31, 2024, 5:16 PM Gábor Hernádi <<a href="mailto:gabor.hernadi@linbit.com">gabor.hernadi@linbit.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="ltr"><div>Hello Zsolt,</div><div><br></div><div>LINSTOR's storage pool mixing has 2 criteria. If one is fulfilled, you have a mixed storage pool setup:</div><div>1) Different extent sizes (this is what I mentioned in the previous email with "mixing LVM with ZFS", since LVM by default has 4M extent size and ZFS has 8k).</div><div>2) Mixing thin and thick storage pools. <br></div><div><br></div><div>Thin and thick storage pools have different initial DRBD-sync behavior (full sync vs day0-based partial sync). Mixing thin and thick forces all thin volumes to act as thick volumes (forever, even if you delete all the thick-resources of the resource-definition and are only left with thin resources).</div><div><br></div><div>So to answer your question: Mixing ZFS and ZFS_THIN is indeed considered storage pool mixing.<br></div></div><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Best regards,<br></div>Gabor Hernadi<br></div></div></div></div></div>
</blockquote></div>