I 1111111111111111 11111 111111111111111 11111 1111111111 lllll 111111111111111111
`US005920893A
`[11] Patent Number:
`5,920,893
`
`United States Patent
`[19J
`[45]Date of Patent:
`
`Nakayama et al.
`Jul. 6, 1999
`
`[54]STORAGE CONTROLAND COMPUTER
`SYSTEM USING THE SAME
`
`Shinichi Nakayama, Odawara; Shizuo[75]Inventors:
`
`
`
`
`
`
`Yokohata, Kanagawa-ken, both of
`Japan
`
`FOREIGN PATENT DOCUMENTS
`
`Japan. 60-25427012/1985
`
`
`
`
`63-2110199/1988 Japan.
`
`
`1-30911712/1989 Japan.
`
`
`0325694511/1991 Japan.
`
`
`
`
`Hitachi, Ltd., Tokyo, Japan[73]Assignee:
`
`[21]Appl. No.: 08/867,191
`
`[22]Filed:Jun. 2, 1997
`
`Primary Examiner-Tod R. Swann
`
`
`
`Assistant Examiner-Nasser Moazzami
`
`
`
`
`
`Attorney, Agent, or Firm-Antonelli, Terry, Stout & Kraus,
`
`LLP
`[57]
`
`ABSTRACT
`
`
`
`
`
`[30] Foreign Application Priority Data
`
`A storage control enables data on various storage media to
`
`
`
`
`
`
`Jun. 4, 1996 [JP] Japan .................................... 8-163927
`
`
`
`be shared among host computers having various different
`
`
`
`
`host computer input/output interfaces. A control processor
`[51]Int. Cl.6
`G06F 12/00
`
`
`
`checks a host computer interface management table when
`
`711/147; [52]U.S. Cl. .......................... 711/147; 711/163;
`
`
`
`
`write is requested by a host computer (HCP). The control
`
`
`
`
`
`
`711/170; 711/206; 395/494; 395/878; 395/200.08;
`
`
`
`processor writes write data in a cache slot of the cache
`
`360/48; 360/369
`
`
`
`
`memory without converting the format if the data format of
`[58]Field of Search ..................................... 711/147, 163,
`
`
`
`
`the HCP is in an FBAformat and it converts the format into
`
`
`
`711/170, 206; 395/494, 878, 200.08; 360/48,
`
`the FBA format and writes it when the data format of HCP
`369
`
`
`
`is in a CKD format. The processor checks a table when read
`
`
`
`is requested by HCP. If the data format of HCP is FBA, the
`
`
`
`processor transfers the read data read from the cache slot
`
`
`
`
`
`without converting it and if it is CKD, the processor converts
`
`the format into the FBA format and transfers the format
`
`
`5,206,939 4/1993 Yanai et al. ............................. 395/400
`
`
`
`
`converted data. The control processors, retrieve write data in
`
`
`5,581,743 12/1996 Burton et al. ........................... 395/500
`
`
`the cache memory and writes it in a drive.
`
`
`5,664,144 9/1997 Yanai et al. ............................. 711/113
`
`
`5,724,542 3/1998 Taroda et al. ........................... 711/113
`
`
`19 Claims, 9 Drawing Sheets
`
`
`
`5,778,349 7/1998 Okonogi ...................................... 707/1
`
`
`
`......................................................
`
`[56]
`
`
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`300
`
`-303
`
`301
`
`304
`
`302
`
`307
`COMMON CONTROL
`MEMORY
`
`a: 305
`..JO
`0(1)
`0:(1)
`1-W
`zu
`00
`Ua:
`CL
`
`306 a:
`DRIVE
`..JO
`0(1)
`CONTROLL
`0:(1)
`500
`1-W
`318 BLOCK (DCB)
`zu
`HOST
`oo
`wo
`u a: (/)a:
`COMPUTER
`CL
`CL
`400
`INTERFACE
`MANAGEMENT
`TABLE
`
`a:
`
`wO
`u(/)
`-(/)
`
`>w
`a:u
`
`308
`
`317
`
`a:
`
`..JO
`0(1)
`0:(1)
`1-W
`zu
`oo
`Ua:
`
`309
`CACHE MEMORY
`a:
`
`CACHE
`SLOT
`
`..JO
`0(1)
`0:(1)
`1-W
`zu
`oo
`Ua:
`CL
`
`310 312 311
`
`DRIVE
`313
`INTERFACE
`
`DRIVE
`INTERFACE
`314
`
`315
`
`316
`
`Google Exhibit 1007
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 1 of 16
`
`

`

`5,920,893
`U.S. Patent Jul. 6, 1999 Sheet 1 of 9
`
`f100
`
`FIG. 1
`101
`f
`
`HOST
`HOST
`HOST
`COMPUTER
`COMPUTER
`COMPUTER
`C
`B
`A
`
`11
`
`103
`f
`f104
`
`STORAGE
`CONTROL
`
`, /105
`
`106
`' f
`
`CONTROL
`CONTROL
`CONTROL
`PROCESSOR
`PROCESSOR
`PROCESSOR
`
`•
`
`'
`
`CONTROL
`CONTROL
`CONTROL
`PROCESSOR
`PROCESSOR
`PROCESSOR
`
`� \109
`
`112
`
`1
`
`113
`,, f
`
`MAGNETIC
`DISK DEVICE
`
`MAGNETIC
`TAPE
`
`DEVIC:;
`
`0
`
`FD
`
`Google Exhibit 1007
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 2 of 16
`
`

`

`U.S. Patent Jul. 6, 1999 Sheet 2 of 9 5,920,893
`
`FIG. 2
`
`!200
`
`210
`STORAGE CONTROL f
`202
`f
`
`201
`f
`
`204
`-
`
`HOST
`COMPUTER
`
`A -)
`205
`
`DATA
`ACCESS
`UNIT
`
`206
`) HOST
`COMPUTER
`B
`
`) .
`207
`
`'
`
`208� �209
`
`STORAGE MEDI UM �203
`
`Google Exhibit 1007
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 3 of 16
`
`

`

`U.S. Patent Jul. 6, 1999 Sheet 3 of 9 5,920,893
`
`FIG. 3
`HOST 300
`
`COMPUTER
`
`HOST 303
`
`COMPUTER
`
`CHANNEL �301
`
`CONTROL
`
`'
`
`SCSI BUS �304
`
`CONTROL
`
`;302
`i )307 ,, i i
`a: )305 MEMORY 306\ a:
`c-500 0(1)
`r-w 318--------- BLOCK (DCB)
`400 oa:
`
`a:
`
`() Cl)
`wO
`-Cl)
`a:o
`>w
`Cl) a:
`wo
`CL
`
`317
`(
`
`....IQ
`0(1)
`a: Cl)
`Z()
`Oa:
`oo
`CL
`
`308
`(
`
`I
`
`a:
`....IQ
`0(1)
`a: Cl)
`r-W
`Z()
`Oa:
`00
`
`i\.310
`
`COMMON CONTROL
`
`DRIVE
`CONTROLL r--
`
`HOST
`COMPUTER ........
`INTERFACE
`MANAGEMENT
`TABLE
`
`....IQ
`a: Cl)
`zo
`r-W
`oo
`CL
`
`' I
`
`'
`
`309
`CACHE MEMORY V a:
`
`CACHE
`SLOT
`
`....IQ
`Cl)
`a: Cl)
`0
`r-W
`Z()
`
`\
`
`(
`
`312
`
`311 ,/ Oa:
`
`oo
`CL
`
`DRIVE �313
`
`INTERFACE
`
`314 -------
`
`DRIVE
`INTERFACE
`
`[..,----/ 315
`
`DRIVE
`
`�316
`
`DRIVE
`
`•
`
`-
`
`::::
`
`1
`
`Google Exhibit 1007
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 4 of 16
`
`

`

