Home / Browse / iSCSI Enterprise Target / Mail / Archive

iSCSI Enterprise Target

Email Archive: iscsitarget-devel (read-only)

Re: [Iscsitarget-devel] iscsi_trgt: ioctl(301) invalid ioctl cmd

From: Arne Redlich <agr@po...> - 2008-07-24 17:58

Am Donnerstag, den 24.07.2008, 14:38 +0200 schrieb Volker Jordan:
> Am Donnerstag, den 17.07.2008, 15:47 -0400 schrieb Ming Zhang:
> > On Thu, 2008-07-17 at 08:25 +0200, Volker Jordan wrote:
> > > Hi,
> > > 
> > > I try to get my LTO library working with ISCSI.
> > > 
> > > On my debian system I installed open-iscsi and download the current
> > > version of iscsitarget.
> > > 
> > > When I start iscsitarget
> > > 
> > > /etc/init.d/iscsitarget start
> > > 
> > > I get
> > > 
> > > iSCSI Enterprise Target Software - version 0.4.16
> > > iscsi_trgt: Registered io type fileio
> > > iscsi_trgt: Registered io type blockio
> > > iscsi_trgt: Registered io type nullio
> > > iscsi_trgt: ioctl(301) invalid ioctl cmd 48086904
> > 
> > 
> > your CPU arch?
> > 
> 
> i686 Intel Xeon

Are you running a 32-bit userland on a 64-bit kernel?
> 
> > 
> > > 
> > > /etc/ietd.conf is
> > > 
> > > Target lto2library.local:iscsilto2
> > > Lun 0 Path=/dev/sg1,Type=blockio
> > 
> > 
> > this is wrong. u can ONLY use disk like device with iet. library is not
> > supported.
> > 
> 
> Is a single LTO drive supportet?

No, only (virtual) disk devices are supported.

HTH,
Arne

Thread View

Thread	Author	Date
[Iscsitarget-devel] iscsi_trgt: ioctl(301) invalid ioctl cmd	Volker Jordan <v_jordan@we...>

Re: [Iscsitarget-devel] iscsi_trgt: ioctl(301) invalid ioctl cmd

From: Ming Zhang <blackmagic02881@gm...> - 2008-07-17 19:46

On Thu, 2008-07-17 at 08:25 +0200, Volker Jordan wrote:
> Hi,
> 
> I try to get my LTO library working with ISCSI.
> 
> On my debian system I installed open-iscsi and download the current
> version of iscsitarget.
> 
> When I start iscsitarget
> 
> /etc/init.d/iscsitarget start
> 
> I get
> 
> iSCSI Enterprise Target Software - version 0.4.16
> iscsi_trgt: Registered io type fileio
> iscsi_trgt: Registered io type blockio
> iscsi_trgt: Registered io type nullio
> iscsi_trgt: ioctl(301) invalid ioctl cmd 48086904


your CPU arch?


> 
> /etc/ietd.conf is
> 
> Target lto2library.local:iscsilto2
> Lun 0 Path=/dev/sg1,Type=blockio


this is wrong. u can ONLY use disk like device with iet. library is not
supported.


> IncomingUser iscsi iscsi
> Alias Lto2_Library
> 
> When I start open-iscsi I get
> 
> Loading iSCSI transport class v2.0-724.
> iscsi: registered transport (tcp)
> iscsi: registered transport (iser)
> 
> Trying to connect 
> 
> iscsiadm -m node -T lto2library.local:iscsilto2 --portal=IP --login
> 
> gives me
> 
> iscsiadm: initiator reported error (5 - encountered iSCSI login failure)
> 
> and the log
> 
> scsi22 : iSCSI Initiator over TCP/IP
> iscsi_trgt: ioctl(301) invalid ioctl cmd c06c690d
> 
> What are those ioctl errors?
> 
> Regards
> 
> Volker Jordan
> 
> 
> 
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Iscsitarget-devel mailing list
> Iscsitarget-devel@...
> https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel
-- 
Ming Zhang


@#$%^ purging memory... (*!%
http://blackmagic02881.wordpress.com/
http://www.linkedin.com/in/blackmagic02881
--------------------------------------------

Re: [Iscsitarget-devel] iscsi_trgt: ioctl(301) invalid ioctl cmd

