[Pkg-iscsi-maintainers] Bug#584999: open-iscsi: no diagnostic of broken targets

[Michal Suchanek]

Excerpts from Ritesh Raj Sarraf's message of Wed Jun 09 17:22:30 +0200 2010:
> 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.

And then you if no device appears how do I determine why it did not
appear?

> 
> 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.

Yes, and it does so. However, that's on a different machine so there is
nothing you can do on the initiator to get this information. The lack of
any message about luns or no devices appearing is not a diagnostic in
itself.
> 
> 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.

Except that targets with no luns are quite useless.

I don't see any option for listing a target's luns so there is no way to
tell if the targets has no luns or attaching the target failed in some
unusual way.

> 
> Nothing to do with the initiator.
> 

Except it attaches the luns to the system. Otherwise it is completely
unrelated to the target and its luns.

Thanks

Michal
-- 
Michal Suchánek
michal.suchanek at ruk.cuni.cz
tel 224491810 fax 224491594
Univerzita Karlova v Praze
Ústav Výpočetní Techniky
Ovocný trh 3
Praha 1