similar to: iscsi target rescan means connections hang for five seconds

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'>

Out of haste I decided for the first time not to pull down and compile iet to export a single volume to a windows machine so I just used tgtd. Well, much more time later than otherwise would be the case had I used iet, when I mount the volume on the windows ini, it can't find and install a driver? WTF? This have anything to do with the tgtd being a tech preview:) Anybody seen this b4? jlc

Hey everyone, Is anybody aware of a /true/ active/active multi-head and multi-target clustered iSCSI daemon? IE: Server 1: Hostname: host1.test.com IP Address: 10.0.0.1 Server 2: Hostname: host2.test.com IP Address: 10.0.0.2 Then they would utilize a CLVM disk between them, let's call that VG "disk" and then directly map each LUN (1,2,3,4,etc) to LV's named 1,2,3,4,... and

On 09.12.2015 00:39, NightLightHosts Admin wrote: > On Tue, Dec 8, 2015 at 5:26 PM, Dennis Jacobfeuerborn > <dennisml at conversis.de> wrote: >> Hi, >> today we ran into a strange problem: When performing a regular Windows >> 2008r2 update apparently among other things the following was installed: >> "SUSE - Storage Controller - SUSE Block Driver for

> 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 12/22/2013 10:09 AM, Marco wrote: > On 2013–12–21 John Ferlan wrote: > >> On 12/17/2013 07:13 PM, Marco wrote: >>> Hi! >>> >>> I'm new to libvirt and face problems connecting to an iSCSI target. >>> What I intend to do is to connect libvirt (I tried virt-manager and >>> virsh) to an iSCSI target and then boot from the LUNs which

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 12/17/2013 07:13 PM, Marco wrote: > Hi! > > I'm new to libvirt and face problems connecting to an iSCSI target. > What I intend to do is to connect libvirt (I tried virt-manager and > virsh) to an iSCSI target and then boot from the LUNs which contain > the VMs. > > I followed the documentation¹ but got stuck at section 12.1.5.4.3. > > 1) > virsh

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

Matej, > This change introduces the behaviour described above by scanning the > entire scsi target when LUN is set to 0. This is both a functional and a > performance fix. It aligns the driver with the spec and allows control > planes to hotplug targets with large numbers of LUNs without having to > request a RESCAN for each one of them. Applied to 5.10/scsi-staging, thanks! --

Hi, I'm trying to build a redundant duo of firewalls/routers/gateways and I'm thinking about not putting any disks in them and instead using a usb-stick raid-1 as storage. Has anyone any experience with this? Since the machines will be running pretty much only iptables, conntrackd and keepalived there is not going to be a lot of disk activity going on and the plan is to do all the

On 27.02.2018 16:45, Stephen John Smoogen wrote: > On 27 February 2018 at 06:11, Dennis Jacobfeuerborn > <dennisml at conversis.de> wrote: >> Hi, >> I'm currently trying to mirror a couple of yum repositories and the only >> tool that seems to be available for this is reposync. >> Unfortunately reposync for some inexplicable reason seems to use the yum

On 15 Apr 2015 13:22, "Dennis Jacobfeuerborn" <dennisml at conversis.de> wrote: > > On 15.04.2015 12:41, Alessandro Baggi wrote: > > Hi there, > > Yesterday I've updated from 7 to 7.1 and today I've noticed on 2 server > > that postgresql systemd file was replaced with default values. This make > > postgres to no start and webserver give me

Hi, I'm currently trying to mirror a couple of yum repositories and the only tool that seems to be available for this is reposync. Unfortunately reposync for some inexplicable reason seems to use the yum config of the local system as a basis for its work which makes no sense and creates all kinds of problems where cache directories and metadata gets mixed up. Are there any alternatives? Some

Do you need the whole configuration? On the switch end, we have the relevant VLAN (VLAN 48) with the assigned IP address of 192.168.48.101 and the range of ports (Gi1/0/1 - Gi1/0/8) assigned to that VLAN. Seems - and acts - like a legitimate setup and works fine, except for this particular instance. Thanks. Boris. On Fri, Jan 23, 2015 at 8:54 PM, Dennis Jacobfeuerborn < dennisml at

Andrew and Dennis are spot on. Their conclusions about your server being connected to an access port and not a trunk port would be my conclusion as well. On Sat, Jan 24, 2015 at 9:11 AM, Dennis Jacobfeuerborn < dennisml at conversis.de> wrote: > Hi Boris, > what I'd like to know is the actual VLAN configuration of the switch > port (link-type and tagged and untagged VLANs).

On 2013–12–21 John Ferlan wrote: > On 12/17/2013 07:13 PM, Marco wrote: > > Hi! > > > > I'm new to libvirt and face problems connecting to an iSCSI target. > > What I intend to do is to connect libvirt (I tried virt-manager and > > virsh) to an iSCSI target and then boot from the LUNs which contain > > the VMs. > > > > I followed the

This is pretty epic if true. I'm installing some Fail 2008r2 now to check. Is your hypervisor running CentOS 6 or 7? -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- > From: "Dennis Jacobfeuerborn" <dennisml at conversis.de> > To: "Discussion about the virtualization on CentOS" <centos-virt at