We only have 2 nodes as of today. It is not easy to explain why vm creation fails, given that we cannot see any error from Linstor / DRBD logs...
We removed 5 old error reports and linstor sp l, and linstor err l still needs 20seconds or so. May be it's time to rebuild from scratch now. Thank you very much for your help, Christophe. Le mer. 5 févr. 2020 à 11:53, Gábor Hernádi <[email protected]> a écrit : > Hello, > > in the logs you can see that `lvs` needs ~150ms, `vgs` ~15-20ms, > `lvcreate` ~200ms, `drbdadm ... --create-md` about 3 seconds (that is > fine)... so no external command executed by linstor is exceptionally slow.. > > however, the reason that a `linstor err show` takes 20 seconds does not > sound good. processing that command basically sends a request to the > controller, the controller forwards the request to the specific satellite, > that satellite reads the content of the specific error report and sends it > back to the controller and thus to the client. > To be honest, there is only one cause that comes to my mind that could > explain this waiting time, namely if you have a huge amount of error > reports. > If you have, you should maybe cleanup old error reports (moving them away > from the usual directory should be enough) > > regarding the last line of the log file you sent: linstor seems to be > happy with the auto-place (that scary large negative number at the ret_code > is only a warning that you apparently have only 2 nodes but auto-tiebreaker > is active.. without a 3rd node that feature cannot be used, which is what > linstor warns you about - usually that warning can be safely ignored) > > -- > Best regards, > Gabor >
_______________________________________________ Star us on GITHUB: https://github.com/LINBIT drbd-user mailing list [email protected] https://lists.linbit.com/mailman/listinfo/drbd-user
