ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Solved iscsitargets unavailable after reboot

    IT Discussion
    3
    5
    765
    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.
    • M
      momurda
      last edited by

      I am stumped here with this problem. I setup a raid 10 array with mdadm made a vg and lv, configured iscsitarget and successfully get the SR to show up in XenServer using Xencenter. I can even load vms on it and do everything it should be able to. Until i reboot the iscsi storage. Then i get
      (0_1470087897267_upload-da84e3d4-1b29-4398-ace3-b2e18d0c659c

      Then of course the test vm wont load correctly. vgs and lvs and pvs all show what i think to be incorrect data after the reboot as well. Certainly not the same as when it is working.
      After reboot lvs and vgs:
      0_1470088695765_upload-0a8761e5-d1c7-4c9e-8e52-d7b20f3cdd70

      T 1 Reply Last reply Reply Quote 4
      • M
        momurda
        last edited by

        Fixed it. the local server lvm service was 'stealing' the block device before iscsi could get it and serve it out. I ended up going into lvm.conf and adding a global filter option.
        Would be nice if the novel of commented lines in lvm.conf would have mentioned when this could/should be used. A normal filter option didnt ever work. But it was a redhat doc i found with a sentence that mentions iscsi devices for vms might have to use the global filter option.

        1 Reply Last reply Reply Quote 3
        • T
          travisdh1 @momurda
          last edited by

          @momurda What's the /etc/tgt/targets.conf look like?

          1 Reply Last reply Reply Quote 1
          • M
            momurda
            last edited by

            Fixed it. the local server lvm service was 'stealing' the block device before iscsi could get it and serve it out. I ended up going into lvm.conf and adding a global filter option.
            Would be nice if the novel of commented lines in lvm.conf would have mentioned when this could/should be used. A normal filter option didnt ever work. But it was a redhat doc i found with a sentence that mentions iscsi devices for vms might have to use the global filter option.

            1 Reply Last reply Reply Quote 3
            • M
              momurda
              last edited by

              Further note.
              This seems to be a problem when using IET iscsi service. This IET seems to be an older implementation of iscsitargets on linux.
              I removed IET, installed and configured targetcli, removed the lvm filter. All is much better now, and dmesg shows no errors on boot.
              Also getting higher performance now as well with targetcli v iet

              1 Reply Last reply Reply Quote 1
              • S
                scottalanmiller
                last edited by

                Yeah, IET is not new.

                1 Reply Last reply Reply Quote 0
                • 1 / 1
                • First post
                  Last post