Nexsan SATAboy setup

Hi. I've got a Nexsan iSCSI array. It has 4 different "data-adresses" that I can all discover and get access to the volumes on the array through. But I'd prefer that my client instead of connnection to a single data-address connected to all of them and balanced over them in order to distribute

Re: Modifying LUN 0 allowed?

On Thu, Jul 10, 2008 at 11:31:06PM -0700, HIMANSHU wrote: > > Very basic question... > > Suppose I added say "MyLun0" in target say "MyTarget1" as a LUN Number > 0. > > Then > > Is it the "Convention" that LUN 0 should not be "modified"? No. You can do whatever you want. > i.e.Afterwards I s

"nodes" and "send_targets"

I am talking about version "iscsi-initiator-utils-6.2.0.865-0.2.fc7". When I discover any target machine say 7.152.entries goes to "/var/lib/ iscsi/nodes" and "/var/lib/iscsi/send_targets".After login,"default" file doesn't change. Then when the SAME initiator wants to discover another target..s

Re: Nexsan SATAboy setup

Jesper Krogh wrote: > > Hi. > > I've got a Nexsan iSCSI array. It has 4 different "data-adresses" that I > can all discover and get access to the volumes on the array through. > > But I'd prefer that my client instead of connnection to a single data-address > connected to all of them and balance

Scientific Linux 4.6 (RHEL Deriv) and "Failing command cdb 0x8a..."

Obviously looking for some help, if any is there to be had. Behavior I'm seeing is a log entry stating "ping timeout of 5 secs expired" then session dropped. Roughly 2 seconds of "Failing command..." then the session is re-established. (log excerpt below). This has been caused corruption in the

Re: Nexsan SATAboy setup

Jesper Krogh wrote: > > Hi. > > I've got a Nexsan iSCSI array. It has 4 different "data-adresses" that I > can all discover and get access to the volumes on the array through. > > But I'd prefer that my client instead of connnection to a single data-address > connected to all of them and balanc

Re: Scientific Linux 4.6 (RHEL Deriv) and "Failing command cdb 0x8a..."

John Reddy wrote: > Obviously looking for some help, if any is there to be had. > > Behavior I'm seeing is a log entry stating "ping timeout of 5 secs > expired" then session dropped. Roughly 2 seconds of "Failing > command..." then the session is re-established. (log excerpt below). > This has