targetcli-fb-devel

targetcli-fb-devel@lists.fedorahosted.org

111 discussions

Minimal version required for configshell-fb, target-fb and rtslib-fb?
by TomK 08 Oct '22

08 Oct '22

Hello, Ref, https://github.com/open-iscsi/configshell-fb/issues/67 +---------------------------------------------------------------------------------------------------------------------------------------------------------- | In /mnt/HTPCFileStorage/Files/target-fb/configshell-fb-rpm/build/rpm/BUILD/configshell-fb-1.1.29.8.gba3a5b8/configshell_fb/shell.py: | Import failed (but source code parsing was successful). | Error: ImportError: cannot import name locatedExpr (line 27) | Above is coming from: configshell-fb-rpm/build/rpm/BUILD/configshell-fb-1.1.29.8.gba3a5b8/configshell_fb/shell.py What is the minimal version of Python libraries and consequently 7 version of the RH clone OS's supported by these tools? I could revert the change to Datera's method: # Pyparsing helper to group the location of a token and its value # http://stackoverflow.com/questions/18706631/pyparsing-get-token-location-in… locator = Empty().setParseAction(lambda s, l, t: l) def locatedExpr(expr): return Group(locator('location') + expr('value')) just not sure if that will be the only thing I need to do or would there be even more packages? Along these lines, what is the minimal version of target-fb, configshell-fb and rtslib-fb I could try that could work with Python 2.6.6 and 6.10 of RHEL clones? -- Thx, Tom K

1 0

【汲】医院租借的李代桃僵,轮椅忘记归还苛政猛于虎
by gl279752 gl279752 11 Dec '21

11 Dec '21

医院租借的轮椅忘记归还 --》点击后面地址进入看午@夜大片: http://myvrti646.aa234.cc/#fedoraproject1211 --》点击后面地址进入看午@夜视频: http://myvrti646.aa234.cc/#fedoraproject1211 医院租借的轮椅忘记归还感恩自然，我们不该忽略。春天，我感谢鸟儿为我高歌，感谢花儿为我绽放；夏天，我感谢烈日给我以磨练，感谢暴雨给我以洗礼；秋天，我感谢飒飒的秋风，感谢无边的金色的稻田，感谢勤劳的农民伯伯；冬天，我感谢雪花为我飞舞，感谢狂风为我呼啸。然而，总有一些贪得无厌的人不懂感恩。他们乱砍滥伐，污染蓝天，污染河流，向大自然肆意掠夺。一时的横财助长了贪念，于是，天空不再蔚蓝，溪水不再清澈，沙漠取代了森林……有人说，去到江南一定要去一次乌镇，你定会感到不虚此行。于是我们便又踏上乌镇的旅途。小桥流水，悠悠船歌，这正是我对乌镇的第一感觉。站在那古老的石桥上，轻轻抚过桥身，手心的微凉，带着潮湿的水汽，温柔细腻得恰到好处。听，那船娘的歌声温和动听，轻轻地飘荡在空气中，把我们裹进一片梦幻般的世界里。离开乌镇时，已经很晚了，让我不能忘记的是这里的古色古香，和这里的小桥、流水、人家。【汲】医院租借的李代桃僵,轮椅忘记归还苛政猛于虎或许自己所拥有的就是幸福！“幸福”多么温馨的字眼，幸福是幸运女神的眷顾，世间万物都受着上帝的恩惠，都拥有着属于自己的幸福。医院租借的轮椅忘记归还

1 0

Pull request #165 review
by Jaroslav Petráš 26 Oct '20

26 Oct '20

Hi there, sorry for disturbance in the force but I would like to ask someone responsible if is it possible to review https://github.com/open-iscsi/rtslib-fb/pull/165 because it is dependency for another pull request https://github.com/ClusterLabs/resource-agents/pull/1529. Thanks and have a nice day. -- Best regards Jaroslav Petráš

2 1

Recent security vulnerabilities reported but no response
by Alex Murray 25 Mar '20

