similar to: [PATCH] Rescan the entire target on transport reset when LUN is 0

On Fri, 28 Aug 2020 12:21:35 +0000, Matej Genci wrote: > VirtIO 1.0 spec says > The removed and rescan events ... when sent for LUN 0, they MAY > apply to the entire target so the driver can ask the initiator > to rescan the target to detect this. > > This change introduces the behaviour described above by scanning the > entire scsi target when LUN is set to 0.

> On Sep 8, 2020, at 3:22 PM, Paolo Bonzini <pbonzini at redhat.com> wrote: > > On 28/08/20 14:21, Matej Genci wrote: >> VirtIO 1.0 spec says >> The removed and rescan events ... when sent for LUN 0, they MAY >> apply to the entire target so the driver can ask the initiator >> to rescan the target to detect this. >> >> This change

On Fri, Aug 28, 2020 at 12:21:35PM +0000, Matej Genci wrote: > VirtIO 1.0 spec says > The removed and rescan events ... when sent for LUN 0, they MAY > apply to the entire target so the driver can ask the initiator > to rescan the target to detect this. > > This change introduces the behaviour described above by scanning the > entire scsi target when LUN is set to

On 28/08/20 14:21, Matej Genci wrote: > VirtIO 1.0 spec says > The removed and rescan events ... when sent for LUN 0, they MAY > apply to the entire target so the driver can ask the initiator > to rescan the target to detect this. > > This change introduces the behaviour described above by scanning the > entire scsi target when LUN is set to 0. This is both a

On 28/08/20 14:21, Matej Genci wrote: > VirtIO 1.0 spec says > The removed and rescan events ... when sent for LUN 0, they MAY > apply to the entire target so the driver can ask the initiator > to rescan the target to detect this. > > This change introduces the behaviour described above by scanning the > entire scsi target when LUN is set to 0. This is both a

I've configured a libvirt storage pool using an iscsi target from a Sun 7310 storage appliance and am using the LUNs in this target as volumes for my KVM guests. The setup is very similar to what Daniel covered in a recent blog posting: http://berrange.com/posts/2010/05/05/provisioning-kvm-virtual-machines-on-iscsi-the-hard-way-part-2-of-2/ It works great, but I can't figure out how

Hi, When I add a new LUN on an iscsi target and then issue a pool-refresh command on the respective storage pool in libvirt, libvirt will not find the new lun (or notice if luns have been removed). I'm using a Dell PowerVault MD3200i iSCSI Array to hold the volumes for virtual servers in libvirt. In libvirt, I have defined the storage pool as this: <pool type='iscsi'>

Hi, I'm starting to experiment with iscsi based volumes and while this works fine so far I ran into a problem. When I add a LUN to a target and refresh tgtd all i/o to that target seems to hang for five seconds. This is obviously less than ideal if the plan is to use the target for lots of guests. There is also the possibility to create one target with one LUN for each guest disk but that

Hi there, I've installed a Qlogic HBA in a 4.8-STABLE machine and I'm able to present LUNs to this machine from an HDS array and use them. That all works perfectly. However, the only time I pick up new LUNs is on a reboot. Seems like I should be able to rescan the fabric and pick up new LUNs, but there doesn't seem to be a way to do this. I tried camcontrol rescan, but that

Hello, How to explain to fdisk that /dev/sda size changed? I increased LUN on storage, reloaded iscsi, did echo 1 > /sys/<something>/rescan. And I see in "dmesg" that kernel found new size of the LUN. But when I type "fdisk /dev/sda" it still shows old size. On /dev/sda1 sits LVM PV and I'd like to resize it instead of adding one more PV to volume group.

Hi everybody. I have an HP StorageWorks array connected to one of my servers, connected via an LSI controller (lspci reports: SCSI storage controller: LSI Logic / Symbios Logic SAS1068E PCI-Express Fusion-MPT SAS (rev 08)) on an HP DL385 running CentOS 5.5 x86_64. I have set up multipath and all is working but, when I create a snaphost and export it as a new LUN from the HP web interface, it

Hi, I got few servers (IBM HS20,HS21 blades, IBM xSeries 3650 & others) connected to a dual fabric san throught Qlogic HBA's (23xx, 24xx). Multipathing is done with device-mapper-multipath. On CentOS 4.x i can scan for new scsi devices without any problems, get them up with multipathing & use them without any problems. However, after i started installing CentOS 5.1 (did not

Hi All :) I am currently involved in a project in which there is a SAN array (Sun Storagetek 2540) which exports LUNs for some servers with Centos 5.2 x86. I will be performing a migration to Centos 5.9 x86_64 in some time and am gathering needed info now :) I am trying to find the place in the OS where there is the information about LUN mappings to /dev/ devices. For example on array level I

Hi Rusty, here is the specification for a virtio-based SCSI host (controller, HBA, you name it) so that you can apply it to the spec document and publish it. I changed the index from 7 to 8 to account for the rpmsg device, and added a feature bit to tell the guest in advance whether the host supports hotplug. Otherwise there is no change from v2. Paolo --- virtio-spec.lyx.saved 2011-11-29

Hi Rusty, here is the specification for a virtio-based SCSI host (controller, HBA, you name it) so that you can apply it to the spec document and publish it. I changed the index from 7 to 8 to account for the rpmsg device, and added a feature bit to tell the guest in advance whether the host supports hotplug. Otherwise there is no change from v2. Paolo --- virtio-spec.lyx.saved 2011-11-29

Matt, > The event handler calls scsi_scan_host() when events are missed, which > will hotplug new LUNs. However, this function won't remove any > unplugged LUNs. The result is that hotunplug doesn't work properly > when the number of unplugged LUNs exceeds the event queue size > (currently 8). > > Scan existing LUNs when events are missed to check if they are still

Hi all, here is the specification for a virtio-based SCSI host (controller, HBA, you name it). The virtio SCSI host is the basis of an alternative storage stack for KVM. This stack would overcome several limitations of the current solution, virtio-blk: 1) scalability limitations: virtio-blk-over-PCI puts a strong upper limit on the number of devices that can be added to a guest. Common

Hi all, here is the specification for a virtio-based SCSI host (controller, HBA, you name it). The virtio SCSI host is the basis of an alternative storage stack for KVM. This stack would overcome several limitations of the current solution, virtio-blk: 1) scalability limitations: virtio-blk-over-PCI puts a strong upper limit on the number of devices that can be added to a guest. Common

virtio-scsi currently has limit of 8 outstanding notifications so when more that 8 LUNs are unplugged, some are missed. Commit 5ff843721467 ("scsi: virtio_scsi: unplug LUNs when events missed") Fixed this by checking the 'event overflow' bit and manually scanned the bus to see which LUNs are still there. However there is a corner case when all LUNs are unplugged. In this case

Link: http://wiki.libvirt.org/page/NPIV_in_libvirt Topic: Virtual machine configuration change to use vHBA LUN There is a NPIV storage pool defined on two hosts and pool contains a total of 8 volumes, allocated from a storage device. Source: # virsh vol-list poolvhba0 Name Path ------------------------------------------------------------------------------ unit:0:0:0