Dataset overwrite protection

By detecting and analyzing write operations in the storage system and performing data protection operations, the problem of difficult detection and diagnosis of data set coverage errors in the data storage environment is solved, and the security and reliability of the data storage environment are improved.

CN112579000BActive Publication Date: 2024-12-06INTERNATIONAL BUSINESS MACHINE CORPORATION
View PDF 8 Cites 0 Cited by

Patent Information

Application Number
CN202011016147.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-09-30
Filing Date
2020-09-24
Publication Date
2024-12-06
Estimated Expiration
2040-09-24

AI Technical Summary

Technical Problem

Dataset coverage errors in existing data storage environments are difficult to detect and diagnose, and commonly used general-purpose tracking tools are inefficient in blocking dataset coverage and can lead to data loss and system interruptions.

Method used

By detecting write operations in the storage system, analyzing relevant metadata, determining whether the storage area contains valid data, and if included, data protection operations are performed to prevent write operations or record detailed information, and prevent data overwriting.

Benefits of technology

Effectively diagnose and prevent data overwrites, reduce system overhead, improve the reliability of the data storage environment, and avoid data loss and system interruption.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112579000B_ABST
    Figure CN112579000B_ABST
Patent Text Reader

Abstract

The present disclosure relates to data set overwrite protection. A method for preventing data overwrite in a data storage system is disclosed. In one embodiment, the method detects a write operation to a storage area of ​​the data storage system. The write operation includes one or more of a format write operation and a full track write operation. When the write operation is detected, the method determines a data set associated with the storage area. The method analyzes metadata associated with the data set to determine whether the storage area contains valid data. If the storage area contains valid data, the method performs a data protection operation, which prevents the write operation from being performed and / or records detailed information of the write operation. A corresponding system and computer program product are also disclosed.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to systems and methods for preventing data overwriting in a data storage environment. Background Art

[0002] Data generated by computing systems are often susceptible to errors. For example, in a network environment where multiple users may access the same production data at the same time, the sensitivity of production data to errors is high. One type of error that can occur in such an environment is a data set overwrite. Due to this error, data is incorrectly written over previously stored data, thereby corrupting and potentially causing the previously stored data to be irreversibly lost. For example, a data overwrite may occur when data from a first data set is mistakenly written over data from a second data set. This may be caused by program errors, malicious activity, human error, etc. In an environment where production data is mirrored from a primary location to a secondary location, errors associated with data set overwrites may also be mirrored, resulting in loss or corruption of data at the secondary location. Data set overwrites can have a huge impact on the data storage environment, not only causing data loss, but also system outages.

[0003] Unfortunately, data set overwrites can be extremely difficult to detect and diagnose in data storage environments. Current detection and diagnosis methods in z / OS environments typically utilize Generic Trace Facility (GTF) tracing to detect and diagnose data set overwrites. However, this type of tracing can require significant overhead to perform. Typically, it does not prevent data set overwrites from occurring. Furthermore, unless and until a data set overwrite is detected and logged soon after it occurs, the GTF trace data typically wraps (i.e., overwrites itself) thereby eliminating the data needed for diagnosis and making it unusable to service personnel.

[0004] In view of the foregoing, there is a need for systems and methods to more effectively diagnose and prevent data overwriting. Ideally, such systems and methods would reduce overhead compared to diagnostic utilities such as the Generic Trace Tool (GTF) or other utilities. Summary of the invention

[0005] The present invention has been developed in response to the current state of the art, and in particular in response to the problems and needs in the prior art that have not been fully solved by currently available systems and methods. Therefore, embodiments of the present invention have been developed to prevent data overwriting in a data storage environment. The features and advantages of the present invention will become more fully apparent from the following description and the appended claims, or may be learned by the practice of the present invention as described below.

[0006] Consistent with the foregoing, a method for preventing data overwriting in a data storage system is disclosed. In one embodiment, the method detects a write operation to a storage area of ​​a data storage system. The write operation includes one or more of a format write operation and a full track write operation. Upon detecting the write operation, the method determines a data set associated with the storage area. The method analyzes metadata associated with the data set to determine whether the storage area contains valid data. If the storage area contains the valid data, the method performs a data protection operation that prevents the write operation from being performed and / or records detailed information of the write operation.