25 Mar '20

Hi, As per https://github.com/open-iscsi/targetcli-fb I recently reported a couple security vulnerabilities[1][2] which I found whilst reviewing targetcli-fb for inclusion in main in Ubuntu[3] - however, I have not received a response. Whilst I realise it has only been a couple days, given the potential severity of these issues I was hoping for some kind of response - is targetcli-fb still maintained? If so, can a maintainer please take a look at these issues? [1] https://github.com/open-iscsi/targetcli-fb/issues/162 [2] https://github.com/open-iscsi/targetcli-fb/issues/163 [3] https://bugs.launchpad.net/ubuntu/+source/targetcli-fb/+bug/1854362 Thanks, Alex --- Ubuntu Security Tech Lead

2 1

want to create readonly block backstore from otherwise mounted block device.
by stefan j kozak 24 Mar '20

24 Mar '20

i want to use /dev/sda1 (which is already mounted r/w elsewhere) as a r/o block backstore. it wont let me and I dont see why that isnt allowable... ------snip start /backstores/block> create sda /dev/sda1 true Cannot configure StorageObject because device /dev/sda1 is already in use ------snip stop So..... i commented out the "raise RTSLibError("Cannot configure Storag.... " in rtslib_fb/tcm.py class BlockStorageObject(StorageObject): _configure to see where that got me. turns out it blows up again trying to fwrite(path, "1\n") where path is "/sys/kernel/config/target/core/iblock_2/MOOOOOO/enable" , so the kernel is complaining i guess? why does it need to write 1 there to enable it? what is it enabling exactly, LIO? now, i'm no dummy, and I know when i'm out of my element.... so just how does targetcli-fb go about setting up LIO to make a target anyways? Shouldn't making a readonly backstore be a no-risk kinda thing? Is there a way to bypass targetcli-fb and do this manually? Not really seeking a feature add, but more rather understanding at what's at play here, and ill keep plugging along to see if I cant figure it out on my own, too. (trying to make a FC target here in this instance if it matters) stay corvid-free, thanks in advance, joe. email$ echo -n "dd if=/dev/zero of=/dev/null count=1 bs=1G"|sed -E s/\\W+/"."/g;echo @gmail.com

1 0

Re: Could not create Target in configFS
by Steffan Cline 05 Feb '20

05 Feb '20