From: Volker Jordan <v_jordan@we...> - 2008-07-24 12:38

Am Donnerstag, den 17.07.2008, 15:47 -0400 schrieb Ming Zhang:
> On Thu, 2008-07-17 at 08:25 +0200, Volker Jordan wrote:
> > Hi,
> > 
> > I try to get my LTO library working with ISCSI.
> > 
> > On my debian system I installed open-iscsi and download the current
> > version of iscsitarget.
> > 
> > When I start iscsitarget
> > 
> > /etc/init.d/iscsitarget start
> > 
> > I get
> > 
> > iSCSI Enterprise Target Software - version 0.4.16
> > iscsi_trgt: Registered io type fileio
> > iscsi_trgt: Registered io type blockio
> > iscsi_trgt: Registered io type nullio
> > iscsi_trgt: ioctl(301) invalid ioctl cmd 48086904
> 
> 
> your CPU arch?
> 

i686 Intel Xeon

> 
> > 
> > /etc/ietd.conf is
> > 
> > Target lto2library.local:iscsilto2
> > Lun 0 Path=/dev/sg1,Type=blockio
> 
> 
> this is wrong. u can ONLY use disk like device with iet. library is not
> supported.
> 

Is a single LTO drive supportet?

Re: [Iscsitarget-devel] iscsi_trgt: ioctl(301) invalid ioctl cmd

From: Arne Redlich <agr@po...> - 2008-07-24 17:58

Am Donnerstag, den 24.07.2008, 14:38 +0200 schrieb Volker Jordan:
> Am Donnerstag, den 17.07.2008, 15:47 -0400 schrieb Ming Zhang:
> > On Thu, 2008-07-17 at 08:25 +0200, Volker Jordan wrote:
> > > Hi,
> > > 
> > > I try to get my LTO library working with ISCSI.
> > > 
> > > On my debian system I installed open-iscsi and download the current
> > > version of iscsitarget.
> > > 
> > > When I start iscsitarget
> > > 
> > > /etc/init.d/iscsitarget start
> > > 
> > > I get
> > > 
> > > iSCSI Enterprise Target Software - version 0.4.16
> > > iscsi_trgt: Registered io type fileio
> > > iscsi_trgt: Registered io type blockio
> > > iscsi_trgt: Registered io type nullio
> > > iscsi_trgt: ioctl(301) invalid ioctl cmd 48086904
> > 
> > 
> > your CPU arch?
> > 
> 
> i686 Intel Xeon

Are you running a 32-bit userland on a 64-bit kernel?
> 
> > 
> > > 
> > > /etc/ietd.conf is
> > > 
> > > Target lto2library.local:iscsilto2
> > > Lun 0 Path=/dev/sg1,Type=blockio
> > 
> > 
> > this is wrong. u can ONLY use disk like device with iet. library is not
> > supported.
> > 
> 
> Is a single LTO drive supportet?

No, only (virtual) disk devices are supported.

HTH,
Arne

[Iscsitarget-devel] Compile error Kernel 2.6.26

From: Volker Jordan <v_jordan@we...> - 2008-07-25 07:49

Hi,

under kernel version 2.6.26 iscsitarget cant be compiled:


make[1]: Entering directory `/usr/src/linux-2.6.26'
  CC [M]  /usr/src/iscsitarget-0.4.16/kernel/block-io.o
In file included from /usr/src/iscsitarget-0.4.16/kernel/block-io.c:12:
include/linux/parser.h:32: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘match_strlcpy’

There is a change in parser.h and the size_t.

Is that a kernel error or a iscsi error?

Regards

Volker Jordan

Re: [Iscsitarget-devel] iscsi_trgt: ioctl(301) invalid ioctl cmd

From: Volker Jordan <v_jordan@we...> - 2008-07-25 08:33

Am Donnerstag, den 24.07.2008, 19:58 +0200 schrieb Arne Redlich:

> > > > iSCSI Enterprise Target Software - version 0.4.16
> > > > iscsi_trgt: Registered io type fileio
> > > > iscsi_trgt: Registered io type blockio
> > > > iscsi_trgt: Registered io type nullio
> > > > iscsi_trgt: ioctl(301) invalid ioctl cmd 48086904
> > > 
> > > 
> > > your CPU arch?
> > > 
> > 
> > i686 Intel Xeon
> 
> Are you running a 32-bit userland on a 64-bit kernel?
> > 
No.

Switching to fileio and a mounted filesystem makes no difference

Target lto2library.local:iscsilto2
Lun 0 Path=/mnt/filesystem,Type=fileio
Alias Lto2_Library

Re: [Iscsitarget-devel] Compile error Kernel 2.6.26

From: Arne Redlich <agr@po...> - 2008-07-25 18:13

Am Freitag, den 25.07.2008, 09:49 +0200 schrieb Volker Jordan:
> Hi,
> 
> under kernel version 2.6.26 iscsitarget cant be compiled:
> 
> 
> make[1]: Entering directory `/usr/src/linux-2.6.26'
>   CC [M]  /usr/src/iscsitarget-0.4.16/kernel/block-io.o
> In file included from /usr/src/iscsitarget-0.4.16/kernel/block-io.c:12:
> include/linux/parser.h:32: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘match_strlcpy’
> 
> There is a change in parser.h and the size_t.
> 
> Is that a kernel error or a iscsi error?

I think it's fixed in the svn repository.

HTH,
Arne

Re: [Iscsitarget-devel] iscsi_trgt: ioctl(301) invalid ioctl cmd

From: Arne Redlich <agr@po...> - 2008-07-25 18:15

Am Freitag, den 25.07.2008, 10:33 +0200 schrieb Volker Jordan:
> Am Donnerstag, den 24.07.2008, 19:58 +0200 schrieb Arne Redlich:
> 
> > > > > iSCSI Enterprise Target Software - version 0.4.16
> > > > > iscsi_trgt: Registered io type fileio
> > > > > iscsi_trgt: Registered io type blockio
> > > > > iscsi_trgt: Registered io type nullio
> > > > > iscsi_trgt: ioctl(301) invalid ioctl cmd 48086904
> > > > 
> > > > 
> > > > your CPU arch?
> > > > 
> > > 
> > > i686 Intel Xeon
> > 
> > Are you running a 32-bit userland on a 64-bit kernel?
> > > 
> No.
> 
> Switching to fileio and a mounted filesystem makes no difference

Of course not, because you cannot export a mounted filesystem, only
files in a filesystem (using fileio) or block devices (using block and
fileio). And the latter must not be mounted either.

HTH,
Arne

> Target lto2library.local:iscsilto2
> Lun 0 Path=/mnt/filesystem,Type=fileio
> Alias Lto2_Library

Re: [Iscsitarget-devel] iscsi_trgt: ioctl(301) invalid ioctl cmd

From: Volker Jordan <v_jordan@we...> - 2008-07-28 14:04

Am Freitag, den 25.07.2008, 20:15 +0200 schrieb Arne Redlich:
> Am Freitag, den 25.07.2008, 10:33 +0200 schrieb Volker Jordan:
> > Am Donnerstag, den 24.07.2008, 19:58 +0200 schrieb Arne Redlich:
> > 
> > > > > > iSCSI Enterprise Target Software - version 0.4.16
> > > > > > iscsi_trgt: Registered io type fileio
> > > > > > iscsi_trgt: Registered io type blockio
> > > > > > iscsi_trgt: Registered io type nullio
> > > > > > iscsi_trgt: ioctl(301) invalid ioctl cmd 48086904
> > > > > 
> > > > > 
> > > > > your CPU arch?
> > > > > 
> > > > 
> > > > i686 Intel Xeon
> > > 
> > > Are you running a 32-bit userland on a 64-bit kernel?
> > > > 
> > No.
> > 
> > Switching to fileio and a mounted filesystem makes no difference
> 
> Of course not, because you cannot export a mounted filesystem, only
> files in a filesystem (using fileio) or block devices (using block and
> fileio). And the latter must not be mounted either.
> 
Now I am running ietd with debugging mode an there is an error:

Can't create a logical unit 22 1 0 Path=/dev/sdd1,Type=fileio

What can I do?

Re: [Iscsitarget-devel] iscsi_trgt: ioctl(301) invalid ioctl cmd

From: Ross S. W. Walker <RWalker@me...> - 2008-07-28 14:16