[0007] Corresponding systems and computer program products are also disclosed and claimed herein. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] In order to readily understand the advantages of the present invention, the invention briefly described above will be described in more detail by reference to specific embodiments shown in the accompanying drawings. Understanding that these drawings depict only typical embodiments of the invention and are therefore not to be considered limiting of the scope of the invention, the present invention will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

[0009] Figure 1 is a high-level block diagram illustrating an example of a network environment in which systems and methods according to the present invention may be implemented;

[0010] Figure 2 is a high-level block diagram showing the Figure 1 An embodiment of a storage system for use in a network environment;

[0011] Figure 3 is a high-level block diagram illustrating a data overwrite prevention module configured to prevent data overwrite in a storage system;

[0012] Figure 4 is a high-level block diagram showing the platters, tracks, and cylinders within a disk drive;

[0013] Figure 5 is a high-level block diagram illustrating storage space in a data set; and

[0014] Figure 6 is a flow chart illustrating one embodiment of a method for preventing data overwriting in a storage system. DETAILED DESCRIPTION

[0015] It will be readily understood that the components of the present invention, as generally described and illustrated in the drawings herein, may be arranged and designed in a variety of different configurations. Accordingly, the following more detailed description of embodiments of the present invention, as illustrated in the drawings, is not intended to limit the scope of the claimed invention, but is merely representative of certain examples of presently contemplated embodiments of the present invention. The presently described embodiments will be best understood with reference to the drawings, wherein like parts are represented by like numerals throughout.

[0016] The present invention may be embodied as a system, method, and / or computer program product. The computer program product may include a computer-readable storage medium having computer-readable program instructions thereon for causing a processor to execute aspects of the present invention.

