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??
On 12/30/19, 2:58 AM, "Steffan Cline" <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.
On 12/29/19, 6:03 PM, "Steffan Cline" <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
602-793-0014
_______________________________________________
targetcli-fb-devel mailing list -- targetcli-fb-devel@lists.fedorahosted.org To
unsubscribe send an email to targetcli-fb-devel-leave@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.fedorahosted.org
_______________________________________________
targetcli-fb-devel mailing list -- targetcli-fb-devel@lists.fedorahosted.org To
unsubscribe send an email to targetcli-fb-devel-leave@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.fedorahosted.org