Volker Jordan wrote:
> Am Freitag, den 25.07.2008, 20:15 +0200 schrieb Arne Redlich:
> > Am Freitag, den 25.07.2008, 10:33 +0200 schrieb Volker Jordan:
> > > Am Donnerstag, den 24.07.2008, 19:58 +0200 schrieb Arne Redlich:
> > > 
> > > > > > > iSCSI Enterprise Target Software - version 0.4.16
> > > > > > > iscsi_trgt: Registered io type fileio
> > > > > > > iscsi_trgt: Registered io type blockio
> > > > > > > iscsi_trgt: Registered io type nullio
> > > > > > > iscsi_trgt: ioctl(301) invalid ioctl cmd 48086904
> > > > > > 
> > > > > > 
> > > > > > your CPU arch?
> > > > > > 
> > > > > 
> > > > > i686 Intel Xeon
> > > > 
> > > > Are you running a 32-bit userland on a 64-bit kernel?
> > > > > 
> > > No.
> > > 
> > > Switching to fileio and a mounted filesystem makes no difference
> > 
> > Of course not, because you cannot export a mounted filesystem, only
> > files in a filesystem (using fileio) or block devices 
> (using block and
> > fileio). And the latter must not be mounted either.
> > 
> Now I am running ietd with debugging mode an there is an error:
> 
> Can't create a logical unit 22 1 0 Path=/dev/sdd1,Type=fileio
> 
> What can I do?

Is /dev/sdd1 mounted somewhere?

You cannot use a storage medium that is used by another process OR
the kernel itself.

-Ross

______________________________________________________________________
This e-mail, and any attachments thereto, is intended only for use by
the addressee(s) named herein and may contain legally privileged
and/or confidential information. If you are not the intended recipient
of this e-mail, you are hereby notified that any dissemination,
distribution or copying of this e-mail, and any attachments thereto,
is strictly prohibited. If you have received this e-mail in error,
please immediately notify the sender and permanently delete the
original and any copy or printout thereof.

Re: [Iscsitarget-devel] iscsi_trgt: ioctl(301) invalid ioctl cmd

From: Volker Jordan <v_jordan@we...> - 2008-07-28 14:25

Am Montag, den 28.07.2008, 10:16 -0400 schrieb Ross S. W. Walker:

> > > > > > > > iSCSI Enterprise Target Software - version 0.4.16
> > > > > > > > iscsi_trgt: Registered io type fileio
> > > > > > > > iscsi_trgt: Registered io type blockio
> > > > > > > > iscsi_trgt: Registered io type nullio
> > > > > > > > iscsi_trgt: ioctl(301) invalid ioctl cmd 48086904
> > > > > > > 
> > > > > > > 
> > > > > > > your CPU arch?
> > > > > > > 
> > > > > > 
> > > > > > i686 Intel Xeon
> > > > > 
> > > > > Are you running a 32-bit userland on a 64-bit kernel?
> > > > > > 
> > > > No.
> > > > 
> > > > Switching to fileio and a mounted filesystem makes no difference
> > > 
> > > Of course not, because you cannot export a mounted filesystem, only
> > > files in a filesystem (using fileio) or block devices 
> > (using block and
> > > fileio). And the latter must not be mounted either.
> > > 
> > Now I am running ietd with debugging mode an there is an error:
> > 
> > Can't create a logical unit 22 1 0 Path=/dev/sdd1,Type=fileio
> > 
> > What can I do?
> 
> Is /dev/sdd1 mounted somewhere?
> 
> You cannot use a storage medium that is used by another process OR
> the kernel itself.
> 
No, sdd1 is not mounted. It is part of a multipath device. But changing
the path to /dev/mapper/mpath1p1 makes no difference.

Re: [Iscsitarget-devel] iscsi_trgt: ioctl(301) invalid ioctl cmd

From: Ross S. W. Walker <RWalker@me...> - 2008-07-28 14:44

Volker Jordan wrote:
> Am Montag, den 28.07.2008, 10:16 -0400 schrieb Ross S. W. Walker:
> > 
> > Is /dev/sdd1 mounted somewhere?
> > 
> > You cannot use a storage medium that is used by another process OR
> > the kernel itself.
> > 
> 
> No, sdd1 is not mounted. It is part of a multipath device. But changing
> the path to /dev/mapper/mpath1p1 makes no difference.
> 