[0017] A computer-readable storage medium may be a tangible device that can retain and store instructions used by an instruction execution device. A computer-readable storage medium may be, for example, but not limited to, an electronic storage system, a magnetic storage system, an optical storage system, an electromagnetic storage system, a semiconductor storage system, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of computer-readable storage media includes the following: a portable computer floppy disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory. Only memory (EPROM or flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanical encoding device such as a punch card or a raised structure in a groove on which instructions are recorded, and any suitable combination of the foregoing. As used herein, a computer-readable storage medium should not be understood as being a transient signal per se, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating through a waveguide or other transmission medium (e.g., a light pulse passing through a fiber optic cable) or an electrical signal transmitted by a wire.

[0018] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to a corresponding computing / processing device via a network (e.g., the Internet, a local area network, a wide area network), or downloaded to an external computer or external storage system, a local area network, and / or a wireless network. The network can include copper transmission cables, optical transmission fibers, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. The network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions to be stored in a computer-readable storage medium in the corresponding computing / processing device.

[0019] Computer readable program instructions for performing operations of the present invention may be assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state setting data, or any source code or object code written in any combination of one or more programming languages ​​(including object-oriented programming languages ​​such as Smalltalk, C++, etc.) and conventional procedural programming languages ​​(such as the "C" programming language or similar programming languages).

[0020] The computer-readable program instructions may be executed entirely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter case, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (for example, via the Internet using an Internet service provider). In some embodiments, electronic circuits including, for example, programmable logic circuits, field programmable gate arrays (FPGAs), or programmable logic arrays (PLAs) may be executed by utilizing the state information of the computer-readable program instructions to personalize the electronic circuits to perform various aspects of the present invention.

[0021] Various aspects of the present invention may be described herein with reference to the flowcharts and / or block diagrams of the methods, devices (systems) and computer program products according to embodiments of the present invention. It will be understood that each frame of the flowchart illustration and / or block diagram and the combination of frames in the flowchart illustration and / or block diagram may be implemented by computer-readable program instructions.

[0022] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to generate a mechanism so that the instructions are executed by a computer or other processor to execute a programmable data processing device to create a device for implementing the functions / actions specified in the flowchart and / or block diagram box. These computer-readable program instructions can also be stored in a computer-readable storage medium, which can instruct a computer, a programmable data processing device, and / or other equipment to function in a particular manner, so that the computer-readable storage medium in which the instructions are stored. An article of manufacture including instructions, the article of manufacture including instructions for implementing various aspects of the functions / actions specified in the flowchart and / or block diagram box.

[0023] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing device, or other device, so that a series of operational steps are performed on the computer, other programmable device, or other device to produce a computer-implemented process, so that the instructions executed on the computer, other programmable device, or other device implement the functions / actions specified in the flowchart and / or block diagram blocks.

[0024] Reference Figure 1 , an example of a network environment 100 is shown. The network environment 100 is presented to illustrate an example of an environment in which the systems and methods according to the present invention can be implemented. The network environment 100 is presented by way of example and not limitation. In fact, in addition to the network environment 100 shown, the systems and methods disclosed herein can be applied to a variety of different network environments.

[0025] As shown, the network environment 100 includes one or more computers 102, 106 interconnected by a network 104. The network 104 may include, for example, a local area network (LAN) 104, a wide area network (WAN) 104, the Internet 104, an intranet 104, etc. In some embodiments, the computers 102, 106 may include a client computer 102 and a server computer 106 (also referred to herein as a "host" 106 or a "host system" 106). Typically, the client computer 102 initiates a communication session, while the server computer 106 waits for and responds to requests from the client computer 102. In some embodiments, the computer 102 and / or the server 106 may be connected to one or more internal or external directly attached storage systems 109 (e.g., arrays of hard disk drives, solid state drives, tape drives, etc.). These computers 102, 106 and the directly attached storage systems 109 may communicate using protocols such as ATA, SATA, SCSI, SAS, Fibre Channel, etc.

[0026] In some embodiments, the network environment 100 may include a storage network 108 behind the server 106, such as a storage area network (SAN) 108 or a LAN 108 (e.g., when network attached storage is used). The network 108 may connect the server 106 to one or more storage systems, such as an array 110 of hard disk drives or solid state drives, a tape library 112, a single hard disk drive 114 or solid state drive 114, a tape drive 116, a CD-ROM library, etc. To access the storage systems 110, 112, 114, 116, the host system 106 may communicate through a physical connection from one or more ports on the host 106 to one or more ports on the storage systems 110, 112, 114, and 116. The connection may be made through a switch, a fabric, a direct connection, etc. In some embodiments, the server 106 and the storage systems 110, 112, 114, 116 may communicate using a networking standard or protocol such as Fibre Channel (FC) or iSCSI.

[0027] Reference Figure 2 , an example of a storage system 110 including an array of hard disk drives 204 and / or solid state drives 204 is shown. The storage system 110 is shown to illustrate an exemplary environment in which errors such as data overwrites may occur. As shown, the storage system 110 includes a storage controller 200, one or more switches 202, and one or more storage drives 204, such as hard disk drives 204 and / or solid state drives 204 (e.g., flash-based storage drives 204). The storage controller 200 can enable one or more host systems 106 (e.g., open systems and / or mainframe servers 106 running operating systems such as z / OS, zVM, or the like) to access data in the one or more storage drives 204.

[0028] In selected embodiments, the storage controller 200 includes one or more servers 206a, 206b. The storage controller 200 may also include a host adapter 208 and a device adapter 210 to connect the storage controller 200 to the host system 106 and the storage drive 204, respectively. Multiple servers 206a, 206b may provide redundancy to ensure that data is always available to the connected host system 106. Therefore, when one server 206a fails, another server 206b may assume the I / O load of the failed server 206a to ensure that I / O can continue between the host system 106 and the storage drive 204. This process may be referred to as "failover".

[0029] In selected embodiments, each server 206 may include one or more processors 212 and memory 214. The memory 214 may include volatile memory (e.g., RAM) and non-volatile memory (e.g., ROM, EPROM, EEPROM, hard disk, flash memory, etc.). In certain embodiments, the volatile and non-volatile memory may store software modules that run on the processor 212 and are used to access data in the storage drive 204. These software modules may manage all read and write requests to the logical volume 322 implemented on the storage drive 204.

[0030] With similar Figure 2 An example of a storage system 110 of the illustrated architecture is an IBM DS8000 TM Enterprise storage system. DS8000 TM It is a high-performance, large-capacity storage controller that provides disk and solid-state storage and is designed to support continuous operation. However, the technology disclosed in this article is not limited to IBM DS8000 TM Rather, the present invention is not intended to be used as an enterprise storage system 110, but rather may be implemented in any comparable or similar storage system 110, regardless of the manufacturer, product name, or components or component names associated with the system 110. Any storage system that may benefit from one or more embodiments of the present invention is considered to fall within the scope of the present invention. Therefore, the IBM DS8000 is described by way of example only and not limitation. TM .

[0031] Reference Figure 3 , such as Figure 1 and 2 The illustrated environment may store and provide access to data that is susceptible to errors. Because such an environment may enable multiple users (potentially simultaneously) to access the same product, the sensitivity of the product data to errors is high. One type of error that may occur in such an environment is a data set overwrite. Due to this error, new or existing data is erroneously overwritten over previously stored data, thereby corrupting and potentially causing the irreversible loss of the previously stored data. In an environment where production data is mirrored from a primary location to a secondary location, errors and / or corruption associated with data set overwrites may also be mirrored, resulting in data loss or corruption at the secondary location.

[0032] Unfortunately, in situations such as Figure 1 and 2In the environment shown, data set overwrites can be difficult to detect and diagnose. Current detection and diagnosis methods in z / OS environments typically utilize Generalized Trace Facility (GTF) tracing to detect and diagnose data set overwrites. However, this type of tracing can require significant overhead to perform. Typically, it does not prevent data set overwrites from occurring. In addition, unless data set overwrites are detected and logged soon after they occur, GTF trace data may wrap, thereby eliminating the data needed for diagnosis and making it unavailable to service personnel. Therefore, systems and methods are needed to more effectively diagnose and prevent data set overwrites.

[0033] In some embodiments, the data overwrite prevention module 300 may be implemented on the host system 106 to prevent data overwriting on the storage system 110 . Figure 3 is a high-level module block diagram showing a data overwrite prevention module 300 and related submodules. The data overwrite prevention module 300 and the associated submodules can be implemented in hardware, software, firmware, or a combination thereof. The data overwrite prevention module 300 and the associated submodules are presented by way of example and not limitation. In different embodiments, more or fewer submodules may be provided. For example, the functions of some submodules may be combined into a single or fewer number of submodules, or the functions of a single submodule may be distributed over multiple submodules.

[0034] As shown, the data overwrite prevention module 300 may include one or more of a detection module 302, a determination module 304, an identification module 306, an analysis module 308, a data determination module 310, a protection module 312, a permission module 318, an application verification module 320, and a block size verification module 322. The protection module 312 may include a module 320 and a block size verification module 322. The protection module 312 may include one or more of a prevention module 314 and a logging module 316. As shown, the data overwrite prevention module 300 and associated sub-modules are implemented within the host system 106. However, the data overwrite prevention module 300 and associated sub-modules are not limited to being implemented within such a host system 106.

[0035] As shown, the detection module 302 can be configured to detect certain types of write operations that may be associated with or more likely to cause data overwriting. For example, in some embodiments, the detection module 302 can be configured to detect format write operations and / or full track write operations. When storage space is allocated to a data set 336 (i.e., a named set of records), the tracks of the data set 336 can be formatted using format write operations. These format write operations can particularly establish the block size of the track. Once formatted, the track is usually not formatted again. If any write operation occurs to the formatted track, if it does not conform to the established block size associated with the track, an I / O error will usually be generated. Therefore, the data overwrite prevention module 300 can be configured to check any format write operations performed on the track after it has been formatted to ensure that it does not cause unexpected data overwriting.

[0036] In contrast, a full track write operation may replace the entire contents of a track with another full track image, including any formatting associated with the block size. The data overwrite prevention module 300 may also be configured to check full track write operations performed on a track to ensure that they do not result in undesired data overwrites. Thus, in some embodiments, the detection module 302 may be configured to detect when a write operation such as a format write operation and / or a full track write operation (hereinafter referred to as a "write operation") is performed on a data set 336 on the storage system 110. .

[0037] When a format write operation and / or a full track write operation is detected, the determination module 304 can be configured to determine what data set 336 is the target of the write operation. In some embodiments, this can be achieved by analyzing metadata such as CCHH (cylinder and head number) and CCW (channel command word) associated with the write operation. For reference, Figure 4 A high-level view of a disk drive 204 is shown, which includes a plurality of platters 402, tracks 404 on the platters, and cylinders 406 consisting of corresponding tracks 404 across the plurality of platters 402. The write operations discussed above may be directed to tracks 404 and cylinders 406 in the disk drive 204. In some embodiments, the track 404 hosting the data set 336 may be determined by analyzing metadata associated with the data set 336 in one or more of the VTOC 334, the directory 332, and / or a VSAM volume data set (VVDS).

[0038] Reference again Figure 3Once the data set 336 associated with the write operation is determined, the identification module 306 can identify metadata associated with the data set 336, and the analysis module 308 can analyze the metadata to determine whether the data set 336 has a data protection feature enabled, and the incoming write operation can be verified for possible data overwrite issues. This can be achieved by analyzing indicators that can be set for the data set 336 (e.g., in the volume table of the directory or VTOC) and / or the volume 330 where the data set 336 resides. Therefore, the data protection feature can be enabled for the data set 336 and / or volume 330 to enable verification of the write operation at the data set 336 and / or volume 330 level.

[0039] If validation is enabled for the data set 336, the data determination module 310 can determine whether the write operation is directed to valid data in the data set 336. That is, the data determination module 310 can determine whether the write operation is directed to a portion 504 of the data set 336 that contains valid data 506, or to a portion 502 of the data set 336 that is empty or does not contain valid data 506, as shown in FIG. Figure 5 As shown. If the data set 336 is a virtual storage access method (VSAM) data set 336, information in a directory 332 can be analyzed in some embodiments to determine the high used relative byte address (HURBA) value. This value can be converted to a CCHH value representing the last track in the data set 336 that has been written with valid data. Any tracks beyond this point generally do not contain valid data. For non-VSAM data sets 336, the DS1LSTAR and DS1TRBAL values ​​in the VTOC 334 can be checked to determine the location of the end of the valid data in the data set 336.

[0040] If a write operation (i.e., a format write operation or a full track write operation) is directed to an area (e.g., a track) containing valid data in a data set 336, the protection module 312 can perform operations to protect the valid data and prevent data overwriting. In some cases, depending on the data protection characteristics, the prevention module 314 within the protection module 312 can terminate the write operation, thereby preventing the write operation from occurring. In other cases, the logging module 316 can record the details of the write operation. That is, the write operation can be allowed to occur, but the logging module 316 can collect additional information about the write operation. In some embodiments, this information can be provided to service personnel so that they can analyze the information to determine whether data overwriting or other errors have occurred due to the write operation.

[0041] If the write operation is not directed to an area (e.g., a track) in the data set 336 that contains valid data, the permission module 318 may allow the write operation to occur. That is, since the write operation will not affect or overwrite valid data, the permission module 318 may allow the format write operation and / or the full track write operation to occur on the data set 336. In some embodiments, the application verification module 320 may determine whether the write operation originates from a trusted application. If the write operation originates from a trusted application, the permission module 318 may allow the write operation to occur even if the write operation does affect or overwrite valid data.

[0042] In certain embodiments, in the event that a storage area (e.g., a track) within data set 336 does not contain valid data but is still within the data range of data set 336, block size verification module 322 may determine whether the block size associated with the write operation corresponds to the block size established for the rest of data set 336. This may help determine whether the write operation is valid or an error. If the CCW for the write operation contains a block size value that is inconsistent with the rest of data set 336, the write operation may be rejected (i.e., not sent to the channel between host system 106 and storage system 110), and depending on whether the data protection features discussed above are enabled for data set 336, a diagnostic dump may be performed and / or a log entry may be created.

[0043] Reference Figure 6 , shows one embodiment of a method 600 for preventing data overwriting in the storage system 110. In some embodiments, this method 600 may be performed by the previously described data overwriting prevention module 300. The method 600 is merely an example of how the data overwriting prevention module 300 works and is not intended to be limiting.

[0044] As shown, method 600 initially determines 602 whether a format write operation or a full track write operation has been received. If so, method 600 determines 604 whether the write operation originates from a trusted application. If so, method 600 allows 606 the write operation to be performed.

[0045] If the write operation does not originate from a trusted application, the method 600 determines 608 a data set 336 associated with the write operation. In certain embodiments, this may be accomplished by analyzing the CCHH and CCW values ​​associated with the write operation and determining the data set 336 corresponding to the values. Once the data set 336 is determined 608, the method 600 determines 610 whether the data set 336 has an enabled data protection feature. In other words, the method 600 determines 610 whether the write operation should be verified. If the data protection feature is not enabled, the method 600 allows the write operation 606 to be performed on the data set 336.

[0046] If, on the other hand, the data protection feature is enabled, the method 600 identifies and analyzes 612 metadata associated with the data set 336 (e.g., directory 332, VTOC 334, etc.). This may be done to determine where valid data ends up within the allocated storage space 500 of the data set 336. At this point, the method 600 determines 614 whether the write operation will overwrite valid data in the data set 336. If so, the method 600 performs 616 a data protection operation to protect the valid data. In some embodiments, the data protection operation involves rejecting the write operation so that it does not modify the data set 336. In other embodiments, if and when a data protection operation is performed for the data set 336, the data protection operation performs logging to collect additional information about the write operation.

[0047] In the event that the write operation does not overwrite valid data, the method 600 can check 618 whether the block size associated with the write operation is consistent with the block size of the other portion of the data (e.g., track) set 336. If not, the method 600 performs the previously described data protection function by rejecting the write operation and / or recording the details of the write operation. On the other hand, if the block size associated with the write operation is consistent with the block size of the rest of the data set 336, the method 600 allows 606 the write operation to be performed for the data set 336.

[0048] The flow chart and / or block diagram in the accompanying drawings illustrate the possible implementation architecture, function and operation of the system, method and computer-usable medium according to various embodiments of the present invention. In this regard, each box in the flow chart or block diagram can represent a module, segment or part of a code, which includes one or more executable instructions for realizing a specified logical function. It should also be noted that in some alternative embodiments, the function indicated in the box may not occur in the order indicated in the figure. For example, depending on the function involved, the two boxes shown in succession can actually be executed substantially simultaneously, or sometimes these boxes can be executed in reverse order. It should also be noted that each box of the block diagram and / or flow chart description and the combination of the boxes in the block diagram and / or flow chart description can be implemented by a system based on special-purpose hardware that performs a specified function or action, or a combination of special-purpose hardware and computer instructions.

Claims

1. A method for preventing data from being overwritten in a data storage system, the method comprising: detecting a write operation to a storage area of ​​a data storage system; determining whether the write operation is at least one of a format write operation and a full track write operation; determining a data set associated with the storage area; analyzing metadata associated with the data set to determine a last track of the data set that has been written with valid data, wherein analyzing the metadata comprises: determining a High Use Relative Byte Address (HURBA) value associated with the data set, and converting the High Use Relative Byte Address (HURBA) value to a Cylinder and Head Number (CCHH) value to determine the last track; and In response to determining that the storage area does not extend beyond the last track and the write operation is at least one of a format write operation and a full track write operation, a data protection operation is performed, the data protection operation including at least one of preventing the write operation and recording details of the write operation.

2. The method according to claim 1, further comprising: In response to determining that the storage region extends beyond the last track, the write operation to the storage region is permitted.

3. The method according to claim 1, further comprising: In response to determining that the storage area does not extend beyond the last track but the write operation originates from a trusted application, allowing the write operation to be performed on the storage area.

4. The method according to claim 1, further comprising: In response to determining that the storage region is beyond the last track but the storage region is within the allocated space of the data set, it is determined whether a block size associated with the write operation complies with a block size associated with the data set.

5. The method according to claim 4, further comprising: In response to determining that a block size associated with the write operation does not conform to a block size associated with the data set, preventing the write operation from being performed on the storage area.

6. The method according to claim 4, further comprising: In response to determining that the block size associated with the write operation complies with the block size associated with the data set, the write operation is allowed to be performed on the storage area.

7. A computer program product, the computer program product comprising: One or more computer-readable storage media and program instructions stored on the one or more computer-readable storage media, wherein the program instructions can be read and executed by one or more computer processors to implement the steps included in the method according to any one of claims 1 to 6.

8. A computer system, the computer system comprising: one or more computer processors; one or more computer-readable storage media; as well as Program instructions stored on a computer-readable storage medium, the program instructions being executed by at least one of the one or more computer processors, the program instructions comprising corresponding program codes for implementing the steps included in the method according to any one of claims 1 to 6.

9. A computer device, comprising one or more logic modules, wherein the one or more logic modules are respectively configured to implement corresponding steps included in the method according to any one of claims 1 to 6.

Citation Information

Patent Citations

  • Systems, methods and computer program products for operating a data processing system

    CN101354715A

  • Method and equipment for retrieving data in storage system

    CN102651009A

  • Managing write operations to an extent of tracks migrated between storage devices

    CN102884502A

  • Data writing method and device and computer readable storage medium

    CN110286853A

  • Virtual worm method and system

    US20030126359A1