lkml.org 
[lkml]   [2014]   [Jan]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH 07/14] target/sbc: Add P_TYPE + PROT_EN bits to READ_CAPACITY_16
From
Date
>>>>> "Sagi" == Sagi Grimberg <sagig@dev.mellanox.co.il> writes:

>> I don't know of any non-disk devices that actually implement FORMAT
>> UNIT. Usually such configuration is done using the array management
>> interface.

Sagi> So this takes me to a corner I still don't understand, if a LUN is
Sagi> pre-formatted as T10-protected, what happens to unwritten blocks
Sagi> read? I mean, SCSI login executes some reads from sevel LBAs
Sagi> which will probably fail as blocks are unwritten.

Per SBC, PI must be initialized to 0xffffffffffffffff. Since an app tag
value of 0xffff is an escape, this will prevent both target and
initiator from performing PI-verification when that block is read.

If a block is subsequently written and no PI is sent from the host
(WRPROTECT=0), the target must generate valid PI for each block.

--
Martin K. Petersen Oracle Linux Engineering


\
 
 \ /
  Last update: 2014-01-12 14:01    [W:0.449 / U:0.036 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site