`5,920,893
`U.S. Patent Jul. 6, 1999 Sheet 4 of 9
`
`FIG. 4
`
`DRIVE CONTROL BLOCK (DCB)
`
`400
`
`DRIVE No.
`
`401
`
`INTERPROCESSOR EXECLUSIVE
`INFORMATION
`
`402
`
`
`
`INTERHOST EXECLUSIVE INFORMATION
`403
`
`DRIVE VACANCY WAITING INFORMATION
`404
`
`FIG. 5
`HOST COMPUTER INTERFACE MANAGEMENT
`
`INFORMATION TABLE
`
`501
`
`CONTROL
`PROCESSOR
`No.
`
`INTERFACE
`INFORMATION
`
`502
`
`500
`
`503
`
`504
`
`305
`
`CKD FORMAT
`
`306
`
`FSA FORMAT
`
`506
`
`507
`
`Google Exhibit 1007
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 5 of 16
`
`

`

`U.S. Patent Jul. 6, 1999 Sheet 5 of 9 5,920,893
`
`START
`600
`
`RESERVE DCB
`601
`
`NO
`IS RESERVATION
`602
`SOCCESSFUL ?
`YES
`
`RESERVE CACHE
`603
`SLOT
`
`YES
`WRITE COMMAND
`604
`?
`NO
`IS DATA IN
`CACHE ?
`YES
`
`617
`
`FIG.6
`
`610
`
`NO G) COMPUTER
`
`REFER HOST
`INTERFACE
`INFORMATION
`
`READ DAT A FROM
`605
`CACHE SLOT
`
`NO
`611 CKD FORMAT ?
`
`YES
`
`CONVERT DATA
`612
`REFER HOST
`
`COMPUTER INTERFACE
`606
`INFORMATION
`
`607
`CKD FORMAT ?
`
`YES
`
`CONVERT DATA
`608
`
`WRITE DATA IN
`CACHE SLOT
`
`613
`
`TRANSFER DATA TO
`609
`HOST COMPUTER
`
`RELEASE CACHE
`614
`SLOT
`
`615-
`
`RELEASE DCB
`
`616 END
`
`Google Exhibit 1007
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 6 of 16
`
`