It turns out the cards I had were falsely advertised as QLE2662 and is why no matter what I did, they wouldn't work. I checked with the SCST developer and it seems no luck there since there's no support in the kernel for anything other than initiator mode. I replaced them with some QLE2564/2562 and am getting MUCH closer with targetcli to making it work. I took a large /dev/sda drive and created a partition of two different sizes as sda1 and sda2, one for working LVM space and the other for a backup volume. Currently my target cli is set up like this: o- / ..................................................................................................................... [...] o- backstores .......................................................................................................... [...] | o- block .............................................................................................. [Storage Objects: 2] | | o- vm_backup .................................................................. [/dev/sda2 (0 bytes) write-thru activated] | | | o- alua ............................................................................................... [ALUA Groups: 1] | | | o- default_tg_pt_gp ................................................................... [ALUA state: Active/optimized] | | o- vm_shared .................................................................. [/dev/sda1 (0 bytes) write-thru activated] | | o- alua ............................................................................................... [ALUA Groups: 1] | | o- default_tg_pt_gp ................................................................... [ALUA state: Active/optimized] | o- fileio ............................................................................................. [Storage Objects: 0] | o- pscsi .............................................................................................. [Storage Objects: 0] | o- ramdisk ............................................................................................ [Storage Objects: 0] o- iscsi ........................................................................................................ [Targets: 0] o- loopback ..................................................................................................... [Targets: 0] o- qla2xxx ...................................................................................................... [Targets: 1] | o- naa.21000024ff67440f ......................................................................................... [gen-acls] | o- acls ........................................................................................................ [ACLs: 1] | | o- naa.21000024ff56a8a8 ............................................................................... [Mapped LUNs: 2] | | o- mapped_lun0 ........................................................................... [lun0 block/vm_shared (rw)] | | o- mapped_lun1 ........................................................................... [lun1 block/vm_backup (rw)] | o- luns ........................................................................................................ [LUNs: 2] | o- lun0 ............................................................... [block/vm_shared (/dev/sda1) (default_tg_pt_gp)] | o- lun1 ............................................................... [block/vm_backup (/dev/sda2) (default_tg_pt_gp)] o- vhost ........................................................................................................ [Targets: 0] The naa.21000024ff67440f under qla2xxxx is the port_name of the target. Under acls, naa.21000024ff56a8a8 is the port_name on the initiator. I used find /sys -name port_name | xargs head to get those. My initiator has a FreeNAS box tied to the second port so the sdb though sdf is the FreeNAS box but lun0 part1 part2 **looks** like the target I'm trying to configure. I'm not sure yet how to tell if that is the sda1&2 for the boot volume from this view. lrwxrwxrwx 1 root root 9 Feb 2 14:41 fc-0x21000024ff56a8a9-0x21000024ff6ba2cc-lun-0 -> ../../sdb lrwxrwxrwx 1 root root 10 Feb 2 14:41 fc-0x21000024ff56a8a9-0x21000024ff6ba2cc-lun-0-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 Feb 2 14:41 fc-0x21000024ff56a8a9-0x21000024ff6ba2cc-lun-1 -> ../../sdc lrwxrwxrwx 1 root root 10 Feb 2 14:41 fc-0x21000024ff56a8a9-0x21000024ff6ba2cc-lun-1-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 Feb 2 14:41 fc-0x21000024ff56a8a9-0x21000024ff6ba2cc-lun-2 -> ../../sdd lrwxrwxrwx 1 root root 10 Feb 2 14:41 fc-0x21000024ff56a8a9-0x21000024ff6ba2cc-lun-2-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 Feb 2 14:41 fc-0x21000024ff56a8a9-0x21000024ff6ba2cc-lun-3 -> ../../sde lrwxrwxrwx 1 root root 10 Feb 2 14:41 fc-0x21000024ff56a8a9-0x21000024ff6ba2cc-lun-3-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 Feb 2 14:41 fc-0x21000024ff56a8a9-0x21000024ff6ba2cc-lun-4 -> ../../sdf lrwxrwxrwx 1 root root 10 Feb 2 14:41 fc-0x21000024ff56a8a9-0x21000024ff6ba2cc-lun-4-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 Feb 2 14:41 fc---lun-0 -> ../../sda lrwxrwxrwx 1 root root 10 Feb 2 14:41 fc---lun-0-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Feb 2 14:41 fc---lun-0-part2 -> ../../sda2 lrwxrwxrwx 1 root root 9 Feb 2 14:41 pci-0000:02:00.0-scsi-0:2:0:0 -> ../../sda lrwxrwxrwx 1 root root 10 Feb 2 14:41 pci-0000:02:00.0-scsi-0:2:0:0-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Feb 2 14:41 pci-0000:02:00.0-scsi-0:2:0:0-part2 -> ../../sda2 lrwxrwxrwx 1 root root 9 Feb 2 14:41 pci-0000:04:00.1-fc-0x21000024ff6ba2cc-lun-0 -> ../../sdb lrwxrwxrwx 1 root root 10 Feb 2 14:41 pci-0000:04:00.1-fc-0x21000024ff6ba2cc-lun-0-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 Feb 2 14:41 pci-0000:04:00.1-fc-0x21000024ff6ba2cc-lun-1 -> ../../sdc lrwxrwxrwx 1 root root 10 Feb 2 14:41 pci-0000:04:00.1-fc-0x21000024ff6ba2cc-lun-1-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 Feb 2 14:41 pci-0000:04:00.1-fc-0x21000024ff6ba2cc-lun-2 -> ../../sdd lrwxrwxrwx 1 root root 10 Feb 2 14:41 pci-0000:04:00.1-fc-0x21000024ff6ba2cc-lun-2-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 Feb 2 14:41 pci-0000:04:00.1-fc-0x21000024ff6ba2cc-lun-3 -> ../../sde lrwxrwxrwx 1 root root 10 Feb 2 14:41 pci-0000:04:00.1-fc-0x21000024ff6ba2cc-lun-3-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 Feb 2 14:41 pci-0000:04:00.1-fc-0x21000024ff6ba2cc-lun-4 -> ../../sdf lrwxrwxrwx 1 root root 10 Feb 2 14:41 pci-0000:04:00.1-fc-0x21000024ff6ba2cc-lun-4-part1 -> ../../sdf1 Suggestions? Thank you, Steffan Cline steffan(a)hldns.com 602-793-0014 On 1/6/20, 6:46 AM, "Rainer Kamenik" <rainer.kamenik(a)tuwien.ac.at> wrote: Hello Steffan, We have a lot of boxes running PBs of storage for many years under Centos/LIO. We never got it running stable with prepackaged RPMs. TRedHat does not officially support the FC fabric modul. It is very sensitive - you have to use a adapter firmware version, kernel and targetcli-fb version that play together and are considered to be stable , but nobody on the mailling-list will be able or wants to tell you what is stable, cause there are maybe too few people that use LIO with the FC fabric module. It is mostly used with iSCSI and Infiniband fabrics. We had the same problems when we started to use it years ago and ended up installing the whole stuff on a minimal Centos installation from scratch (Vanilla Kernel, rtslib,configshell,targetcli, some python modules ...) The versions on CentOS that we consider as stable are: OS: Centos 7 with vanilla kernel 4.18.14 Target: tcm_qla2xxx Stable boot Firmware: 8.07.80 (Firmware Flash via qaucli !) Stable Qlogic driver for tcm_qla2xxx: 10.00.00.07-k (Kernel 4.18.14) targetcli: Custom Install (/w Python 2.7) rainer -- -------------------------------------------------------------------- Rainer Kamenik | rainer.kamenik(a)tuwien.ac.at IT Solutions - Server and Storage TU Wien - Operngasse 11/020, 1040 Wien T +43-1-58801-42077 --------------------------------------------------------------------

