Subject: Re: iSCSI initiator CHAP failure
To: Chavdar Ivanov <email@example.com>
From: Alistair Crooks <firstname.lastname@example.org>
Date: 11/27/2007 22:21:39
On Tue, Nov 27, 2007 at 03:27:00PM +0000, Chavdar Ivanov wrote:
> On Nov 27, 2007 10:43 AM, Alistair Crooks <email@example.com> wrote:
> > On Mon, Nov 26, 2007 at 05:29:55PM -0600, Jay Nelson wrote:
> > > Initiator command is:
> > >
> > > 'iscsifs -u jdn -h acp /mnt'
> > >
> > > What did I overlook?
> > Nothing except very weird syntax on the part of the iSCSI target.
> > One of the things on my TODO list is to clean this area up
> > entirely.
> > Regards,
> > Alistair
> While we are on the topic of iSCSI target, I have been having problem
> for quite some time to use two targets on one NetBDS-current machine
> from a W2K3 initiator (latest version from Microsoft; tried also
> StarWind from RocketDivision, but this simply froze with error
> messages from the target, but that is another story).
> I can connect to one of the targets - no problem; I can log on the
> second one and it appears in the disk list, but any operation on it
> fails with an error message in the event log, stating that it cannot
> be completed, as the second one is a redundancy path for the first.
> If I log out from the second target, I can connect and use it from
> another server (in this case Windows 2008 RC0), so there is no problem
> as far as I can see on the NetBSD system.
> Any ideas? The targets are whole 80GB IDE disks - just /dev/wd?d is in
> the spec. No authentication is used for now.
I know it's no consolation, but this is a known bug, and we (Greg
Oster and myself) are working on it right now. I know Greg made some
progress today, so I'm hopeful in general that we can squish this