I think that dual primary option is disabled by default in linstor/drbd9. So, in order to activate it you will have to either activate it globally by using "--allow-two-primaries" option in "linstor controller" options (that's if you wish all current and future linstor resources to have that option enabled by default which usually it's not a good idea.), or explicitly enable it per resource definition by using "linstor rd sp <rd_name> DrbdOptions/Net/allow-two-primaries yes" .
Gianni On Mon, 30 Sep 2019 at 06:36, Michael Roth <[email protected]> wrote: > > Hi, > > i've a problem with drbd9 and auto-promote. > > I mount a device on Node #1 , everything is fine. But if I try to mount > the same device on Node # I got the following error. > > mount: /dev/drbd1000 is write-protected, mounting read-only > mount: mount /dev/drbd1000 on /mnt failed: Wrong medium type > > In /var/log/messages I can see the following message > > Sep 27 08:27:21 drbd02 kernel: drbd testvolume: Auto-promote failed: > Multiple primaries not allowed by config > > I'm using a three node drbd 9 cluster with linstor for management. > The strange thing about it is that the existing volumes are still working > with auto-promote, just new volumes have the problem. > > I build a new cluster for testing, with the same result. > > I guess that the upgrade to CentOS 7.7 could have something to do with > that behaviour, I'll check that in the next days. > > I'm thankful for every hint ! > > Best regards, > Michael > > _______________________________________________ > Star us on GITHUB: https://github.com/LINBIT > drbd-user mailing list > [email protected] > https://lists.linbit.com/mailman/listinfo/drbd-user >
_______________________________________________ Star us on GITHUB: https://github.com/LINBIT drbd-user mailing list [email protected] https://lists.linbit.com/mailman/listinfo/drbd-user
