NetBSD Problem Report #46623

From martin@aprisoft.de  Sat Jun 23 11:03:10 2012
Return-Path: <martin@aprisoft.de>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
	by www.NetBSD.org (Postfix) with ESMTP id E322963B85F
	for <gnats-bugs@gnats.NetBSD.org>; Sat, 23 Jun 2012 11:03:09 +0000 (UTC)
Message-Id: <20120623110301.C30E0AF580E@emmas.aprisoft.de>
Date: Sat, 23 Jun 2012 13:03:01 +0200 (CEST)
From: martin@NetBSD.org
Reply-To: martin@NetBSD.org
To: gnats-bugs@gnats.NetBSD.org
Subject: iscsi failure to enumerate bus
X-Send-Pr-Version: 3.95

>Number:         46623
>Category:       kern
>Synopsis:       iscsi attaches a scsibus, but fails to enumerate LUNs with certain target
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    martin
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jun 23 11:05:00 +0000 2012
>Last-Modified:  Sat Jun 23 16:55:01 +0000 2012
>Originator:     Martin Husemann
>Release:        NetBSD 6.99.7
>Organization:
The NetBSD Foundation, Inc.
>Environment:
System: NetBSD whoever-brings-the-night.aprisoft.de 6.99.7 NetBSD 6.99.7 (MODULAR) #189: Mon Jun 18 11:01:49 CEST 2012 martin@emmas.aprisoft.de:/nelly/usr/src/sys/arch/sparc64/compile/MODULAR sparc64
Architecture: sparc64
Machine: sparc64
>Description:

I have a iscsi target where I can log in and get a new scsibus attached, but
no devices. Using "iscsictl report_luns" answers "No LUNs!".
Forcing "scsictl scsibus0 scan 0 1" makes an sd disk attach:
sd0 at scsibus0 target 0 lun 1: <NAS, iSCSI-VDISK, 0> disk fixed

>How-To-Repeat:
No idea, works with other targets.

>Fix:
I will have a look, but can't dig right now, filing as a reminder.

>Release-Note:

>Audit-Trail:

Responsible-Changed-From-To: kern-bug-people->martin
Responsible-Changed-By: martin@NetBSD.org
Responsible-Changed-When: Sat, 23 Jun 2012 11:10:05 +0000
Responsible-Changed-Why:
Probably hard to reproduce elsewhere, so I'll better debug it locally


From: "Michael L. Hitch" <mhitch@lightning.msu.montana.edu>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/46623: iscsi failure to enumerate bus
Date: Sat, 23 Jun 2012 07:03:51 -0600 (MDT)

 > I have a iscsi target where I can log in and get a new scsibus attached, but
 > no devices. Using "iscsictl report_luns" answers "No LUNs!".
 > Forcing "scsictl scsibus0 scan 0 1" makes an sd disk attach:
 > sd0 at scsibus0 target 0 lun 1: <NAS, iSCSI-VDISK, 0> disk fixed

    I think this is because the NetBSD probe will stop scanning when the 
 probe for an lun doesn't show a device.  So if lun 0 doesn't exist, the 
 scan stops.  See scsi_probe_bus() in sys/dev/scsipi/scsiconf.c.

 --
 Michael L. Hitch			mhitch@montana.edu
 Computer Consultant
 Information Technology Center
 Montana State University	Bozeman, MT	USA

From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/46623: iscsi failure to enumerate bus
Date: Sat, 23 Jun 2012 15:17:53 +0200

 On Sat, Jun 23, 2012 at 01:05:03PM +0000, Michael L. Hitch wrote:
 >     I think this is because the NetBSD probe will stop scanning when the 
 >  probe for an lun doesn't show a device.  So if lun 0 doesn't exist, the 
 >  scan stops.  See scsi_probe_bus() in sys/dev/scsipi/scsiconf.c.

 Oh, obvious once you look there ;-)
 Is this realy needed?

 I see how it is usefull if the failure to probe the device involves a
 timeout of some sorts, but can we tell those cases apart via different
 return values from the inquiry?


 Martin

From: Manuel Bouyer <bouyer@antioche.eu.org>
To: gnats-bugs@NetBSD.org
Cc: martin@NetBSD.org, gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
Subject: Re: kern/46623: iscsi failure to enumerate bus
Date: Sat, 23 Jun 2012 18:50:05 +0200

 On Sat, Jun 23, 2012 at 01:20:05PM +0000, Martin Husemann wrote:
 > The following reply was made to PR kern/46623; it has been noted by GNATS.
 > 
 > From: Martin Husemann <martin@duskware.de>
 > To: gnats-bugs@NetBSD.org
 > Cc: 
 > Subject: Re: kern/46623: iscsi failure to enumerate bus
 > Date: Sat, 23 Jun 2012 15:17:53 +0200
 > 
 >  On Sat, Jun 23, 2012 at 01:05:03PM +0000, Michael L. Hitch wrote:
 >  >     I think this is because the NetBSD probe will stop scanning when the 
 >  >  probe for an lun doesn't show a device.  So if lun 0 doesn't exist, the 
 >  >  scan stops.  See scsi_probe_bus() in sys/dev/scsipi/scsiconf.c.
 >  
 >  Oh, obvious once you look there ;-)
 >  Is this realy needed?
 >  
 >  I see how it is usefull if the failure to probe the device involves a
 >  timeout of some sorts, but can we tell those cases apart via different
 >  return values from the inquiry?

 Isn't lun 0 supposed to always exist ?

 -- 
 Manuel Bouyer <bouyer@antioche.eu.org>
      NetBSD: 26 ans d'experience feront toujours la difference
 --

>Unformatted:

Home	PR Database Search