Home » Fujitsu Manuals » Hard Drives » Fujitsu MAX3073NC » Manual Viewer

Fujitsu MAX3073NC Specifications - Page 210

LBCSS Logical Block Cache Segment Size not supported

UPC - 550221511118

Add to My Manuals
Save this manual to your list of manuals

Page 210 highlights

Parameter Data Formats "1" : Requests that the device server not read into the buffer any logical blocks beyond the addressed logical blocks. "0" : The device server continues to read logical blocks into the buffer beyond the addressed logical blocks. n. FSW (force sequential write) (not supported) This bit specifies how to write multiple blocks. "1" : If the IDD writes multiple blocks, this indicates that data are recorded on the disk media in the order in which they are transferred from the INIT. "0" : If the IDD writes multiple blocks, this indicates that data are recorded on the disk media with their order changed in order to complete the command in the fastest time. This bit cannot be changed. The IDD disregards the specification in this bit and operates according to the "Default" value (="1"). o. LBCSS (Logical Block Cache Segment Size) (not supported) "1" : Indicates that the "Cache segment size" field units are interpreted as logical blocks. "0" : The "Cache segment size" field units are interpreted as bytes. This bit is not supported for the IDD. The IDD disregards the specification in this bit. p. Cache segment count This parameter specifies the number of cache segments used by the IDD. This parameter is valid when the SIZE bit specification is "0." When a value greater than max value is specified, the IDD performs rounding processing and sets max value. Also, when a value less than 3 is specified, the IDD performs rounding processing and set 4. This parameter indicates the same value for all initiators and if it is changed by any initiator, a UNIT ATTENTION condition (UNIT ATTENTION [=6] / Mode select parameter changed [=2A-01]) is generated for all the initiators that did not change it. This parameter can be changed though the IDD disregards the specification of this field. The IDD divides the Cache Segments according to the inherent algorithm. That is, the Cache Segment size is best tuned per the request data size of Host command. Within one Cache Segment, data for various commands are stored. IDD does not support this parameter. IDD disregards the specification of this field. q. Non cache buffer size If this field is greater than zero, this field advises the device server how many bytes the application client requests that the device server allocate for a buffer function when all other cache segments are occupied by data to be retained. If the number is at least one, caching functions in the other 4-26 C141-C010

Section	Page
Front Cover	1
FOR SAFE OPERATION	2
Revision History	3
Preface	5
Contents	11
Illustrations	16
Figures	16
Tables	17
CHAPTER 1 Command Processing	19
1.1 Command Format	19
1.2 Status	24
1.3 Outline of Command Processing	26
1.3.1 Single commands	26
1.3.2 Command link	27
1.3.3 Disconnect/reconnect processing	29
1.3.4 Synchronous mode data transfer/wide mode data transfer	33
1.4 Command Queuing Function	34
1.4.1 Untagged queuing	34
1.4.2 Tagged queuing	36
1.5 UNIT ATTENTION Condition	37
1.5.1 Generation of the UNIT ATTENTION condition	37
1.5.2 Response and release condition at UNIT ATTENTION condition hold state	38
1.5.3 UNIT ATTENTION condition multiple hold	38
1.6 Sense Data Hold State	40
1.6.1 Sense data hold condition	40
1.6.2 Response and release conditions at sense data hold state	40
1.7 Command Processing Exceptions	41
1.7.1 Overlapping commands	41
1.7.2 Illegal LUN specification	42
1.7.3 Reserved operation code	42
1.7.4 Command processing in the not ready state	42
1.7.5 Error recovery processing	44
1.7.6 Reset processing	46
1.7.7 Fatal hardware errors	47
1.8 Data Block Addressing	48
1.8.1 Definition of data space	48
1.8.2 Logical block addressing	50
CHAPTER 2 Data Buffer Management	51
2.1 Data Buffer	51
2.1.1 Data buffer configuration and basic operation	51
2.1.2 Operation mode setting	55
2.2 Look-Ahead Cache Feature	56
2.2.1 Caching operation	56
2.2.2 Caching parameters	59
2.2.3 Look-Ahead operation, Look-Ahead volume	60
2.3 Write Cache	61
CHAPTER 3 Command Specifications	63
3.1 Control/Sense Commands	63
3.1.1 TEST UNIT READY (00)	63
3.1.2 INQUIRY (12)	64
3.1.3 READ CAPACITY (25)	75
3.1.4 CHANGE DEFINITION (40)	76
3.1.5 MODE SELECT (15)	81
3.1.6 MODE SELECT EXTENDED (55)	89
3.1.7 MODE SENSE (1A)	92
3.1.8 MODE SENSE EXTENDED (5A)	100
3.1.9 REZERO UNIT (01)	103
3.1.10 START/STOP UNIT (1B)	103
3.1.11 RESERVE (16)	105
3.1.12 RESERVE EXTENDED (56)	108
3.1.13 RELEASE (17)	109
3.1.14 RELEASE EXTENDED (57)	110
3.1.15 REQUEST SENSE (03)	110
3.1.16 LOG SELECT (4C)	112
3.1.17 LOG SENSE (4D)	116
3.1.18 PERSISTENT RESERVE IN (5E)	117
3.1.19 PERSISTENT RESERVE OUT (5F)	124
3.1.20 REPORT LUNS (A0)	128
3.1.21 REPORT DEVICE IDENTIFIER (A3)	130
3.1.22 SET DEVICE IDENTIFIER (A4)	131
3.2 Data Access Commands	133
3.2.1 READ (08)	133
3.2.2 READ EXTENDED (28)	134
3.2.3 WRITE (0A)	135
3.2.4 WRITE EXTENDED (2A)	136
3.2.5 WRITE AND VERIFY (2E)	137
3.2.6 VERIFY (2F)	138
3.2.7 SEEK (0B)	139
3.2.8 SEEK EXTENDED (2B)	139
3.2.9 SET LIMITS (33) (Not Supported)	140
3.2.10 SYNCHRONIZE CACHE (35)	142
3.3 Format Commands	143
3.3.1 FORMAT UNIT (04)	143
3.3.2 REASSIGN BLOCKS (07)	153
3.3.3 READ DEFECT DATA (37)	156
3.4 Maintenance, Diagnostic Commands	161
3.4.1 SEND DIAGNOSTIC (1D)	161
3.4.2 RECEIVE DIAGNOSTIC RESULTS (1C)	168
3.4.3 WRITE BUFFER (3B)	172
3.4.4 READ BUFFER (3C)	177
3.4.5 READ LONG (3E)	181
3.4.6 WRITE LONG (3F)	182
3.4.7 WRITE SAME (41)	183
CHAPTER 4 Parameter Data Formats	185
4.1 Mode Parameters	185
4.1.1 Read/Write error recovery parameters (page code = 1)	185
4.1.2 Disconnect/reconnect parameters (page code = 2)	194
4.1.3 Format parameter (page code = 3)	198
4.1.4 Drive parameter (page code = 4)	202
4.1.5 Verify error recovery parameters (page code = 7)	203
4.1.6 Caching parameters (page code = 8)	205
4.1.7 Control mode parameters (page code = 0A)	211
4.1.8 Notch parameter (page code = 0C)	215
4.1.9 Port control parameter (page code = 19)	217
4.1.10 Informational exceptions control page (page code = 1C)	227
4.1.11 Background control mode parameter (page code = 1C/subpage = 01)	231
4.1.12 Additional error recovery parameters (page code = 21)	232
4.2 Log Parameters	233
4.2.1 Supprot log page (X'00')	233
4.2.2 Buffer overrun / underrun page (X'01')	234
4.2.3 Write error count page (X'02')	235
4.2.4 Read error count page (X'03')	238
4.2.5 Verify error count page (X'05')	242
4.2.6 Non-medium error count page (X'06')	245
4.2.7 Temperature page (X'0D')	246
4.2.8 Start-stop cycle counter page (X'0E')	247
4.2.9 Application client page (X'0F')	250
4.2.10 Self-test result page (X'10')	251
4.2.11 Background medium scan page (X'15')	253
4.2.12 SMART status page (X'2F')	255
4.2.13 SMART data page (X'38')	256
CHAPTER 5 Sense Data Error Recovery Methods	257
5.1 Sense Data	257
5.1.1 Sense data format	257
5.1.2 Sense data basic information	258
5.1.3 Sense data additional information	268
5.2 INIT Error Recovery Methods (Recommended)	268
5.2.1 Termination status analysis and error recovery methods	268
5.2.2 Sense data analysis and error recovery methods	271
5.2.3 Error logging	278
5.3 Disk Drive Error Recovery Processing	279
5.3.1 Error states and retry processing procedures	279
5.3.2 Auto alternate block allocation processing	280
5.3.3 Error recovery processing control	282
CHAPTER 6 Disk Media Management	285
6.1 Defect Management	285
6.2 Disk Media Initialization	287
6.2.1 Initialization during installation	287
6.2.2 Re-initialization	289
6.3 Data Block Verification Methods (Recommended)	290
6.4 Alternate Block Allocation Processing	291
Glossary	293
Acronyms and Abbreviations	297
Index	299
READER’S COMMENT FORM	307

Match case Limit results 1 per page

Parameter Data Formats

4-26

C141-C010

"1"

: Requests that the device server not read into the buffer any logical blocks beyond the

addressed logical blocks.

"0"

: The device server continues to read logical blocks into the buffer beyond the addressed logical

blocks.

FSW (force sequential write)

(not supported)

This bit specifies how to write multiple blocks.

"1"

: If the IDD writes multiple blocks, this indicates that data are recorded on the disk media in the

order in which they are transferred from the INIT.

"0"

: If the IDD writes multiple blocks, this indicates that data are recorded on the disk media with

their order changed in order to complete the command in the fastest time.

This bit cannot be changed.

The IDD disregards the specification in this bit and operates according

to the "Default" value (="1").

LBCSS (Logical Block Cache Segment Size) (not supported)

"1"

: Indicates that the "Cache segment size" field units are interpreted as logical blocks.

"0"

: The "Cache segment size" field units are interpreted as bytes.

This bit is not supported for the IDD.

The IDD disregards the specification in this bit.

p. Cache segment count

This parameter specifies the number of cache segments used by the IDD.

This parameter is valid

when the SIZE bit specification is "0."

When a value greater than max value is specified, the IDD performs rounding processing and sets

max value.

Also, when a value less than 3 is specified, the IDD performs rounding processing and

set 4.

This parameter indicates the same value for all initiators and if it is changed by any initiator, a UNIT

ATTENTION condition (UNIT ATTENTION

[=6] / Mode select parameter changed

[=2A-01]) is

generated for all the initiators that did not change it.

This parameter can be changed though the IDD disregards the specification of this field.

The IDD

divides the Cache Segments according to the inherent algorithm.

That is, the Cache Segment size is

best tuned per the request data size of Host command.

Within one Cache Segment, data for various

commands are stored.

IDD does not support this parameter. IDD disregards the specification of this field.

Non cache buffer size

If this field is greater than zero, this field advises the device server how many bytes the application

client requests that the device server allocate for a buffer function when all other cache segments are

occupied by data to be retained.

If the number is at least one, caching functions in the other