1 0

Re: Could not create Target in configFS
by Steffan Cline 06 Jan '20

06 Jan '20

I figure the type of HBA would be good to know. They're a Cavium QLogic BR-1860 QLE2662 which is supported from all I've read. Here are some details. # systool -c fc_host -v Class = "fc_host" Class Device = "host2" Class Device path = "/sys/devices/pci0000:00/0000:00:02.0/0000:04:00.0/host2/fc_host/host2" active_fc4s = "0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 " dev_loss_tmo = "60" fabric_name = "0x0" issue_lip = <store method only> max_npiv_vports = "255" maxframe_size = "0 bytes" node_name = "0x20008c7cffc7ef00" npiv_vports_inuse = "0" port_id = "0x000000" port_name = "0x10008c7cffc7ef00" port_state = "Linkdown" port_type = "Unknown" speed = "unknown" supported_classes = "Class 3" supported_fc4s = "0x00 0x00 0x01 0x00 0x00 0x00 0x00 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 " supported_speeds = "2 Gbit, 4 Gbit, 8 Gbit, 16 Gbit" symbolic_name = "QLogic-1860-2p | 3.2.25.1 | | | " tgtid_bind_type = "wwpn (World Wide Port Name)" uevent = vport_create = <store method only> vport_delete = <store method only> Device = "host2" Device path = "/sys/devices/pci0000:00/0000:00:02.0/0000:04:00.0/host2" uevent = "DEVTYPE=scsi_host" Thank you, Steffan Cline steffan(a)hldns.com 602-793-0014 On 1/5/20, 3:32 PM, "Steffan Cline" <steffan(a)hldns.com> wrote: Same error /> /qla2xxx create wwn=naa.10008c7cffc7dc01 Could not create Target in configFS No dice. It seems odd that there's zero error reporting to show what's failing. Thank you, Steffan Cline steffan(a)hldns.com 602-793-0014 On 1/5/20, 2:40 AM, "admin(a)commanderlake.net" <admin(a)commanderlake.net> wrote: Try qla2xxx/ create wwn=naa.10008c7cffc52800 with any of your naa wwn's. -----Original Message----- From: Steffan Cline Sent: Saturday, January 04, 2020 11:32 PM To: targetcli-fb-devel(a)lists.fedorahosted.org Subject: Re: Could not create Target in configFS Chris, Here is the output. /> qla2xxx/ create naa.10008c7cffc52800 naa.10008c7cffc52801 naa.10008c7cffc58b00 naa.10008c7cffc58b01 naa.10008c7cffc7dc00 naa.10008c7cffc7dc01 naa.10008c7cffc7ef00 naa.10008c7cffc7ef01 wwn= /> qla2xxx/ create Fabric cannot generate WWN but it was not given I saw something on one of many posts I ready where they used the mac address for ECOE. I'll give that a shot. Thank you, Steffan Cline steffan(a)hldns.com 602-793-0014 On 1/4/20, 3:41 PM, "Steffan Cline" <steffan(a)hldns.com> wrote: You caught me as I was just about to try FreeNAS again and wipe this clean. Where did you look for the allowed WWNs? I did an "ls" in targetcli and see qla2xxx listed there. When I do /qla2xxx info I can see the allowed and they didn't work. Is that what you're referring to? Thank you, Steffan Cline steffan(a)hldns.com 602-793-0014 On 1/4/20, 3:37 PM, "admin(a)commanderlake.net" <admin(a)commanderlake.net> wrote: I'm not sure about the qla2xxx module but I was getting the same error creating an srpt target because I assumed I had to enter the wwn of the initiator but then I had a look at srpt/ info and noticed the Allowed WWNs list, I tried the one listed and it worked. So the error "Could not create Target in configFS" must simply mean the wwn you entered is not valid rather than there being some other problem. -----Original Message----- From: Steffan Cline Sent: Saturday, January 04, 2020 8:46 PM To: targetcli-fb-devel(a)lists.fedorahosted.org Subject: Re: Could not create Target in configFS Could you please elaborate? The full details of what I tried are here: https://github.com/open-iscsi/targetcli-fb/issues/159 Is there something beyond that you're talking about? Thank you, Steffan Cline steffan(a)hldns.com 602-793-0014 On 1/4/20, 1:05 PM, "admin(a)commanderlake.net" <admin(a)commanderlake.net> wrote: I figured it out, it needs the targets wwn which can be found using the info command. -----Original Message----- From: Steffan Cline Sent: Saturday, January 04, 2020 7:36 PM To: targetcli-fb-devel(a)lists.fedorahosted.org Subject: Re: Could not create Target in configFS No such package I found however I do know that configfs is mounted correct according to the docs. # cat /proc/mounts | grep configfs configfs /sys/kernel/config configfs rw,nosuid,nodev,noexec,relatime 0 0 Thank you, Steffan Cline steffan(a)hldns.com 602-793-0014 On 1/4/20, 6:05 AM, "Chris Dos" <chris(a)chrisdos.com> wrote: I ran into a similar error for Libvirt a couple months back on Devuan (Debian). I needed to install a package for the configFS objects to be created. Looking through my history it was called cgroupfs-mount. Not sure if there a similar RPM? Chris On 1/4/20 3:19 AM, Steffan Cline wrote: > 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(a)hldns.com <mailto:steffan@hldns.com> > > 602-793-0014 > > > > > > On 12/30/19, 2:58 AM, "Steffan Cline" <steffan(a)hldns.com > <mailto:steffan@hldns.com>> wrote: > > > > A few additional points. > > > > In the kernel config: > CONFIG_CONFIGFS_FS=y > > > > Kernel: > 4.4.207-1.el7.elrepo.x86_64 > > > > Should I be able to create a directory in /sys/kernel/config/target/qla2xxxx? > # mkdir naa.|xxxxxxxxxxxxxxx| > mkdir: cannot create directory ‘naa.xxxxxxxxxxxxxxx’: Invalid argument > > > > I did notice that when I rebooted, there was no qla2xxx folder in > /sys/kernel/config/target/ but after trying to use targetcli, it did make one > so I'm not sure what else would cause it to fail. > > I’ve been working on this for a couple days and getting nowhere. > > > > Thank you, > > Steffan Cline > > steffan(a)hldns.com <mailto:steffan@hldns.com> > > 602-793-0014 > > > > > > On 12/29/19, 6:03 PM, "Steffan Cline" <steffan(a)hldns.com > <mailto:steffan@hldns.com>> wrote: > > > > I posted this in as an issue on Github but saw there’s a mailing list too and > figured I’d try this as well. > > > > I installed targetcli via yum on CentOS 7 and this is the version in the repo: > |# targetcli| > |targetcli shell version 2.1.fb49| > |Copyright 2011-2013 by Datera, Inc and others.| > |For help on commands, type 'help'.| > > > > I downloaded the .zip of the targetcli-fb version and tried it too from the > scripts folder and same results. > > Python: > |# python --version| > |Python 2.7.5| > > > > The error comes up when using create. > |/> /qla2xxx create naa.xxxxxxxxxxxxxxx| > |Could not create Target in configFS| > > > > Below is the info on my FC > |/> qla2xxx/ info| > |Fabric module name: qla2xxx| > |ConfigFS path: /sys/kernel/config/target/qla2xxx| > |Allowed WWN types: naa| > |Allowed WWNs list: naa.xxxxxxxxxxxxxxx, naa.xxxxxxxxxxxxxxx, > naa.xxxxxxxxxxxxxxx, naa.xxxxxxxxxxxxxxx, naa.xxxxxxxxxxxxxxx, > naa.xxxxxxxxxxxxxxx, naa.xxxxxxxxxxxxxxx, naa.xxxxxxxxxxxxxxx| > |Fabric module features: acls| > |Corresponding kernel module: tcm_qla2xxx| > > > > I have attached the log but don't see anything that really stands out. > > I checked per the > link http://www.linux-iscsi.org/wiki/Fibre_Channel#Enable_target_mode to > ensure that I have initiator mode disabled > > |# cat /sys/module/qla2xxx/parameters/qlini_mode| > |disabled| > > > > The kernel modules are loaded. > |# lsmod | grep qla2xxx| > |tcm_qla2xxx 32768 1| > |target_core_mod 335872 4 tcm_qla2xxx,iscsi_target_mod| > |qla2xxx 634880 1 tcm_qla2xxx| > |scsi_transport_fc 65536 3 bfa,qla2xxx,tcm_qla2xxx| > > > > configfs is mounted: > |# cat /proc/mounts | grep configfs| > |configfs /sys/kernel/config configfs rw,relatime 0 0| > > > > Does the error suggest it cannot access the configFS path? > > Suggestions? > > > > > > Thank you, > > Steffan Cline > > steffan(a)hldns.com <mailto:steffan@hldns.com> > > 602-793-0014 > > > > _______________________________________________ targetcli-fb-devel mailing > list -- targetcli-fb-devel(a)lists.fedorahosted.org To unsubscribe send an email > to targetcli-fb-devel-leave(a)lists.fedorahosted.org Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: > https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: > https://lists.fedorahosted.org/archives/list/targetcli-fb-devel@lists.fedor… > > > _______________________________________________ targetcli-fb-devel mailing > list -- targetcli-fb-devel(a)lists.fedorahosted.org To unsubscribe send an email > to targetcli-fb-devel-leave(a)lists.fedorahosted.org Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: > https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: > https://lists.fedorahosted.org/archives/list/targetcli-fb-devel@lists.fedor… > > > > _______________________________________________ > targetcli-fb-devel mailing list -- targetcli-fb-devel(a)lists.fedorahosted.org > To unsubscribe send an email to targetcli-fb-devel-leave(a)lists.fedorahosted.org > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedorahosted.org/archives/list/targetcli-fb-devel@lists.fedor… > _______________________________________________ targetcli-fb-devel mailing list -- targetcli-fb-devel(a)lists.fedorahosted.org To unsubscribe send an email to targetcli-fb-devel-leave(a)lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/targetcli-fb-devel@lists.fedor… _______________________________________________ targetcli-fb-devel mailing list -- targetcli-fb-devel(a)lists.fedorahosted.org To unsubscribe send an email to targetcli-fb-devel-leave(a)lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/targetcli-fb-devel@lists.fedor… _______________________________________________ targetcli-fb-devel mailing list -- targetcli-fb-devel(a)lists.fedorahosted.org To unsubscribe send an email to targetcli-fb-devel-leave(a)lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/targetcli-fb-devel@lists.fedor… _______________________________________________ targetcli-fb-devel mailing list -- targetcli-fb-devel(a)lists.fedorahosted.org To unsubscribe send an email to targetcli-fb-devel-leave(a)lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/targetcli-fb-devel@lists.fedor… _______________________________________________ targetcli-fb-devel mailing list -- targetcli-fb-devel(a)lists.fedorahosted.org To unsubscribe send an email to targetcli-fb-devel-leave(a)lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/targetcli-fb-devel@lists.fedor… _______________________________________________ targetcli-fb-devel mailing list -- targetcli-fb-devel(a)lists.fedorahosted.org To unsubscribe send an email to targetcli-fb-devel-leave(a)lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/targetcli-fb-devel@lists.fedor… _______________________________________________ targetcli-fb-devel mailing list -- targetcli-fb-devel(a)lists.fedorahosted.org To unsubscribe send an email to targetcli-fb-devel-leave(a)lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/targetcli-fb-devel@lists.fedor… _______________________________________________ targetcli-fb-devel mailing list -- targetcli-fb-devel(a)lists.fedorahosted.org To unsubscribe send an email to targetcli-fb-devel-leave(a)lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/targetcli-fb-devel@lists.fedor…

