DRBD version 9.2.5, but version 9.2.7 (or higher) is required

Gábor Hernádi gabor.hernadi at linbit.com
Mon Feb 5 12:16:39 CET 2024


You are correct, this is a bug that was introduced recently. We will fix
that in the next release.

On Wed, Jan 31, 2024 at 6:38 PM Zsolt Baji <bajizs at gmail.com> wrote:

> 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?
>
> On Wed, Jan 31, 2024, 5:16 PM Gábor Hernádi <gabor.hernadi at linbit.com>
> wrote:
>
>> Hello Zsolt,
>>
>> LINSTOR's storage pool mixing has 2 criteria. If one is fulfilled, you
>> have a mixed storage pool setup:
>> 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).
>> 2) Mixing thin and thick storage pools.
>>
>> 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).
>>
>> So to answer your question: Mixing ZFS and ZFS_THIN is indeed considered
>> storage pool mixing.
>>
>> --
>> Best regards,
>> Gabor Hernadi
>>
>

-- 
Best regards,
Gabor Hernadi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20240205/846d96e8/attachment.htm>


More information about the drbd-user mailing list