From: Douglas Gilbert <dgilbert@interlog.com>
To: Raju <krishnamraju-e@hcl.com>
Cc: linux-scsi@vger.kernel.org,
"Nicholas A. Bellinger" <nab@linux-iscsi.org>
Subject: Re: mkdir: cannot create directory `/sys/kernel/config/target/iscsi': Invalid argument
Date: Fri, 16 Sep 2011 12:09:21 -0400 [thread overview]
Message-ID: <4E7374B1.8040502@interlog.com> (raw)
In-Reply-To: <loom.20110719T170144-482@post.gmane.org>
ping ....
Could some target folks please answer the following question?
I get the same show stopper on lk 3.0.4 :
root@test:/sys/kernel/config# mkdir target
mkdir: cannot create directory `target': No such file or directory
Doug Gilbert
On 11-07-19 11:17 AM, Raju wrote:
> Hi,
> I can't able create an iscsi target because of some problem in configfs:
>
>
> Below are the steps I followed in Debian Lenny(upgraded kernel to 2.6.39.2):
>
> #!/bin/sh
> # BEGIN CONFIG FOR CONFIGFS USAGE
> modprobe configfs
> mount -t configfs none /sys/kernel/config
> # END CONFIG FOR CONFIGFS USAGE
>
> # BEGIN CONFIGFS CODE FOR GENERIC TARGET ENGINE
> modprobe target_core_mod
> export CONFIGFS=/sys/kernel/config/
> export TARGET=/sys/kernel/config/target/core/
> export FABRIC=/sys/kernel/config/target/iscsi/
> # END CONFIGFS CODE FOR GENERIC TARGET ENGINE
>
> # START RAMDISK SUBSYSTEM PLUGIN OBJECTS
> mkdir -p $TARGET/rd_mcp_0/ramdisk
> echo rd_pages=32768> $TARGET/rd_mcp_0/ramdisk/control
> echo 1> $TARGET/rd_mcp_0/ramdisk/enable
> # END RAMDISK SUBSYSTEM PLUGIN OBJECTS
>
> # BEGIN CONFIGFS CODE FOR LINUX ISCSI TARGET (LIO-TARGET)
> DEF_IQN="iqn.2003-01.org.linux-iscsi.target.i686:sn.e475ed6fcdd0"
> # Define the first iSCSI Network Portal
> PORTAL1="10.0.0.1:3260"
> # The first mkdir(2) to $FABRIC will load iscsi_target_mod
> mkdir -p "$FABRIC/$DEF_IQN/tpgt_1/np/$PORTAL1"
> mkdir: cannot create directory `/sys/kernel/config/target/iscsi':
> Invalid argument
>
>
> AND KERNEL LOG:
>
> [10443.799266] CORE_HBA[0] - TCM Ramdisk HBA Driver v4.0 on Generic
> Target CoreStack v4.0.0-rc7-ml
> [10443.799272] CORE_HBA[0] - Attached Ramdisk HBA: 0 to Generic Target
> Core TCQDepth: 256 MaxSectors: 1024
> [10443.799278] CORE_HBA[1] - Attached HBA to Generic Target Core
> [10443.799329] Target_Core_ConfigFS: Allocated struct se_subsystem_dev:
> f4ee1000se_dev_su_ptr: f4e3e2c0
> [10443.800370] Missing rd_pages= parameter
> [10443.805761] Target_Core_ConfigFS: REGISTER-> group:f8552220 name:iscsi
> [10443.838505] target_core_get_fabric() failed for iscsi
> [10443.841826] Target_Core_ConfigFS: REGISTER-> group:f8552220 name:iscsi
> [10443.875313] target_core_get_fabric() failed for iscsi
> [10443.878496] Target_Core_ConfigFS: REGISTER-> group:f8552220 name:iscsi
> [10443.910039] target_core_get_fabric() failed for iscsi
> [10443.921684] Target_Core_ConfigFS: REGISTER-> group:f8552220 name:iscsi
> [10443.951926] target_core_get_fabric() failed for iscsi
>
>
>
> Please suggest any idea,
>
>
> Thanks,
> Raju.
next prev parent reply other threads:[~2011-09-16 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 15:17 mkdir: cannot create directory `/sys/kernel/config/target/iscsi': Invalid argument Raju
2011-09-16 16:09 ` Douglas Gilbert [this message]
2011-09-16 17:05 ` Douglas Gilbert
2011-09-16 19:29 ` Nicholas A. Bellinger
2011-09-16 19:41 ` James Bottomley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E7374B1.8040502@interlog.com \
--to=dgilbert@interlog.com \
--cc=krishnamraju-e@hcl.com \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox