Cloned for the iscsi-initiator-utils component.

+++ This bug was initially created as a clone of Bug #159708 +++

Description of problem:
After configuring a Tape LUN, iscsi-ls -l shows the device mapped to. But it
also gives some error message as well. If any IO is executed on this tape, the
linux host panics and crashes.

Version-Release number of selected component (if applicable):
- kernel-smp-2.6.9-11.EL
- kernel-smp-devel-2.6.9-11.EL

How reproducible:
Always reproducible

Steps to Reproduce:
1. Configured a tape (Quantum ATL1500) LUN on MDS 9216
2. Execution of iscsi-ls -l gives the following output:
[root@cnitin-linux-6 ~]# iscsi-ls -l
*******************************************************************************
SFNet iSCSI Driver Version ...4:0.1.11(12-Jan-2005)
*******************************************************************************
TARGET NAME             : iqn.2004-04.com.cisco.cnitin-tape-drive-2
TARGET ALIAS            : 
HOST ID                 : 0
BUS ID                  : 0
TARGET ID               : 0
TARGET ADDRESS          : 10.1.1.80:3260,12416
SESSION STATUS          : ESTABLISHED AT Wed Jun  1 16:00:00 IST 2005
SESSION ID              : ISID 00023d000001 TSIH 3080

DEVICE DETAILS:
---------------
LUN ID : 0
  Vendor: QUANTUM  Model: SuperDLT1        Rev: 2323
  Type:   Sequential-Access                ANSI SCSI revision: 04
open class /sys/block/st0 failed: No such file or directory
  page83 type0: 
open class /sys/block/st0 failed: No such file or directory
  page80: 
  Device: /dev/st0
*******************************************************************************

  
Actual results:
iscsi-ls -l gives errors when a tape LUN is configured.
Also, an IO on tape device displayed panics the system.


Expected results:
iscsi-ls -l should display the tape details without errors. An IO on tape should
not panic the system.