Categories

  • All news regarding Xen and XCP-ng ecosystem

    145 Topics
    5k Posts
    Y
    @dinhngtu Yes, I've submitted a false positive report here: https://www.bitdefender.com/en-us/business/submit

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    dthenotD
    @samuelolavo Hello, Could the fact that this is a local LVM SR on a non-master host be relevant to how make_chain_rw is being handled? Yes, it's indeed what's happening. The check for the SRMaster (for a shared SR it's the master but for a local it's supposed to be done on the host directly) is failing and always saying False. I'll fix this. Thank you for the help

  • All Xen Orchestra related questions/reports

    3k Topics
    29k Posts
    P
    @Danp Happy to hear that you too were able to reproduce the phenomenon. Thank you for taking the time to look.

  • Our hyperconverged storage solution

    52 Topics
    812 Posts
    poddingueP
    From LINBIT's description, drbd_peerdevice_outofsync_bytes is what one node's bitmap says is still out of sync with one particular peer, while the UpToDate in linstor r l is the state of each node's own disk, so as far as I understand the two aren't measuring the same thing (the resource states are described at https://docs.xcp-ng.org/xostor#drbdlinstor-resource-state). Your table has the 119 GiB on .10 and .14, the two Unused copies, so I'd be curious which peer those series point at; the labels on the metric should say. If I'm reading drbd-utils right, drbdsetup status xcp-volume-6a8544e8-f17f-49c8-b725-54c5e3213ae1 --verbose --statistics on xen01 also prints an out-of-sync figure per peer, but I haven't got an XOSTOR cluster to try it on, so treat that as a (not so educated) guess. Whether a non-zero number between two secondaries means anything is beyond me; @Team-Storage will know.

  • Non-English speakers

    37 Topics
    136 Posts
    J
    @AtaxyaNetwork Merci pour tes recherches ! Oui "cd_label" serait cool comme ajout au plugin ce qui permet sur les distro type Fedora/Redhat de ne pas avoir de boot_command à gérer