<p dir="ltr"></p>
<p dir="ltr">On 17 Oct 2016 6:11 pm, "Gandalf Corvotempesta" <<a href="mailto:gandalf.corvotempesta@gmail.com">gandalf.corvotempesta@gmail.com</a>> wrote:<br>
><br>
> Il 17 ott 2016 09:01, "Jan Schermer" <<a href="mailto:jan@schermer.cz">jan@schermer.cz</a>> ha scritto:<br>
> ><br>
> > 3 storages, many more hypervisors, data triplicated... that's the usual scenario<br>
><br>
> Are you using drbd9 with a 3 nodes replication?<br>
> could you please share the drbd config?<br>
><br>
> > We use ZFS on the storages, ZVOLs on top of that, each ZVOL makes up part of the DRBD resource that gets exported to the hypervisor.<br>
><br>
> No raid volumes?<br>
> are you creating a single drbd resource for each storage disk? (In example, in a server with 12 disks are you creating 12 drbd resources?)<br>
><br>
> i would like to create a raidz2 on each node but the resulting volume is not seen as block device thus can't be used as drbd resource<br>
><br>
And thats why you create zvol then and use it as backing device for the drbd device. How many zvols/drbds you create depends on the raidz2 size and your needs. Each zvol backed drbd is then given to the hypervisor to be used as vm volume.</p>
<p dir="ltr">> I can create a raid6 with mdadm, use that volume for drbd and put zfs on top of it but there are too many moving parts stacked together, that would be a perfect reciepe for a huge mess<br>
><br>
><br>
> _______________________________________________<br>
> drbd-user mailing list<br>
> <a href="mailto:drbd-user@lists.linbit.com">drbd-user@lists.linbit.com</a><br>
> <a href="http://lists.linbit.com/mailman/listinfo/drbd-user">http://lists.linbit.com/mailman/listinfo/drbd-user</a><br>
></p>