`

`U.S. Patent Jul. 6, 1999 Sheet 6 of 9 5,920,893
`
`FIG.7
`
`START
`
`700
`
`SET
`INTERPROCESSOR
`EXCLUSIVE
`701
`INFORMATION
`
`IS INTERHOST YES
`EXCLUSIVE
`
`INFORMATION "ON" ?
`
`NO
`702
`SET INTERHOST
`EXCLUSIVE
`703
`
`INFORMATION "ON"
`
`REPORT HOST
`COMPUTER THAT
`705
`DCB IS NOW USED
`
`SET SUCCESS OF
`
`RESERVATION IN
`704
`RETURN CODE
`
`SET VACANCY
`WAITING 706
`INFORMATION
`OF DCB
`
`SET FAILURE OF
`
`RESERVATION IN
`707
`RETURN CODE
`
`CANCEL
`INTERPROCESSOR 708
`EXCLUSIVE
`INFORMATION
`
`RETURN TO CALL
`709
`
`ORIGINATING STEP
`
`Google Exhibit 1007
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 7 of 16
`
`

`

`U.S. Patent Jul. 6, 1999
`
`Sheet 7 of 9 5,920,893
`
`FIG.8
`
`START
`
`800
`
`SET
`INTERPROCESSOR
`EXCLUSIVE
`801
`INFORMATION
`
`CANCEL INTERHOST
`EXCLUSIVE 802
`INFORMATION
`
`IS WAITING
`INFORMATION
`PRESENT ?
`NO
`
`803
`
`CANCEL
`INTERPROCESSOR
`805
`EXCLUSIVE
`INFORMATION
`
`RETURN TO CALL
`806
`
`ORIGINATING STEP
`
`REPORT HOST
`COMPUTER THAT
`804
`DCB IS FREE
`
`Google Exhibit 1007
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 8 of 16
`
`

