linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ycsapo <ycsapo@mines.edu>
To: linux-admin@vger.kernel.org
Subject: iscsi woes
Date: Wed, 20 Sep 2006 14:52:08 -0600	[thread overview]
Message-ID: <4511A9F8.4010301@mines.edu> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,

I wonder if anyone has any idea what error 1006 means in:

iscsid: detected iSCSI connection (handle 0xf7d16600) error (1006) state (3)

This shows up in messages whenever I try to mkfs a volume on an SAN
connected via iSCSI. This is my setup:

My server (called screms) is a Dell PE1650 running Debian testing
(etch), kernel 2.6.15-1-686-smp, open-iscsi 1.0-485 as provided by the
official kernel package.

The Dell connects to the SAN through its builtin Gig-ethernet NIC (Intel
PRO/1000). This NIC is connected to a Cisco switch which connects to the
SAN through one of its Gig-ethernet fiber ports. The SAN is built by
Hitachi around a McData switch which has 2 fiber-channel and 2 fiber
ethernet iSCSI ports.

The server's IP address is 192.168.1.88; the SAN's IP address is
192.168.1.10. The network between the server and the SAN is segregated
to its own vlan.

I don't think any of these details are relevant, the same symptoms occur
with any other connection mode I was able to try so far. I've included
them here for completion's sake.

- From the server acting as an initiator, I can query the SAN:

screms:~# iscsiadm -m discovery -t sendtargets -p 192.168.1.10
[8664fe] 192.168.1.10:3260,-1 eui.50060e800044ddb2
[8664fc] 192.168.1.10:3260,-1 eui.50060e800044ddb0

I can also login to the controller:

screms:~# iscsiadm -m node -r 8664fc --login
screms:~# dmesg|tail
scsi29 : iSCSI Initiator over TCP/IP, v.0.3
  Vendor: HITACHI   Model: DF600F            Rev: 0000
  Type:   Direct-Access                      ANSI SCSI revision: 04
SCSI device sdf: 150994944 512-byte hdwr sectors (77309 MB)
SCSI device sdf: drive cache: write through
SCSI device sdf: 150994944 512-byte hdwr sectors (77309 MB)
SCSI device sdf: drive cache: write through
 sdf: unknown partition table
sd 29:0:0:0: Attached scsi disk sdf
sd 29:0:0:0: Attached scsi generic sg6 type 0
i.50060e800044ddb0

However when I try to mkfs the sdf device the process hangs while
writing inode tables at around 180/576. If I log out of the controller
the mkfs process does finish but the resulting fs is unusable.

Any takers?

Thanks!


- --
Yuri Csapo
Academic Computing & Networking
Colorado School of Mines
Green Center Rm 249
Phone:  (303) 273-3503
Fax:      (303) 273-3475
Email:   ycsapo@mines.edu

Please use the following link to open a service request:
http://helpdesk.mines.edu
===========================================
With a PC, I always felt limited
by the software available.
On Unix, I am limited only by my knowledge.
- --Peter J. Schoenster
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFEan4+RvQxW88fq4RAlbAAJ0RD/jIPpRaZSbTEpw+WPDrzY9bQACfRov5
fEqkD0D6RHCryT2JYFQ+fc8=
=f54e
-----END PGP SIGNATURE-----

             reply	other threads:[~2006-09-20 20:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-20 20:52 ycsapo [this message]
2006-10-10 19:04 ` iscsi woes - SOLVED Yuri Csapo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4511A9F8.4010301@mines.edu \
    --to=ycsapo@mines.edu \
    --cc=linux-admin@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).