From: "Nicholas A. Bellinger" <nab@risingtidesystems.com>
To: dgilbert@interlog.com
Cc: linux-scsi@vger.kernel.org, Jerome Martin <jxm@risingtidesystems.com>
Subject: Re: mkdir: cannot create directory `/sys/kernel/config/target/iscsi': Invalid argument
Date: Fri, 16 Sep 2011 12:29:01 -0700 [thread overview]
Message-ID: <1316201341.12820.370.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <4E7381BF.7020802@interlog.com>
On Fri, 2011-09-16 at 13:05 -0400, Douglas Gilbert wrote:
> Well I can answer my own question.
> configfs doesn't seem to be mounted at /sys/kernel/config
> and even when it is, superuser cannot create a directory
> there. So mount configfs somewhere else:
>
> mount -t configfs none /tmp/config
This should actually be:
mount -t configfs configfs /sys/kernel/config
>
> Then in reference to this page:
> http://linux-iscsi.org/wiki/Target/configFS
>
> change this line:
> export TARGET=/sys/kernel/config/target/core/
> to
> export TARGET=/tmp/config/target/core/
> then continue.
>
> BTW The target infrastructure creates this noise in the log:
> "Unable to load target_core_stgt"
> There is no such module that I can see.
>
>
> And I still can't do what I want: to use the target
> infrastructure to make a disk image in a file look
> like a SCSI device on the local machine. No iSCSI,
> SRP, FCxxx, SAS, UAS nor SOP ... just _SCSI_ !!
>
I just sent an email off-list with the various wiki pointers to tcm_loop
for local SCSI LLD device access.
Using the rtsadmin shell is definately the easiest way to configure
target core backends and tcm_loop target ports. Installing this from
www.risingtidesystems.com/git source is still a bit challenging atm, but
we'd be happy to send you an rtsadmin-frozen build offlist for your own
use. Please let us know if you prefer rpm or debs. ;)
--nab
next prev parent reply other threads:[~2011-09-16 19:29 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
2011-09-16 17:05 ` Douglas Gilbert
2011-09-16 19:29 ` Nicholas A. Bellinger [this message]
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=1316201341.12820.370.camel@haakon2.linux-iscsi.org \
--to=nab@risingtidesystems.com \
--cc=dgilbert@interlog.com \
--cc=jxm@risingtidesystems.com \
--cc=linux-scsi@vger.kernel.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