XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Not sure if its XOStor but ... VDIs disappearing

    Scheduled Pinned Locked Moved XOSTOR
    3 Posts 2 Posters 16 Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J Online
      jcdick1
      last edited by jcdick1

      I am having an issue with my XCP cluster, running Linstor across three nodes.

      Migrations don't complete. The final handoff doesn't finish, and they sit at 100%. VM reboots result in the underlying VDI becoming unavailable. A VM that was running just fine gets a reboot and I have to go through the process of 'xl list' 'xl destroy <X>' etc. And then on attempted start:

      Error code: SR_BACKEND_FAILURE_46
      Error parameters: , The VDI is not available [opterr=VDI 6c8fe996-2466-47ef-993b-0de3b66da92e not detached cleanly],

      I can't snapshot or do full backups. The task just hangs.
      Edit: I just attempted a snapshot of a VM via the official XO Appliance, and got this:

      SR_BACKEND_FAILURE_82(, Failed to snapshot VDI [opterr=['MAP_DUPLICATE_KEY', 'VDI', 'sm_config', 'OpaqueRef:cbf6441d-c558-725b-8b21-39609026f507', 'paused']], )

      This is becoming a regular occurrence, and I'm not sure what to do to stop this. My environment is slowly degrading. But it definitely seems like its an issue within the SR.

      Any help would be appreciated.

      poddingueP 1 Reply Last reply Reply Quote 0
      • poddingueP Online
        poddingue Vates 🪐 @jcdick1
        last edited by

        Before anything else, could you post rpm -q sm from one of the hosts?

        A batch of LINSTOR fixes landed in sm 3.2.12-23.1 back in July, and two of them sit in the path your error comes out of: one stops it loading VDIs during VDI.deactivate, and another changes when the GC gives up if a VHD chain is still open. 🤞

        I'm reading patch names out of the changelog rather than the patches themselves (way out of my league), so I honestly don't know whether they touch your case, but the version is the cheapest thing to rule in or out first.

        If you're already on that one or later and still hitting this, let us know, because being up to date and still broken is a different problem from being behind.

        Either way, probably worth pulling in @Team-Storage.

        J 1 Reply Last reply Reply Quote 0
        • J Online
          jcdick1 @poddingue
          last edited by jcdick1

          @poddingue

          sm-3.2.12-23.5.xcpng8.3.x86_64 across all three hosts.

          Just tried running through the chain of repair and restart, and I'm getting this on the latest as well:

          [12:49 host1 ~]# xe vm-start uuid=c0faf508-9f14-e091-43b1-d6c5ef7e07d4
          Error code: SR_BACKEND_FAILURE_1200
          Error parameters: , [Errno 30] Read-only file system: '/dev/drbd/by-res/xcp-volume-693829e3-0b60-4b0c-bed2-611995ec83f1/0',

          1 Reply Last reply Reply Quote 0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          • First post
            Last post