On Mon, 2007-06-18 at 15:56 +0200, Heiko Carstens wrote:
> One of my current disks has an FCP LUN of 0x401040ba... That's just
That's correct and coped with ... SCSI LUNs are BE ... this is still
only a four byte lun ... it actually says Flat Space addressing, 2 level
LUN: 16-168
> the li
On Mon, Jun 18, 2007 at 10:47:28AM +0200, Hannes Reinecke wrote:
> James Bottomley wrote:
> > On Tue, 2007-05-29 at 15:29 +0200, Swen Schillig wrote:
> >> From: Christof Schmitt <[EMAIL PROTECTED]>
> >>
> >> zfcp reported units to the SCSI stack starting
> >> with number 0. LUN 0 reported to the S
On Monday 18 June 2007 10:47, Hannes Reinecke wrote:
> James Bottomley wrote:
> > On Tue, 2007-05-29 at 15:29 +0200, Swen Schillig wrote:
> >> From: Christof Schmitt <[EMAIL PROTECTED]>
> >>
> >> zfcp reported units to the SCSI stack starting
> >> with number 0. LUN 0 reported to the SCSI stack is
James Bottomley wrote:
> On Tue, 2007-05-29 at 15:29 +0200, Swen Schillig wrote:
>> From: Christof Schmitt <[EMAIL PROTECTED]>
>>
>> zfcp reported units to the SCSI stack starting
>> with number 0. LUN 0 reported to the SCSI stack is usually
>> not the FCP LUN 0. When scanning for devices,
>> th
On Tue, 2007-05-29 at 15:29 +0200, Swen Schillig wrote:
> From: Christof Schmitt <[EMAIL PROTECTED]>
>
> zfcp reported units to the SCSI stack starting
> with number 0. LUN 0 reported to the SCSI stack is usually
> not the FCP LUN 0. When scanning for devices,
> the SCSI stack tried to issue a
From: Christof Schmitt <[EMAIL PROTECTED]>
zfcp reported units to the SCSI stack starting
with number 0. LUN 0 reported to the SCSI stack is usually
not the FCP LUN 0. When scanning for devices,
the SCSI stack tried to issue a REPORT LUN command to LUN 0.
The current design for zfcp does not wa
6 matches
Mail list logo