`

`Jul. 6, 1999 Sheet 8 of 9
`U.S. Patent
`5,920,893
`
`0
`
`...
`... ...
`...
`...
`... ...
`' ...
`...
`'
`... ... ... ...
`
`...
`... ...
`...
`...
`' '
`... ...
`... ...
`'
`---
`------
`
`',
`
`0
`
`-----------
`---
`
`�
`
`()
`
`0)
`
`---
`
`LL
`
`----------
`
`0
`
`0
`
`0
`
`-----... _
`---
`------------
`0
`
`0
`
`1--
`
`1--
`
`�
`
`()
`--,-
`
`---
`
`LU.-...
`I- �
`>-O
`coo
`C\I _J
`..-CO
`()
`I.[)-
`------------
`
`0
`
`�
`
`<(
`co
`_J
`
`<(
`�
`er:
`0
`LL
`
`<(
`co
`LL
`
`I­<(
`
`
`�
`a:
`0
`LL
`
`0
`�
`()
`
`Google Exhibit 1007
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 9 of 16
`
`

`

`U.S. Patent Jul. 6, 1999 Sheet 9 of 9 5,920,893
`
`FIG. 10
`
`HOST 300 303
`HOST
`I
`I
`COMPUTER
`COMPUTER
`I
`I
`7 � -- ,· 31 9
`-------�--------
`CHANNEL V"'----" 3 0 1 304---
`t -----
`. ------
`: FIBER : :
`SCSI BUS
`: CHANNEL �Tv 317
`CONTROL
`CONTROL
`)302
`: CONTROL :
`•------♦-------
`305 ( i 500 f 307
`-'OOu,a: en1-W
`z (.)
`oo Ua:
`
`I
`
`I I
`
`I
`I
`I
`I
`-'O
`I
`
`I
`
`I
`I
`
`318-. I I
`i
`i
`,-•�_Lt_
`I
`I
`COMMON CONTROL
`I
`I
`a:
`I
`a:
`I a: I
`I
`MEMORY
`I Ou, I
`-'O Ou,a: en1-W Z(.)
`wO (.) Cf)
`I a:cn I
`- Cf)
`I 1-W
`>wa:(.)
`zu I
`I
`I
`I
`wo Cf) a:CL
`I
`oo Ua:CL
`I ua: I
`I
`oo I
`I CL I
`I
`I
`I
`I
`1 _______ ,
`' \_306 I -- - - - - --,-- - - - - - - I
`(
`317
`t_ _ -----;
`( ,-------_
`308 : :---'---:
`: -'O I
`: Oen :
`I a:(/) I
`I 1-W :
`:zu •
`: 00:
`I Ua: :
`I
`CL I
`I
`I
`I
`I
`I l---,--,-
`I
`I
`\ 320
`
`p
`
`a:
`
`CL
`
`DRIVE
`CONTROLL
`BLOCK (DCB)
`
`HOST
`COMPUTER
`INTERFACE
`MANAGEMENT
`TABLE
`
`:
`
`'
`
`I
`
`' I
`I
`I
`I
`
`'
`
`I
`
`a: :
`
`1 I
`
`a:
`
`I
`
`I
`I
`
`-'
`
`'
`
`CACHE MEMORY
`
`CACHE
`SLOT
`
`a:
`
`-'OOu, a: en1-w Z(.)
`oo Ua:CL
`
`)309
`-'OOena:cn1-W zu
`I ( 312
`oo Ua:
`311 _)L--...,� CL
`DRIVE 313
`DRIVE
`INTERFACE
`314--------- INTERFACE
`V"'----"
`
`a
`
`315
`DRIVE
`I 316
`l,--J
`DRIVE
`
`;-
`
`i
`
`----,
`
`I ---
`
`I
`
`I
`
`: ,---, L,-_,..,321
`
`I t l
`I I
`I
`: ,..__/
`:
`I I
`I
`:
`�-------- I
`I I
`----------------
`\
`I I
`
`\ 322
`
`Google Exhibit 1007
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 10 of 16
`
`

`

`1
`
`5,920,893
`
`SYSTEM USING THE SAME
`
`STORAGE CONTROLAND COMPUTER
`
`2
`It is an object of the present invention to provide a storage
`
`
`
`
`
`
`
`control in which a request of data access to a storage
`
`
`
`medium from host computers having different host computer
`BACKGROUND OF THE INVENTION
`
`
`
`input/output interfaces is made possible by conducting data
`
`
`
`5 conversion if it is necessary for such a request and in which
`
`The present invention relates to a storage control and in
`
`
`
`
`
`
`
`sharing of data on the storage medium among host comput­
`
`
`
`particular to a storage control system which enables data on
`
`
`ers having different host computer input/output interfaces is
`
`
`
`various storage media for storing input/output data to/from
`
`
`
`made possible whereby extensibility of file subsystem and
`
`
`host computers to be shared among said host computers
`
`
`
`responsiveness of data is enhanced to enable a wide rage of
`
`
`
`
`having various host computer input/output interfaces; and a
`
`
`built. 10 computer system configurations to be
`
`computer system using the same.
`
`
`
`
`
`It is another object of the present invention to provide a
`
`
`
`Recently cases have been increased in which main frames
`
`
`
`
`
`storage control which enables various host computer input/
`are linked with a division system of an open system bases,
`
`
`
`
`
`
`output interfaces and/or various storage medium input/
`
`such as downsizing of part of operations (transactions, jobs)
`
`
`
`
`
`output interfaces to be added to or removed from the storage
`which used to be processed by a main frame to a division
`
`
`15 control.
`
`server (for example, UNIX server, etc.) or incorporation of
`
`
`
`
`an information system into a division.
`It is a further object of the present invention to provide a
`
`
`
`
`
`
`
`
`
`
`
`
`In these cases, due to the fact that the data format (CKD computer system including the above-mentioned storage
`
`
`
`format) of the main frame is different from the data format control.
`
`
`
`
`(FBA format) of the host computer input/output interface of
`In order to accomplish the above-mentioned object, in an
`
`
`
`20
`
`
`
`
`the UNIX server, development of programs for data con-
`
`
`
`
`
`aspect of the present invention there is provided a storage
`
`
`
`
`version and data conversion between host computers is
`
`
`
`
`control in a computer system including a plurality of host
`
`
`
`
`required or a storage control devoted to each host computer
`
`
`
`computers having various different host computer input/
`
`
`input/output interface is necessary. This makes it difficult to
`
`
`
`
`
`output interfaces, the storage control for controlling input/
`
`
`build a wide range of computer system configurations.
`
`
`output to/from the host computers, and various storage
`
`As one of methods which have been devised in order to 25
`
`
`
`media for storing input/output data of the host computers,
`
`
`
`overcome the above-mentioned problems, an integrated
`
`
`
`wherein the storage control is made up of: control
`
`
`
`computer system which enables various programs to be
`
`
`
`
`processors, each being connected to one of host com­
`
`
`
`
`executed without limiting the CPU (central processing unit)
`
`
`
`
`puters; device input/output interfaces, each for one of
`
`
`
`
`architecture by adopting, for example, a hardware configu-30
`
`
`
`
`storage media, for connecting the control processors
`
`
`
`
`ration including a plurality of computers in one system is
`
`
`
`
`
`with the various storage media to input/output data in
`
`disclosed in JP-A-60-254270.
`
`
`
`a predetermined format to/from each storage medium;
`
`
`
`
`A magnetic disk device including an interface which is
`
`
`and a host interface management table for managing
`
`
`
`
`
`compatible to a plurality of different interface standards and
`
`
`
`the data format of the host computer interface of each
`
`
`
`
`an interface conversion control circuit which enables files on 35
`host computer;
`
`
`a magnetic disk to be shared is disclosed in JP-A-1-309117.
`each of the control processors includes a data format
`
`
`
`
`converting unit which compares the data format of
`SUMMARY OF THE INVENTION
`
`
`
`corresponding host computer in the host computer
`In the prior art technology which is disclosed in the
`
`
`
`
`
`
`interface managing table with the predetermined data
`
`
`above-mentioned JP-A-60-254270, CPUs having different
`
`
`
`format when a write data request is issued from the
`40
`
`
`
`architectures have a master-slave relationship with each
`
`
`
`corresponding host computer, convertes the data format
`
`
`other. The CPU on the other slave side having different
`
`
`of the write data into the predetermined data format,
`
`architecture is exclusively prevented to simultaneously use
`
`
`
`
`writes the converted write data in the storage medium
`
`the storage medium in order that the CPU on the slave side
`
`
`
`when the compared formats match with each other and
`
`
`
`is selected by a hardware switch to occupy a system bus for
`
`
`
`
`
`writes the write data without converting the data format
`45
`
`
`
`
`executing an input/output operation to/from the storage
`
`
`of the write data when they do not match with each
`
`
`
`medium. Accordingly when the selected CPU is used for an
`
`
`
`other, and which also compares the data format of the
`
`
`
`extended period of time, a disadvantage occurs that the
`
`
`
`corresponding host computer in the host computer
`
`
`storage medium and/or the system bus which are resources
`
`
`interface managing table with the predetermined data
`common to the system would be occupied for an extended
`
`
`
`format when a read data request is issued from the
`50
`period of time.
`
`
`
`corresponding host computer, converts the data format
`Since files in the magnetic disk device are divided and
`
`
`
`
`of the read data read from the storage medium into the
`
`
`
`stored for each of CPU sharing different architectures, it is
`
`
`predetermined data format to transfer the converted
`
`
`impossible to share the same file in the magnetic disk device
`
`
`read data to the corresponding host computer when the
`
`
`among CPUs having different architectures. 55
`
`
`compared formats do not match with each other and
`
`
`
`
`Although it is possible for host computers having different
`
`
`
`transfers the read data to the corresponding host com-
`
`
`architectures to share a storage medium in the prior art as
`
`
`puter without converting the data format of the read
`
`
`
`
`mentioned above, the storage medium is exclusively used
`
`
`data when they match with each other. This configu­
`
`
`
`among host computers having different architectures. This
`
`
`
`
`ration enables data on various storage media to be
`
`
`
`
`may partly cause the utilization efficiency of the file sub-60
`
`
`shared among host computers having different host
`
`
`
`system to be remarkably lowered. The disadvantage that
`
`
`computer input/output interfaces.
`
`
`
`data sharing among host computers having different host
`
`
`
`In a computer system having the storage control of the
`
`
`computer input/output interfaces is not overcome.
`
`
`
`above-mentioned configuration, addition or removal of one
`
`
`
`
`Although file sharing among host devices having
`
`
`or more host computers having different desired kinds of host com-
`
`
`interfaces is possible
`
`
`65 puter input/output in the above-mentioned JP-A-1- interfaces and one or more control pro­
`
`
`
`
`different
`
`
`
`
`
`cessors 309117, data sharing among interfaces is not men­compatible to the host computers is made possible
`
`
`
`
`
`by updating the host computer interface managing table.
`tioned.
`
`Google Exhibit 1007
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 11 of 16
`
`

`

`5,920,893
`
`DESCRIPTION OF THE PREFERRED
`
`EMBODIMENTS
`
`
`
`4
`3
`In accordance with one feature of the present invention, medium 203 are connected to the storage control 210, which
`
`
`
`
`
`
`
`
`
`
`includes a data access unit 202. An access request 204
`
`
`
`drive control blocks (DCB ), each for one of storage devices
`
`
`
`
`(write), 205 (read), 206 (write) and 207 (read) which are
`
`
`(drives) are provided for controlling the access to each
`
`generated by the host computers A200 and B201 to the
`
`
`
`
`
`storage device. This enables various storage devices having
`
`
`
`media 203 are issued to the storage control 210.
`5 storage
`
`
`a given device input/output interface to be added or
`
`
`
`
`
`These access requests are executed by the data access unit
`removed.
`202.
`BRIEF DESCRIPTION OF THE DRAWINGS
`If the write access request 204 from the host computer
`
`
`
`
`A200 is issued, the data access unit 202 performs data
`
`
`
`
`FIG. 1 is a schematic block diagram showing one embodi­
`10 conversion
`
`
`
`when the data conversion of the write data is
`
`
`
`ment of a computer system of the present invention;
`
`
`
`
`
`necessary and writes converted data on the storage medium
`
`
`
`
`FIG. 2 is a schematic block diagram which is useful for
`
`
`
`203 and write unconverted write data on the storage medium
`
`explaining the summary of the present invention;
`
`
`
`203 when the data conversion is not necessary.
`
`
`FIG. 3 is a schematic block diagram showing the con­
`
`
`If the write access data request 204 is issued from the host
`
`
`
`
`
`
`
`figuration of another embodiment of a disk subsystem of the
`A200, the data access unit 202 performs data
`15 computer
`present invention;
`
`
`
`
`conversion of the write data when it is necessary and writes
`
`the converted data on storage medium 203 and writes
`
`
`
`
`FIG. 4 is a diagram showing the configuration of a drive
`
`unconverted write data on the storage medium 203 when the
`
`
`control block;
`
`data conversion is not necessary (208).
`
`FIG. 5 is a diagram showing one example of host com-
`
`
`
`
`20 If the read access request 205 from the host computer
`
`
`puter interface management information;
`
`
`A200 is issued, the data access unit 202 reads data from the
`
`
`FIG. 6 is a flow chart showing a data access operation;
`
`
`
`storage medium and performs data conversion when it is
`
`
`FIG. 7 is a flow chart showing a DCB reserving operation;
`
`
`
`
`necessary and transfers the converted data to the host
`
`
`
`FIG. 8 is a flow chart showing a DCB releasing operation;
`
`
`
`computer A and transfers the unconverted read data to the
`
`
`
`FIG. 9 is a chart useful for illustrating the conversion
`
`
`
`conversion is not necessary. 25 host computer A when the data
`
`
`between CKD and BAD formats; and
`
`
`
`
`Processing for the access request from the host computer
`FIG. 10 is a schematic block diagram showing the con­
`
`
`
`
`
`
`
`B201 is conducted similarly to the processing for the access
`
`
`
`
`figuration of a further embodiment of a disk subsystem of
`
`
`request from the host computer A200.
`
`the present invention.
`
`
`
`The above-mentioned operation enables the host comput-
`
`
`
`30 ers having various different host computer input/output
`
`
`
`interfaces to share the data on the storage medium.
`
`
`
`It is to be noted that the number of the host computers
`
`
`
`
`Now, the embodiments of the present invention will be
`
`
`
`
`
`having different host computer input/output interfaces is not
`
`
`described in detail with reference to drawings.
`
`
`
`limited to 2, the three or more host computers may be
`35 connected.
`
`
`
`FIG. 1 is a block diagram which is useful for explaining
`
`
`
`the principle of the operation of the present invention and
`FIG. 3 is a block diagram showing the of a
`
`configu ration
`
`
`showing the configuration of an embodiment of a computer
`
`
`
`disk subsystem having a cache memory in another embodi­
`
`system of the present invention which comprises a plurality
`
`ment of the present invention.
`
`
`
`of host computers having various different input/outputs
`
`
`
`In FIG. 3, a disk control 302 is connected to a host
`
`
`
`40 computer 300 via a channel control 301 on the host side and
`
`
`
`therefor, a storage control for controlling the input/output
`
`
`
`to/from the host computers and various storage media for
`
`is also connected to a host computer 303 via a small
`
`
`
`
`
`storing therein input/output data to/from the host computers.
`
`
`
`computer system interface ( abbreviated as SCSI).
`
`
`
`In FIG. 1, the plurality of host computersAlO0, BlOl and
`
`In the present embodiment, the host computer 300 is a
`
`
`
`
`
`C102 having various different host computer input/output
`
`
`main frame computer (CKD data format) and the host
`
`
`45 computer 303 is an UNIX computer (FBA data format).
`
`interfaces are connected to a magnetic disc device 111,
`
`
`
`
`
`magnetic tape device 112 and floppy disk device 113 via a
`
`
`
`The disk control 302 is connected to drives 315 and 316
`
`
`storage control 103.
`
`
`
`
`which are magnetic storage medium on the lower side.
`
`
`
`
`Control processors 104, 105, 106, 108, 109 and 110 which
`
`
`
`The disk control 302 performs read/write of data on the
`
`
`
`are incorporated in the storage control 103 are adapted to
`
`
`
`
`
`drives 315 and 316 in response to the requests of the host
`50
`
`
`control the transfer of data among the host computers AlOO,
`
`
`
`computers 300 and 303.
`
`
`BlOl and C102 and the magnetic disk device 111, magnetic
`Data transfer among the host computers 300, 303 and the
`
`
`
`
`tape device 112 and the floppy disk device 113.
`
`
`
`
`
`drives 315, 316 is controlled by the control processors 305,
`
`
`In other words, the control processors 104, 105 and 106
`
`
`
`
`306, 310 and 311 which are incorporated in the disk control
`
`
`
`
`execute an input/output data transfer request from the host 55
`302.
`
`
`computers AlOO, BlOl and C102 and the control processors
`The control processors 305 and 306 are connected to the
`
`
`
`
`
`
`108, 109 and 110 execute a request of input/output data
`
`
`
`
`host computers 300 and 303 through the channel control 301
`
`
`transfer to the magnetic disk device 111, magnetic tape
`
`
`
`and the SCSI bus control 304, respectively and the control
`
`
`device 112 and the floppy disk device 113.
`
`
`
`
`processors 310 and 311 are connected to the drives 315 and
`
`
`
`
`All the control processors 104, 105, 106, 108, 109 and 110 60
`
`
`316 through the drive interfaces 313 and 314, respectively.
`
`
`
`receive and transmit data and control signal with each other
`
`
`
`The control processors 305 and 306 mainly perform data
`
`via a control line 107.
`
`transfer between the host computers 300 and 303 and the
`
`
`
`
`
`
`FIG. 2 is a block diagram for explaining
`
`cache memory 309. The control the outline of the processors 310 and 311
`
`
`mainly of the present invention perform data transfer between the cache memory 309
`
`
`present invention. Now, the outline
`
`
`
`
`315 and 316.
`
`will be described with reference to FIG. 2. 65 and the drives
`
`
`
`
`
`In FIG. 2, the host computersA200, B201 having different A common control memory 307 is a common memory
`
`host computer input/output interfaces and the storage which is accessible from all control processors 305,306,310
`
`
`
`
`
`
`
`Google Exhibit 1007
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 12 of 16
`
`

`

`5,920,893
`
`
`
`
`
`If it is a write command, operation will be conducted as
`
`6
`5
`Now, operation of the control processors 305, 306, 310
`
`
`
`
`
`
`
`
`and 311 and stores therein common control information 318
`
`
`and 311 in the disk control 302 in accordance with the
`
`
`
`used for allowing the disk control 302 to manage the drives
`
`
`present invention will be described.
`
`315 and 316. The common control information 318 will be
`
`
`
`described hereafter in detail.
`
`
`FIG. 6 is a flow chart showing the main flow of operation
`
`
`
`5 which is executed by a data access processing unit (600)
`
`
`The cache memory 309 is accessible from all control
`
`
`processors 305,306, 310 and 311 and is used for temporarily
`
`
`including a data format conversion unit.
`
`
`
`storing data which is read from the drives 315 and 316. A
`
`
`
`When a control processor 305 receives a data access
`
`
`cache slot 312 is the data management unit quantity in the
`
`
`command from the host computer 300, DCB processing for
`cache memory 309.
`
`
`reserving the access right for the DCB of the specified drive
`/ 10
`
`
`The control processors 305, 306, 310 and 311 receive
`
`number is executed (step 601).
`transmit data and control signals from/to the cache memory
`
`
`
`A determination as to whether reservation of DCB is
`
`
`
`
`309 and the common control memory 307 via a signal line
`
`
`succeeded or not is made (step 602). If failed, the data access
`308.
`
`
`
`processing is ended (step 616). If it is successful, following
`
`
`
`The control processors 305 and 306 are connected to a
`
`15 operation will be conducted.
`
`
`
`service processor 317.
`Firstly, reservation of the cache slot is conducted (step
`
`
`
`When update of the common control information 318 in
`
`
`
`
`
`603). Subsequently, a determination is made as to whether or
`
`
`
`the common control memory 307 is instructed from the
`
`
`
`not the data access command is a write command or a read
`
`
`
`
`
`service processor 317, the service processor 317 selects any
`command (step 604).
`
`
`one of the control processors 305 and 306 to send an update 20
`
`
`
`
`
`
`
`request, so that the selected control processor will update the
`follows:
`
`
`
`common control information 318 in the common control
`With reference to the host computer interface manage­
`
`
`
`memory 307.
`
`ment information table 500 (FIG. 5) (step 610), a determi­
`Now, the common control information will be described.
`
`
`
`
`
`
`
`nation is made as to whether the host computer interface
`
`
`
`
`The common control information 318 includes a drive 25
`
`
`
`which is connected to the control processor is in the CKD or
`
`
`control block 400 and host computer interface management
`FBA format (step 611).
`
`
`
`information table 500, which will be described in order.
`In the present embodiment, the control processors 305
`
`
`
`
`
`
`
`FIG. 4 shows a drive control block (abbreviated as DCB)
`
`and 306 are in the CKD and FBA formats 506 and 507,
`
`
`400.One DCB 400 is provided for each one of the drives and
`respectively.
`
`
`stores therein four data.
`If it is in the CKD format, the control processor 305
`
`
`
`
`
`30
`
`
`
`
`The four data include a drive number 401 for enabling the
`
`converts CKD data into FBA data (step 612) and thereafter
`
`disk control 302 to identify each drive, interprocessor exclu­
`
`
`
`
`writes the converted write data into the cache slot 312 (step
`sive data 402, interhost exclusive information 403 and drive
`
`
`
`
`
`
`613). If it is in the FBA format, the control processor 305
`
`
`
`vacancy waiting information 404.
`
`35 writes FBA data into the cache slot 312 without conducting
`
`
`
`
`The interprocessor exclusive information 402 is used
`
`any conversion. Conversion of FBA data into CKD data will
`
`
`
`when the control processor 305 or 306 exclusively controls
`
`
`be described hereafter Thereafter, the cache slot is released
`
`
`
`
`the DCB access from the other control processor and sets the
`
`(step 614) and DCB is released (step 615).
`
`
`
`
`
`processor number when the control processor reserves the
`
`
`If the received command is a read command, operation
`
`
`
`
`access right for the DCB having the specified drive number
`
`40 will be executed as follows:
`
`
`and cancels the processor number when the control proces­
`Firstly, a determination is made as to whether a read data
`
`
`
`
`
`
`sor releases the access right to the DCB.
`
`exists in the cache memory (step 617). If the data exists,
`
`
`
`
`The interhost exclusive information 403 is used when the
`
`
`
`
`operation at step 605 and the subsequent steps will be
`
`
`
`host computer 300 or 303 exclusively controls the drive
`
`conducted. Ifno data exists, operation (1) will be conducted.
`
`
`
`
`access from the other host computer and sets the information
`45
`
`
`
`
`In the operation (1), the control processors 305 and 306
`
`
`
`403 "on" when the processor reserves access of the specified
`
`
`
`
`
`instruct the control processors 310, 311 to read data from the
`
`drive number and sets it "off" when the host computer
`
`
`
`
`drives and the control processors 310, 311 read data from the
`
`
`releases the access right.
`
`
`
`
`drives via the drive interfaces 313,314 to write read data in
`
`
`
`The drive vacancy waiting information 404 is used to
`
`
`
`the cache slot of the cache memory. This operation is
`
`
`inform one of the host computers 300 and 304 that a DCB
`
`
`50 omitted in the flow chart of FIG. 6.
`
`having the drive number specified is vacant upon being
`
`
`
`
`
`
`released from use by the other host computer which has been
`be described.
`
`
`
`using the DCB when the one computer requested to reserve
`
`Data on the cache slot 312 is read (step 605).
`
`
`
`
`the access right for the DCB but was informed of the fact
`
`
`that the DCB was being used by the other host computer.
`
`
`With reference to the host computer interface manage­
`55
`
`ment information table 500 (FIG. 5) (step 606), a determi­
`
`
`FIG. 5 shows a host interface management information
`
`
`
`
`nation is made as to whether the host computer interface
`table 500.
`
`
`
`which is connected to the control processor is in the CKD or
`
`
`In the table 500, the host interface information 502 is
`FBA format (step 607).
`
`
`
`
`managed for each number 501 of the control processor of a
`If it is in the CKD format, the control processor 305
`
`
`
`
`
`
`
`
`host computer connected. It is determined based upon this
`60
`
`converts the read data from FBA format into CKD format
`
`
`
`information as to whether data conversion is to be con­
`
`
`data (step 608) and transfers the converted data to the host
`ducted.
`
`
`computer 300 (step 609). Conversion of FED data into CKD
`
`
`
`
`In the present embodiment, the control processors 305
`
`data will described later.
`
`(503 in FIG. 5) and 306 (504 in FIG. 5) manage the CKD
`
`and FBA formats 506 and 507, respectively. The present
`
`
`
`If it is in the FBA format, the data which is read out from
`65
`
`
`management information table 500 is set and reset in
`
`
`the cache slot 312 is transferred to the host computer 303
`
`
`
`
`response to an instruction from the service processor 317.
`
`without conducting any conversion.
`
`Now, operation at step 605 and the subsequent steps will
`
`Google Exhibit 1007
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 13 of 16
`
`

`

`5,920,893
`
`15
`
`7
`8
`Subsequently, the cache slot 312 is released (step 614) and
`
`
`end of the positioned blocks. The remaining portion of the
`
`
`
`
`
`DCB is released (step 615).
`block is left as it is. In the case of data input/output to/from
`
`
`
`host computer having FBA format, the specified LEA
`The write data on the cache slot 312 is written into the
`
`
`
`
`
`(Logical Block Address) is accessed from the host computer.
`
`
`
`drives 315, 316 by the control processors 310, 311 asyn­
`
`
`
`chronously with the operation of the host computers 300, 5
`
`
`Now, conversion from FBA format data to CKD format
`
`
`
`303.In other words, the control processors 310, 311 retrieve
`data will be described.
`
`
`
`the cache memory and when data to be written into the drive
`In the case of data input/output to/from a host computer
`
`
`
`
`
`
`is found in the cache memory, it writes the data into the
`drive.
`
`having CKD format, a block having the C information of
`
`
`
`
`10 interest is searched and accessed from the specified C
`
`
`FIG. 7 is a flow chart showing the flow (700) of operation
`information.
`
`
`
`in DCB reservation operation (601) in FIG. 6.
`In the case of data input/output to/from a host computer
`
`
`
`
`
`Interprocessor exclusive information 402 of the DCB 400
`
`
`corresponding to the specified drive number 401 is preset
`
`
`having FBA format a block of specified LEA is accessed.
`(step 701).
`
`
`Since the method of conversion is well known, its detailed
`Subsequently, a determination is made as to whether the
`
`
`
`
`
`
`description will be omitted herein.
`
`
`
`interhost exclusive information is "on" or not (step 702).
`
`
`Although a magnetic di