2 1

Could not create Target in configFS
by Steffan Cline 05 Jan '20

05 Jan '20

I posted this in as an issue on Github but saw there’s a mailing list too and figured I’d try this as well. I installed targetcli via yum on CentOS 7 and this is the version in the repo: # targetcli targetcli shell version 2.1.fb49 Copyright 2011-2013 by Datera, Inc and others. For help on commands, type 'help'. I downloaded the .zip of the targetcli-fb version and tried it too from the scripts folder and same results. Python: # python --version Python 2.7.5 The error comes up when using create. /> /qla2xxx create naa.xxxxxxxxxxxxxxx Could not create Target in configFS Below is the info on my FC /> qla2xxx/ info Fabric module name: qla2xxx ConfigFS path: /sys/kernel/config/target/qla2xxx Allowed WWN types: naa Allowed WWNs list: naa.xxxxxxxxxxxxxxx, naa.xxxxxxxxxxxxxxx, naa.xxxxxxxxxxxxxxx, naa.xxxxxxxxxxxxxxx, naa.xxxxxxxxxxxxxxx, naa.xxxxxxxxxxxxxxx, naa.xxxxxxxxxxxxxxx, naa.xxxxxxxxxxxxxxx Fabric module features: acls Corresponding kernel module: tcm_qla2xxx I have attached the log but don't see anything that really stands out. I checked per the link http://www.linux-iscsi.org/wiki/Fibre_Channel#Enable_target_mode to ensure that I have initiator mode disabled # cat /sys/module/qla2xxx/parameters/qlini_mode disabled The kernel modules are loaded. # lsmod | grep qla2xxx tcm_qla2xxx 32768 1 target_core_mod 335872 4 tcm_qla2xxx,iscsi_target_mod qla2xxx 634880 1 tcm_qla2xxx scsi_transport_fc 65536 3 bfa,qla2xxx,tcm_qla2xxx configfs is mounted: # cat /proc/mounts | grep configfs configfs /sys/kernel/config configfs rw,relatime 0 0 Does the error suggest it cannot access the configFS path? Suggestions? Thank you, Steffan Cline steffan(a)hldns.com 602-793-0014

