-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Christie wrote:
Lars Schimmer wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
In trying to get iSCSI running here, I stumble upon problems..
I upgraded my system to a recent 2.6.26 kernel from debian and the
open-iSCSO package
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lars Schimmer wrote:
Hi!
In trying to get iSCSI running here, I stumble upon problems..
I upgraded my system to a recent 2.6.26 kernel from debian and the
open-iSCSO package 2.0.870~rc3-0.3 from debian.
But it keeps failing to start iSCSI,
On Mon, Dec 08, 2008 at 12:45:11PM -0800, Kmec wrote:
IIRC IOmeter for Linux had some issues.. related to queue depth maybe? So
you should use other tools than IOmeter on Linux. Dunno if that problem is
already fixed or if there is a patch available for IOmeter for Linux..
Oh,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
That is the 20 MB access Lun used for in-band management with the MD3000i
controller. Its not a proper scsi LUN so you might want those error messages.
Yes, but why do I see two of them and NO configured LUN with 2000 GB?
Mike Christie wrote:
What firmware do you have, and did yo just start seeing these with a
target firmware upgrade or a iscsi/ubuntu upgrade?
I can't find it, but I believe we are running version 4.0.1 of the
Equallogic firmware, but we were originally running 3.3.1 and saw
problems with that
Lars Schimmer wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Christie wrote:
Lars Schimmer wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
In trying to get iSCSI running here, I stumble upon problems..
I upgraded my system to a recent 2.6.26 kernel from debian
Mike Christie wrote:
Not with just the above info. I t could be happening for a variety of
reasons.
It looks like the target is either disconnecting us (this is why I was
looking for a TCP_CLOSE in the debug output) because we goofed on some
iscsi protocol issue but normally I would have
