[DRBD-user] DRBD Behavior on Device Failure, and Recovery Procedure

Gábor Hernádi gabor.hernadi at linbit.com
Mon May 2 10:56:59 CEST 2022


Hello,

As mentioned in the other drbd-user thread (Adding a Physical Disk to a
Storage Pool), this behaviour is controlled by LVM, not by Linstor. During
the `linstor sp c ...` command you only gave Linstor the name of the
volume-group, which is also what Linstor will use for the `lvcreate ...`
commands. If you want to control how LVM distributes the volumes within
that VG, you have to configure your VG accordingly, or use Linstor's
"StorDriver/LvcreateOptions"
property [1] to configure raid levels "per resource" (you can also set that
property on controller level which will affect all new resources).

> In such an event, what would be the recovery procedure? Swap the failed
drive, use vgcfrestore to restore the LVM data to the new PV, then do a
DRBD resync?

Sounds correct to me.

[1]
https://linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-storage-providers
-- 
Best regards,
Gabor Hernadi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20220502/86ebcd30/attachment.htm>


More information about the drbd-user mailing list