Re: DRBD Behavior on Device Failure, and Recovery Procedure
Gábor Hernádi <[email protected]>
| Newsgroups | gmane.comp.linux.drbd |
|---|---|
| Message-ID | <CAL16tNZp=JEDeC=g9rQPs3sE97XQ=rfWza=vTDtyVZdcR7kjMQ@mail.gmail.com> |
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 _______________________________________________ Star us on GITHUB: https://github.com/LINBIT drbd-user mailing list [email protected] https://lists.linbit.com/mailman/listinfo/drbd-user