Errno 22 stands for EINVAL (error in value) or "garbage in", what is your ietd.conf?

And can you give an ls -l of the devices in question?

Can you access the device normally? Make a file system on it and mount it?

-Ross

______________________________________________________________________
This e-mail, and any attachments thereto, is intended only for use by
the addressee(s) named herein and may contain legally privileged
and/or confidential information. If you are not the intended recipient
of this e-mail, you are hereby notified that any dissemination,
distribution or copying of this e-mail, and any attachments thereto,
is strictly prohibited. If you have received this e-mail in error,
please immediately notify the sender and permanently delete the
original and any copy or printout thereof.

Re: [Iscsitarget-devel] iscsi_trgt: ioctl(301) invalid ioctl cmd

From: Volker Jordan <v_jordan@we...> - 2008-07-28 15:11

Am Montag, den 28.07.2008, 10:44 -0400 schrieb Ross S. W. Walker:
> 
> Errno 22 stands for EINVAL (error in value) or "garbage in", what is your ietd.conf?
> 
Target lto2library.local:iscsilto2
Lun 0 Path=/dev/mapper/mpath1p1,Type=fileio
Alias Lto2_Library
MaxConnections 1

> And can you give an ls -l of the devices in question?
> 

ls -l /dev/mapper/mpath1p1
brw-rw---- 1 root disk 254, 2 2008-07-28 12:01 /dev/mapper/mpath1p1

> Can you access the device normally? Make a file system on it and mount it?
> 
Yes I can.

mount /dev/mapper/mpath1p1 /mnt/iscsi/

Re: [Iscsitarget-devel] iscsi_trgt: ioctl(301) invalid ioctl cmd

From: Ross S. W. Walker <RWalker@me...> - 2008-07-28 15:27

Volker Jordan wrote:
> Am Montag, den 28.07.2008, 10:44 -0400 schrieb Ross S. W. Walker:
> > 
> > Errno 22 stands for EINVAL (error in value) or "garbage in", what is your ietd.conf?
> > 
> 
> Target lto2library.local:iscsilto2
> Lun 0 Path=/dev/mapper/mpath1p1,Type=fileio
> Alias Lto2_Library
> MaxConnections 1

Well if that is your ietd.conf exactly, then the problem is that
you didn't indent the target options with whitespace:

Target lto2library.local:iscsilto2
 Lun 0 Path=/dev/mapper/mpath1p1,Type=fileio
 Alias Lto2_Library
 MaxConnections 1

At least 1 whitespace indent is needed, don't worry about MaxConnections
IET doesn't do multiple connections per session so it is always 1 (it can
do multiple sessions by the same initiator though for fail-over).

Don't worry about the Alias option either as it isn't used.

Some options that you should/could have are:

 InitialR2T              No
 ImmediateData           Yes
 MaxRecvDataSegmentLength 8192
 MaxXmitDataSegmentLength 65536
 MaxBurstLength          262144
 FirstBurstLength        65536
 MaxOutstandingR2T       8
 HeaderDigest            None
 DataDigest              None
 Wthreads                8
 QueuedCommands          64

I have found these provide decent performance for mixed workloads to
a variety of initiators.

> > And can you give an ls -l of the devices in question?
> > 
> 
> ls -l /dev/mapper/mpath1p1
> brw-rw---- 1 root disk 254, 2 2008-07-28 12:01 /dev/mapper/mpath1p1
> 
> > Can you access the device normally? Make a file system on it and mount it?
> > 
> 
> Yes I can.
> 
> mount /dev/mapper/mpath1p1 /mnt/iscsi/
> 

Ok, well it's probably the whitespace indent, indent and try again.

-Ross

______________________________________________________________________
This e-mail, and any attachments thereto, is intended only for use by
the addressee(s) named herein and may contain legally privileged
and/or confidential information. If you are not the intended recipient
of this e-mail, you are hereby notified that any dissemination,
distribution or copying of this e-mail, and any attachments thereto,
is strictly prohibited. If you have received this e-mail in error,
please immediately notify the sender and permanently delete the
original and any copy or printout thereof.