3 13

Re: Latest versions of rtslib, configshell and targetcli
by TomK 15 Dec '19

15 Dec '19

Allright. Gave the -fb versions a try. 790037 -rw-r--r--. 1 root root 18100 Dec 14 23:22 scsi_target.lio 786433 drwxr-xr-x. 155 root root 12288 Dec 14 23:52 .. 787390 -rw-------. 1 root root 71 Dec 15 01:43 saveconfig.json They use json instead of the old .lio format for storing the config. And so won't let me restore my old config: /> restoreconfig /etc/target/scsi_target.lio Error parsing savefile: /etc/target/scsi_target.lio /> The -fb version however supports the force_pr_aptpl option: config# load /etc/target/scsi_target.lio Replace the current configuration with /etc/target/scsi_target.lio? [y/N] y *** Unknown attribute: storage fileio disk mdsesxip01-d01.img attribute force_pr_aptpl config# [root@nexus01 target]# grep -EiR force_pr_aptpl * targetcli-fb/build/targetcli-fb-2.1.51.2.g94d971d/targetcli/ui_backstore.py: 'force_pr_aptpl': ('number', 'If set to 1, force SPC-3 PR Activate Persistence across Target Power Loss operation.'), targetcli-fb/targetcli/ui_backstore.py: 'force_pr_aptpl': ('number', 'If set to 1, force SPC-3 PR Activate Persistence across Target Power Loss operation.'), So just want to bring up the question once more: which version of targetcli, rtslib and configshell did folks here find most compatible? Still the -fb version? Thx, TK On 4/7/2019 12:30 AM, TomK wrote: > On 3/28/2019 1:53 PM, J. Roeleveld wrote: >> On March 28, 2019 5:42:52 PM UTC, Christoph Hellwig >> <hch(a)infradead.org> wrote: >> >> On Fri, Mar 22, 2019 at 11:26:13PM -0400, TomK wrote: >> >> Hey All, >> >> I'm wondering if there are newer versions of the following >> packages still >> available and where I could download them from? The github link >> hasn't >> been updated in quite some time: >> >> >> I think you want to look for the versions with the -fb postfix. They >> aren't 100% compatible, but a lot more actively maintained. >> >> I've Cced the mailing list for the project, although I haven't gotten >> a single mail from that list for more than a year either.. >> >> ------------------------------------------------------------------------ >> targetcli-fb-devel mailing list -- >> targetcli-fb-devel(a)lists.fedorahosted.org >> To unsubscribe send an email to >> targetcli-fb-devel-leave(a)lists.fedorahosted.org >> Fedora Code of Conduct:https://getfedora.org/code-of-conduct.html >> List >> Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines >> List >> Archives:https://lists.fedorahosted.org/archives/list/targetcli-fb-devel@li… >> >> >> >> I have been using the -fb versions for a while now and not had any >> issues with them. >> You do need to use either the -fb versions for all, or the non-fb >> versions for all. Mix and match is not supported and can lead to >> strange results (if it even works). >> >> I also don't remember getting any emails on this list for a while either. >> >> -- >> Joost >> -- >> Sent from my Android device with K-9 Mail. Please excuse my brevity. > > Thanks all! > > If targetcli or the -fb version isn't maintained much anymore, I'm > wondering what else I could use in it's place? > -- Thx, TK.

1 0

Could not create SRPTFabricModule in configFS
by admin＠commanderlake.net 28 May '19

28 May '19

I’m trying to create an srpt target but I get “Could not create SRPTFabricModule in configFS”

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

targetcli-fb-devel