--neYutvxvOLaeuPCA
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Sep 25, 2007 at 07:58:05PM +0200, nbap@gmx.net wrote:
> > > I am using iscsi-target "netbsd-iscsi 20060727" from pkgsrc
> > > on 4.0_BETA2 with an AIX 5.3 software initiator.
> > > It seems that AIX wants SCSI write and verify - I get an
> > >=20
> > > UNKNOWN OPCODE 0x2e=20
> > >=20
> > > when using the AIX hdisk.
> > >=20
> > > Is this correct or am I misinterpreting the message?
> > > Would it be (easily) possible to add support for 0x2e?
> >=20
> > Note: unless you're seeing an error in the initiator's logs, this isn't=
=20
> > fatal.
>=20
> Sorry I missed that - there are indeed (fatal) errors on the
> initiators side. Just to give an example from AIX "errpt -a":
>=20
>=20
> LABEL:          SC_DISK_ERR3
> IDENTIFIER:     C62E1EB7
>=20
> Date/Time:       Fri Sep 21 14:48:09 CEST 2007
> Sequence Number: 51001
> Machine Id:      0042303A4C00
> Node Id:         eckwand
> Class:           H
> Type:            PERM
> Resource Name:   hdisk26        =20
> Resource Class:  disk
> Resource Type:   osdisk
> Location:       =20
> VPD:            =20
>         Manufacturer................NetBSD =20
>         Machine Type and Model......NetBSD iSCSI   =20
>         Part Number.................
>         ROS Level and ID............30202020
>         Serial Number...............
>         EC Level....................
>         FRU Number..................
>         Device Specific.(Z0)........00000300FB000060
>         Device Specific.(Z1)........
>         Device Specific.(Z2)........
>         Device Specific.(Z3)........
>         Device Specific.(Z4)........
>         Device Specific.(Z5)........
>         Device Specific.(Z6)........
>=20
> Description
> DISK OPERATION ERROR
>=20
> Probable Causes
> DASD DEVICE
> STORAGE DEVICE CABLE
>=20
> Failure Causes
> DISK DRIVE
> DISK DRIVE ELECTRONICS
> STORAGE DEVICE CABLE
>=20
>         Recommended Actions
>         PERFORM PROBLEM DETERMINATION PROCEDURES
>=20
> Detail Data
> PATH ID
>            0
> [...]
>=20
> (more details on request)

Can you get a sense code, and ASC and ASCQ?

Does the initiator stop accessing the disk?

That log message looks like we might have the sense info wrong on reply.

Take care,

Bill

--neYutvxvOLaeuPCA
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (NetBSD)

iD8DBQFG+VFDWz+3JHUci9cRAozBAJ9/h4UgK9qRtlHl/bhAQkcYJZ0VGgCdHhy0
qQWGYK2Um2VzyUm/BvLXFZA=
=Gmdd
-----END PGP SIGNATURE-----

--neYutvxvOLaeuPCA--