.\" This manpage has been automatically generated by docbook2man 
.\" from a DocBook document.  This tool can be found at:
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
.\" Please send any bug reports, improvements, comments, patches, 
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "SCSI_SEQUENTIAL_LUN_SCAN" "9" "09 October 2005" "" ""

.SH NAME
scsi_sequential_lun_scan \- sequentially scan a SCSI target
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
void scsi_sequential_lun_scan  (struct scsi_target * \fIstarget\fB, int \fIbflags\fB, int \fIlun0_res\fB, int \fIscsi_level\fB, int \fIrescan\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fIstarget\fB\fR
pointer to target structure to scan
.TP
\fB\fIbflags\fB\fR
black/white list flag for LUN 0
.TP
\fB\fIlun0_res\fB\fR
result of scanning LUN 0
.TP
\fB\fIscsi_level\fB\fR
-- undescribed --
.TP
\fB\fIrescan\fB\fR
-- undescribed --
.SH "DESCRIPTION"
.PP
Generally, scan from LUN 1 (LUN 0 is assumed to already have been
scanned) to some maximum lun until a LUN is found with no device
attached. Use the bflags to figure out any oddities.
.PP
Modifies sdevscan->lun.