Your message dated Wed, 9 Jun 2010 20:55:13 +0530
with message-id <[email protected]>
and subject line Re: Bug#584999: open-iscsi: no diagnostic of broken targets
has caused the Debian Bug report #584999,
regarding open-iscsi: no diagnostic of broken targets
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
584999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584999
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: open-iscsi
Version: 2.0.871.3-1
Severity: normal
I tried to set up a Linux scsi target and the results I got with
open-iscsi were very disappointing.
I could discover the created target, log in but nothing would happen, no
device would get created.
It turned out that I had a typo in the name of the file to export as the
iscsi target. Surely there is something the iscsiadm could print other
than "login successful".
-- System Information:
Debian Release: squeeze/sid
APT prefers stable
APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages open-iscsi depends on:
ii libc6 2.11.1-2 Embedded GNU C Library: Shared lib
ii udev 0.125-7+lenny3 /dev/ and hotplug management daemo
open-iscsi recommends no packages.
open-iscsi suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Closing the bug report as it does not apply to open-iscsi
On Wednesday 09 Jun 2010 20:52:30 Ritesh Raj Sarraf wrote:
> On Wednesday 09 Jun 2010 16:53:47 Michal Suchanek wrote:
> > I guess the issue is that it is non-obvious if you log in into a target
> > that has no luns and thus no devices are created.
> >
> > If it's not the job of iscsiadm to diagnose issues with the iscsi target
> > then where are the issues supposed to be diagnosed?
>
> You can always be logged into the target, for example, to test if the auth
> models are working or not. It does not have to reflect a device appearance
> on the initiator.
>
> As for the typo on the target side that you mentioned in the initial post,
> it is the target that should error out on start-up.
>
> The iscsiadm utility's job is Discovery, Login, Rescan and a bunch of other
> stuff. It does not bother if the target that you discovered, has LUNs for
> your initiator or not.
>
> Nothing to do with the initiator.
>
> For the Linux iscsitarget, ietadm is what should do the diagnosis for the
> target.
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
