similar to: Any information on targetcli (fcoe) for centos 6? Close to end of my rope

CentOS Errata and Enhancement Advisory 2018:1403 Upstream details at : https://access.redhat.com/errata/RHEA-2018:1403 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 52be736c9ef564f9822e7f0165a77403547bfcb958eba0d3a31e1a751caa95ac targetcli-2.1.fb46-4.el7_5.noarch.rpm Source:

CentOS Errata and Bugfix Advisory 2018:1999 Upstream details at : https://access.redhat.com/errata/RHBA-2018:1999 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: bbef4644c71682f79333af26666663364030908e692da8553cb0482292f13952 targetcli-2.1.fb46-6.el7_5.noarch.rpm Source:

http://bugs.freedesktop.org/show_bug.cgi?id=15486 Summary: You Have to Burn the Rope doens't work Product: swfdec Version: unspecified Platform: Other URL: http://www.mazapan.se/games/BurnTheRope.php OS/Version: All Status: NEW Severity: normal Priority: medium Component: library

I have been successful at getting one XEN host to initiate a iSCSI connection to a target served by CentOS7, but not a second XEN host. xe sr-create complains the StorageRepository is in use. Is there a configuration change? Another iSCSI target server to use?

CentOS Errata and Bugfix Advisory 2015:1961 Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-1961.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: a0ee99a9a8c2dc995c8836241b5eda2d7015599390f42550c97a230b23b3c79a fcoe-utils-1.0.29-9.1.el7_1.x86_64.rpm Source:

CentOS Errata and Bugfix Advisory 2017:0916 Upstream details at : https://rhn.redhat.com/errata/RHBA-2017-0916.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 33f74dbf67f72c8235f187c13dc3fff8ee141cadd5600772b78f3d472f0c54f2 fcoe-utils-1.0.31-1.git5dfd3e4.el7_3.1.x86_64.rpm Source:

CentOS Errata and Bugfix Advisory 2019:0515 Upstream details at : https://access.redhat.com/errata/RHBA-2019:0515 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 6d19ac27ae50b29b496a7250101cb44ebda60ec5d5d53cc38494fd2ef9e3a5f0 fcoe-utils-1.0.32-2.el7_6.x86_64.rpm Source:

Hi, Michael I have met ext4 error when using vhost_scsi on arm64 platform, and suspect it is vhost_scsi issue. Ext4 error when testing virtio_scsi & vhost_scsi No issue: 1. virtio_scsi, ext4 2. vhost_scsi & virtio_scsi, ext2 3. Instead of vhost, also tried loopback and no problem. Using loopback, host can use the new block device, while vhost is used by guest (qemu).

Hi, Michael I have met ext4 error when using vhost_scsi on arm64 platform, and suspect it is vhost_scsi issue. Ext4 error when testing virtio_scsi & vhost_scsi No issue: 1. virtio_scsi, ext4 2. vhost_scsi & virtio_scsi, ext2 3. Instead of vhost, also tried loopback and no problem. Using loopback, host can use the new block device, while vhost is used by guest (qemu).

In waiting, I tried CentOS 8 which was an even bigger bust. I wiped that clean and tried again with Fedora 31. Same darn error "Could not create Target in configFS". Anyone?? Thank you, Steffan Cline steffan at hldns.com 602-793-0014 ?On 1/2/20, 2:00 AM, "CentOS on behalf of Steffan Cline via CentOS" <centos-bounces at centos.org on behalf of centos at centos.org>

Hi, I am working to get iscsi running using targetcli. So far everything seems to be working except for the fact that when I run saveconfig, exit the targetcli shell and reboot, the iscsi configs are gone. If I run restoreconfig, the configuration gets reloaded and all is well. Can someone tell me how to get the targetcli configuration to persist through a reboot? Regards, -- Tom me at

On Wed, Sep 13, 2017 at 1:03 PM, GiangCoi Mr <ltrgiang86 at gmail.com> wrote: > Hi all > Hi GiangCoi, The Good news is that now we have gluster-block [1] which will help you configure block storage using gluster very easy. gluster-block will take care of all the targetcli and tcmu-runner configuration for you, all you need as a pre-requisite is a gluster volume. And the sad part is

Hi there, I've installed C7 and I'm trying to use targetcli and other. Until yesterday all works good. Today I've runned yum update, that has updated glibc. Then I installed targetcli and targetd. After some operation on an md device like mount/umont. After this, during yum install lsof I get: ..... Install 1 Package Total size: 331 k Installed size: 927 k Is this ok [y/d/N]: y

Hi Jeremy, It's now clear. We'll do a short term workaround somehow. I created the bug. https://bugzilla.samba.org/show_bug.cgi?id=11295 Thanks for the useful reply. Kind regards, Szilard 2015-05-28 2:27 GMT+02:00 Jeremy Allison <jra at samba.org>: > On Wed, May 27, 2015 at 11:16:08PM +0200, Szilard Matyas wrote: > > Dear Gents, > > > > We are using

Hi Ralph, I applied the patch to a new build of Sernet 4.4.6 SRPM. I could still open the file from both hosts, and in fact this time I could actually open it on the same host without any problems: host 1: smbclient -U ajc //172.31.0.120/ifa_v ... smb: \jmi\Corporate Accounting\ISL Ltd Accounts\2016\1609\> open "201609 213_ ISL Balance sheet variance analysis.xls" open file

In having configured my first * server there are a few questions I could not understand or find answers to 1) How does one use ztmonitor to adjust the rxgain and txgain. I have set mine to -1.0 each to get rid of echo on std phones connected on the TDM10B FXS module 2) Is it best to use a TDM card with an TFX and FXO module or is the the FXO = X100p and FXS on TDM a good method? 3) How do I

Hi all I want to configure glusterfs to expose iSCSI target. I followed this artical https://pkalever.wordpress.com/2016/06/23/gluster-solution-for-non-shared-persistent-storage-in-docker-container/ but when I install tcmu-runner. It doesn't work. I setup on CentOS7 and installed tcmu-runner by rpm. When I run targetcli, it not show *user:glfs* and *user:gcow* */>* ls o- /

In commit 365a7150094 ([SCSI] virtio-scsi: hotplug support for virtio-scsi), hotplug support is added to virtio-scsi. This patch adds hotplug and hotunplug support to tcm_vhost. You can create or delate a LUN in targetcli to hotplug or hotplug a LUN in guest. Signed-off-by: Asias He <asias at redhat.com> --- drivers/vhost/tcm_vhost.c | 171 ++++++++++++++++++++++++++++++++++++++++++++--

In commit 365a7150094 ([SCSI] virtio-scsi: hotplug support for virtio-scsi), hotplug support is added to virtio-scsi. This patch adds hotplug and hotunplug support to tcm_vhost. You can create or delate a LUN in targetcli to hotplug or hotplug a LUN in guest. Signed-off-by: Asias He <asias at redhat.com> --- drivers/vhost/tcm_vhost.c | 171 ++++++++++++++++++++++++++++++++++++++++++++--

Hi folks, The following are initial virtio-scsi + target vhost benchmark results using multiple target LUNs per vhost and multiple virtio PCI adapters to scale the total number of virtio-scsi LUNs into a single KVM guest. The test setup is currently using 4x SCSI LUNs per vhost WWPN, with 8x virtio PCI adapters for a total of 32x 500MB ramdisk LUNs into a single guest, along with each backend