CN119356625A

CN119356625A - Drive task management method, device and storage medium of tape library system

Info

Publication number: CN119356625A
Application number: CN202411944386.1A
Authority: CN
Inventors: 刘仁仕; 何梓轩; 朱剑文
Original assignee: Shenzhen Jetio Technology Co ltd
Current assignee: Shenzhen Jetio Technology Co ltd
Priority date: 2024-12-27
Filing date: 2024-12-27
Publication date: 2025-01-24
Anticipated expiration: 2044-12-27

Abstract

The application discloses a method, equipment and a storage medium for managing a driver task of a tape library system, and belongs to the technical field of data processing. After triggering the updating of a driver task, determining a tape task to be executed in a task queue to be executed, acquiring a driver state table, selecting an execution driver of the tape task to be executed according to the driver state table and the driver task updating, and adding an execution command of the tape task to be executed into a command queue corresponding to the execution driver. According to the magnetic tape task to be executed or the task state of the driver, which is received by the driver task management module, the resource scheduling is carried out on the driver, so that the response speed of the magnetic tape request with high priority is improved.

Description

Method, apparatus and storage medium for managing drive tasks of tape library system

Technical Field

The present application relates to the field of data processing technologies, and in particular, to a method, an apparatus, and a storage medium for managing a task of a drive of a tape library system.

Background

The magnetic tape library can disassemble and fill the magnetic tape through the mechanical arm, so that the automatic storage and retrieval of data are realized. When data on the tape is to be read from or written to, the tape library system directs the robotic arm to remove the tape from the tape slot and to place it in the tape drive to cause the drive to read and write data on an as-needed basis.

In the related art, a tape library system performs corresponding operations on a tape through a drive based on priority through priority scheduling of the tape. In order to avoid the waiting time process of the user, the tape storage system generally increases the priority of the tape read-back task so as to increase the response speed of data reading.

However, when the tape library system is in a high dump load state, all drive resources may be occupied by dump tasks. In this case, since the tape library system does not support preemption of tape requests that are not actively released, a persistent dump of tape that is not actively released by the dump task may result in tape resources that are read back from the task request being blocked at all times.

The foregoing is provided merely for the purpose of facilitating understanding of the technical solutions of the present application and is not intended to represent an admission that the foregoing is prior art.

Disclosure of Invention

The application mainly aims to provide a method, equipment and storage medium for managing a driver task of a tape library system, and aims to solve the technical problem that a continuous dump of a tape is not actively released by a dump task when the tape library system is in a high dump load state, so that the response waiting time of a read-back task request is overlong.

In order to achieve the above object, the present application provides a method for managing a drive task of a tape library system, which is applied to a drive task management module, wherein the drive management module is deployed in a data storage subsystem of the tape library system, and the method comprises the following steps:

after triggering the update of the driver task, determining a tape task to be executed in a task queue to be executed;

Acquiring a driver state table, and selecting an execution driver of the tape task to be executed according to the driver state table and the driver task update;

And adding the execution command of the tape task to be executed into a command queue corresponding to the execution driver.

In an embodiment, after triggering the update of the drive task, before determining the tape task to be executed in the task queue to be executed, the method further includes:

Scanning a driver message queue, and acquiring a driver message in the message queue according to a scanning result;

determining a message source driver for the driver message;

resetting the driver task state of the message source driver to idle in the driver state table;

And when the task queue to be executed is not empty, judging to trigger the task update of the driver.

In an embodiment, after the step of determining to trigger the update of the task of the driver when the task queue to be executed is not empty, the method further includes:

When a non-writing tape task exists in the task queue to be executed, matching the non-writing tape task with a processing tape of the message source driver;

Selecting the tape task to be executed from the non-writing tape tasks according to the matching result and/or the priority of the non-writing tape task;

Or when the non-writing tape task does not exist in the task to be executed, selecting the task to be executed from the tape tasks according to the matching result of the tape task and the processing tape in the task queue to be executed and/or the priority of the tape task.

acquiring the priority of a tape task in the task queue to be executed, and determining a priority execution task in the tape task according to the priority;

taking the priority execution task as the tape task to be executed;

and triggering the driver task update based on the tape task to be executed.

In an embodiment, before the step of triggering the update of the drive task based on the tape task to be performed, the method further includes:

acquiring a preset maximum number of non-writing tasks and the number of available drivers;

Taking the minimum value of the maximum non-writing task number and the available drive number as a non-writing task number threshold;

When the priority execution task is a non-writing tape task, sequencing the non-writing tape task based on the priority of the non-writing tape task and the task submitting time;

and scanning the non-writing tape tasks in sequence according to the sequencing result, setting the non-writing tape tasks which are sequenced before the non-writing task number threshold to be scheduled, and setting the non-writing tape tasks which are sequenced after the non-writing task number threshold to be non-scheduled.

In one embodiment, the step of triggering the drive task update based on the tape task to be performed further comprises:

adding the non-writing tape task to be scheduled into a temporary processing queue;

Matching the non-writing tape task with the driver task state of the scheduled driver, and determining a target driver in the scheduled driver according to a matching result;

transmitting a task interrupt command to the target drive, so that a drive task module interrupts a tape task currently executed by the target drive based on the interrupt command;

Setting the target drive to be preempted in the drive state table, and triggering the drive task of the target drive to update, wherein the drive task module controls the drive to execute the tape task on the target tape after the target tape is loaded into the target drive based on the updated tape task;

And removing the non-writing tape task in the temporary processing queue.

In an embodiment, after the step of determining the tape task to be executed in the task queue to be executed after the step of triggering the driver task update, the method further includes:

Obtaining driver information, and initializing a driver state table and a driver message queue in the driver task management module;

Generating a command queue of each driver according to the driver information, and starting a driver task for the driver;

and associating the driver task with a driver task state in the driver task management module.

In an embodiment, after the step of adding the execution command of the tape task to be executed to the command queue corresponding to the execution driver, the method further includes:

Determining a target tape task currently executed by an executing driver in a driver task module of the executing driver;

determining tape information of a target tape task;

determining the tape task to be executed corresponding to the tape information in the task queue to be executed;

And adding the tape task execution command to be executed into a command queue of the execution driver.

In addition, in order to achieve the above object, the present application also provides a drive task management device of a tape library system, the device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the computer program being configured to implement the steps of the drive task management method of a tape library system as described above.

In addition, in order to achieve the above object, the present application further provides a storage medium, which is a computer-readable storage medium, on which a computer program is stored, the computer program implementing the steps of the drive task management method of the tape library system as described above when being executed by a processor.

One or more technical schemes provided by the application have at least the following technical effects:

The application sets the driver task management module in the data storage subsystem of the tape library system, which can schedule the driver task after the high-priority read-write task appears or the driver completes the task, thereby improving the scheduling capability of the tape library system to the driver, improving the response speed of the driver to the high-priority tape request by actively adjusting the way of processing the task of the driver, and reducing the response waiting time of the high-priority tape request.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.

In order to more clearly illustrate the embodiments of the application or the technical solutions of the prior art, the drawings which are used in the description of the embodiments or the prior art will be briefly described, and it will be obvious to a person skilled in the art that other drawings can be obtained from these drawings without inventive effort.

FIG. 1 is a flow chart of a first embodiment of a method for managing drive tasks in a tape library system according to the present application;

FIG. 2 is a schematic diagram of a magnetic tape library system architecture according to a first embodiment of a method for managing drive tasks in a magnetic tape library system of the present application;

FIG. 3 is a flow chart of a second embodiment of a method for managing drive tasks in a tape library system according to the present application;

FIG. 4 is a flow chart of a third embodiment of a method for managing drive tasks in a tape library system according to the present application;

FIG. 5 is a flow chart of a fourth embodiment of a method for managing drive tasks in a tape library system according to the present application;

FIG. 6 is a schematic diagram of a drive task management device of a tape library system of a hardware runtime environment according to an embodiment of the present application.

The achievement of the objects, functional features and advantages of the present application will be further described with reference to the accompanying drawings, in conjunction with the embodiments.

Detailed Description

It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.

In order to better understand the above technical solutions, the following detailed description will refer to the accompanying drawings and specific embodiments.

The main solution of the embodiment of the application is that after the update of the driver task is triggered, the tape task to be executed in the task queue to be executed is determined, a driver state table is obtained, an execution driver of the tape task to be executed is selected according to the driver state table and the driver task update, and an execution command of the tape task to be executed is added into a command queue corresponding to the execution driver.

Because in the prior art, the tape library system performs corresponding operations on the tape by the drive based on priority through priority scheduling of the tape. In order to avoid the waiting time process of the user, the tape storage system generally increases the priority of the tape read-back task so as to increase the response speed of data reading. However, when the tape library system is in a high dump load state, all drive resources may be occupied by dump tasks. In this case, since the tape library system does not support preemption of tape requests that are not actively released, a persistent dump of tape that is not actively released by the dump task may result in tape resources that are read back from the task request being blocked at all times.

The application sets the driver task management module in the data storage subsystem of the tape library system, and can dispatch the driver task after the high-priority read-write task appears or the driver finishes the task, thereby improving the response speed of the driver to the high-priority tape request and reducing the response waiting time of the high-priority tape request in a mode of actively adjusting the driver to process the task.

In order to better understand the above technical solution, exemplary embodiments of the present application will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present application are shown in the drawings, it should be understood that the present application may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the application to those skilled in the art.

It should be noted that, the execution body of the present embodiment may be a driver task management module, or may be a computing service device with functions of data processing, network communication and program running, such as a tablet computer, a personal computer, a mobile phone, or an electronic device capable of implementing the above functions, a driver task management device of a tape library system, or the like, which is not limited in this embodiment. The present embodiment and the following embodiments will be described below by taking a driver task management module as an example.

Based on this, an embodiment of the present application provides a method for managing a drive task of a tape library system, and referring to fig. 1, fig. 1 is a flowchart of a first embodiment of a method for managing a drive task of a tape library system according to the present application.

In this embodiment, the method for managing a drive task of the tape library system includes steps S10 to S30:

step S10, after triggering the update of the driver task, determining a tape task to be executed in a task queue to be executed;

In this embodiment, the tape library system may be deployed in a server. The server can be a cloud server or terminal equipment such as a computer. The tape library system may access drives and robotic arms of the tape library to access and move disks in the tape library. The tape library comprises a drive slot, a storage slot and an import and export slot, wherein the drive slot is the slot where the drive is positioned, the storage slot is used for storing the tape, and the import and export slot is used for taking out the tape from the tape library or adding the tape to the tape library.

Further, the tape library system comprises a resource management subsystem and a data storage subsystem. The resource management subsystem is responsible for managing and scheduling the tape library resources, and can schedule the tape tasks based on the priority of the tape requests of the client and mount the target tapes corresponding to the tape requests. The data storage subsystem may then access the target tape by accessing the target tape based on the mounting path of the target tape and determine tape tasks to be performed by the target tape based on the tape request. Wherein the data storage subsystem may determine one or more tape tasks to perform based on one tape request based on the number of drives and the number of files to be processed in the tape request.

In the process that the tape library system executes the tape task through the drive, based on the condition that the data storage subsystem does not sense the drive, the data storage subsystem cannot call the drive occupied by the dump task in the high dump load state of the tape library system, so that the tape task other than the dump task, namely, the non-write tape task, is in the blocking state for a long time. For example, since the read-back task of the tape needs to return the read data to the client, and the dump task can be processed asynchronously by the tape library system in the background, the tape library system needs to process the read-back task preferentially, and the read-back task with high priority waits for a response for a long time due to the inability of the drive to release.

Specifically, as shown in fig. 2, fig. 2 is a schematic diagram of a tape library system architecture according to an embodiment of the present application. Referring to FIG. 2, a data storage subsystem includes a drive task management module and a drive task module. The driver task management module is responsible for scheduling driver tasks. Wherein a drive task is initiated for each drive configured for the data storage subsystem. And for each drive task, constructing a command queue of the drive, wherein the command queue is used for sending commands to the drive by the drive management module. For the driver task management module, a message queue is constructed for the driver task to send a message to the driver task management module.

Optionally, a tape library management agent module is also configured in the data storage subsystem and is responsible for carrying out remote procedure call on the resource management subsystem. The data storage subsystem allocates tape, releases tape, and loads tape to remote procedure calls that are primarily used by the resource management subsystem.

In an alternative embodiment for triggering the update of the driver task, step S10 may include steps S11 to S14:

s11, scanning a driver message queue, and acquiring a driver message in the message queue according to a scanning result;

step S12, determining a message source driver of the driver message;

S13, resetting the driver task state of the message source driver to be idle in the driver state table;

And S14, judging to trigger the driver task update when the task queue to be executed is not empty.

In this embodiment, the driver task management module periodically checks whether there is a driver message sent from the driver in the driver message queue based on a preset time in the system. The driver message comprises a message type, a message source driver name and a message source driver state. If the drive information exists, the drive task management module marks the information source drive as idle state, records the current tape information of the information source drive, and modifies the tape information in the drive state as idle. If the driver to preempt flag is true, the driver to preempt flag is reset to false.

For example, when the type of the drive message is a drive task end message, if the state of the message source drive is a readback state, the drive is indicated to end from readback, whether a file list in the tape readback task is empty is checked according to the recorded current tape of the message source, if so, the tape readback task is deleted, otherwise, a readback command is sent to the drive again. If the tape stock where the message source driver is located needs to be scheduled in the tape read-back task, the tape stock management submodule is requested to load the read-back tape to the message source driver, after the tape loading is completed by the driver, a read-back command is sent to a driver command queue, the driver task is recorded as being read-back, the processing is finished, and the tape read-back task is marked as scheduled. Otherwise, further checking whether the dump file list is empty, if not, requesting the available writable tape, then requesting to schedule the available writable tape to the drive, recording the drive task as being dumped, and then sending a dump command to the drive.

Specifically, when a non-writing tape task exists in the task queue to be executed, the driver task management module matches the non-writing tape task with the processing tape of the message source driver, and selects the tape task to be executed from the non-writing tape tasks according to the matching result and/or the priority of the non-writing tape task. Or when the non-writing tape task does not exist in the task to be executed, the driver task management module also selects the tape task to be executed from the tape tasks according to the matching result of the tape task and the processing tape in the task to be executed queue and/or the priority of the tape task.

For example, if there is a non-dump task to be scheduled, then the first matching non-write tape task is selected, the task tape is loaded to the drive, and a specific task execution command is sent to the message source drive, and the drive state table is updated. In the process of matching the non-writing magnetic tape task with the processing magnetic tape of the message source driver, the driver task management module firstly tries to match the magnetic tape used by the driver last time, namely, processes the magnetic tape, and the corresponding non-writing magnetic tape task is used for reducing the moving magnetic tape of the magnetic tape library as much as possible. Furthermore, the task tape added by the drive cannot be the tape currently in the dump state.

Otherwise, the driver task management module attempts to schedule the driver task as a dump task. First see if there is a writable tape currently not scheduled, otherwise allocate a new tape. After the writable tape is acquired, the writable tape is loaded into a drive, the drive is notified to perform a dump, and the drive task state table is updated.

Alternatively, the drive message type may be a drive failure message, or a drive dirty message. Wherein when the type of the drive message is a drive failure message, the drive failure state is recorded as true in the drive state table, and the task is not scheduled to the failed drive later. When the type of the drive message is a drive dirty message, the tape library management agent module requests to load the cleaning tape to the drive, records the state of the drive as being cleaned after the cleaning tape is loaded, and sends a cleaning command to the message source drive.

In another possible embodiment, the step S10 may include steps S15 to S17:

step S15, acquiring the priority of the tape task in the task queue to be executed, and determining the priority of the tape task to be executed according to the priority;

step S16, taking the priority execution task as the tape task to be executed;

And step S17, triggering the driver task update based on the tape task to be executed.

In this embodiment, the tape library system is provided with different task priorities based on the different types of tape tasks to be performed. For example, since the execution of the tape-back task is typically in the waiting process of the user, in order to avoid the waiting time of the user being too long, the task priority of the tape-back task may be set to be the highest. The tape dump task, tape garbage collection task, and tape initialization task may be set to a lower priority. The priority may be adjusted over time by the tape library system based on the latency of the task or other factors. When the driver task management system determines that the tape task with the priority higher than the priority threshold exists in the task queue to be executed, the tape task is used as a priority execution task, the driver resource preemption is carried out on the priority execution task, and the driver task management system is triggered to update the driver task.

Alternatively, when multiple tape tasks to be executed are received concurrently by the drive task management system, the order of execution of the tape tasks may be ordered based on the priority of the tape tasks.

In one embodiment, the drive task management module further updates the number of non-write tasks based on the non-write tape tasks before performing the drive task update. By acquiring a preset maximum non-writing task number and an available drive number, the minimum value of the maximum non-writing task number and the available drive number can be used as a non-writing task number threshold. And terminating the drive task update for the non-write tape task when the number of non-write tasks is greater than or equal to the non-write task number threshold. The non-writing tape tasks are other tape tasks except for the dump task in the tape tasks, and the number of the non-writing tape tasks is the number of the other tape tasks except for the dump task in the tape tasks.

Alternatively, the drive task management module may order the non-write tape tasks based on their priority and task commit time when the priority execution tasks are non-write tape tasks. Wherein, the higher the task priority of the non-writing tape task, the earlier the task commit time, the earlier the ordering. And sequentially scanning the non-writing tape tasks according to the sequencing result, and setting the non-writing tape tasks which are sequenced before the non-writing task quantity threshold value as to be scheduled by the driver task management module, and setting the non-writing tape tasks which are sequenced after the non-writing task quantity threshold value as to be non-to be scheduled.

It should be noted that, to avoid that the drive is in a state of waiting continuously for a dump task due to preemption of a high priority task such as a tape readback task, the drive task management module is set with a maximum number of readback tasks. The driver task management module counts the number of non-writing tasks to be scheduled, and when the number of the readback tasks to be scheduled is greater than or equal to the maximum number of the non-writing tasks or the number of available drivers, the driver preemption operation is stopped, so that stagnation of dump tasks is avoided. The drive task management module adds one to the current accumulated number of non-write tasks when determining one non-write tape task to be scheduled in the process of carrying out drive task scheduling. The number of the non-writing tasks is the number of the non-writing tape tasks which are determined to be required to be preempted by the drive, and the number of the non-writing tasks is the number of the tape tasks which are determined to be required to be preempted by the drive.

In an embodiment, when the driver state table with the idle driver task state does not exist, the driver task management module selects a target driver from the drivers with the dump task driver task state, and sends a task interrupt instruction to the target driver. The target drive is a drive that is available for preemption of non-write tape tasks. The driver task management module may update the driver task state of the target driver to be preempted in the driver state table.

Specifically, the driver task management module adds a non-writing tape task to be scheduled into a temporary processing queue, matches the non-writing tape task with the driver task state of the scheduled driver, and determines a target driver in the scheduled driver according to a matching result. And sending a task interrupt command to the target drive so that the drive task of the target drive interrupts the tape task currently executed by the target drive based on the interrupt command in the drive task module. Meanwhile, the driver task management module sets the target driver as to-be-preempted in the driver state table, triggers the driver task update of the target driver, and removes the non-writing tape task from the temporary processing queue. Wherein the drive task module controls the drive to perform a tape task on the target tape after the target tape is loaded into the target drive based on the updated tape task.

In one example, the driver task management module adds all non-write tasks to be scheduled to the temporary processing queue. If the tape of the non-writing task to be scheduled is already occupied by the dump task, such as reading the data on a certain tape currently being written, the dump task is interrupted, and the non-writing task is deleted from the temporary processing queue. The non-scheduled non-writing tape task is interrupted, specifically, a driver corresponding to the task can be found according to a driver task state table, an interrupt instruction is sent to the driver, each time a scheduled non-writing task is preempted, if the non-writing task temporary queue is not empty, the non-writing tape task is removed from the temporary processing queue. If the temporary processing queue of the non-writing task is still non-empty at the moment, judging whether the driver is in an idle state, sending a notification instruction for informing the driver of the idle state to the idle driver, and feeding back a message for enabling the driver to be in the idle state to a scheduling module so as to realize the subsequent scheduling processing of the idle message of the driver. Each time a notification is sent that itself is in an idle instruction, an element is deleted from the temporary processing queue. If the non-writing task temporary processing queue is still non-empty at this time, further judging whether the driver with the dump task state is not in an interrupt state, namely the state to be preempted. If so, the dump task is interrupted and the element is deleted from the temporary processing queue.

In another example, the drive task management module may first check whether the tape read back task has tape in the dump task. If so, an interrupt command is sent to the driver corresponding to the magnetic tape, the state of the driver is adjusted to be preempted, and the required scheduling mark of the magnetic tape read-back task is marked as true. Further, the drive task management module checks whether there is a drive in an idle state or a clean state. When there is a drive in an idle or clean state and the drive is in tape inventory where tape read-back tasks marked as false need to be scheduled, then marking the tape read tasks requires scheduling the mark as true. In addition, the driver task management module notifies itself of an idle command to be transmitted to the driver in an idle state therein. Still further, the drive task management module checks the drive in the dump state, and whenever a dump drive is found, and the dump drive is marked as false to be preempted, and the tape stock where the drive is located is in need of scheduling the tape read-back task marked as false, marks the tape read-back task as true, and sends a task interrupt command to the drive.

Optionally, if the file dump list is not empty and the existing drive is in an idle state, setting the latest check dump-free load to be zero, sending a notification self-idle command to the drive. If the file dump list is empty, and if the latest check dump-free load is zero, setting the latest check dump-free load as the current time. Otherwise, further checking the latest current time minus the latest check dump-free load to obtain continuous dump-free load, and when the configuration threshold is reached, representing that the data storage system has reached the dump-free load for a certain time, in order to reduce the power consumption of the idle state driver, sending a task interrupt command to all drivers currently in the dump state.

Step S20, a driver state table is obtained, and an execution driver of the tape task to be executed is selected according to the driver state table and the driver task update;

In this embodiment, the drive task management module includes a drive status table, in which drive task status, tape information, and failure information of the drive are recorded. The driver task management module can be matched with the action of updating the driver task or the tape task to be executed based on the driver task state in the driver state table, and select the driver to be executed from the drivers according to the matching result.

Specifically, the drive task update includes a readback task update, i.e., a drive preemption process that updates the drive's current executing task to a tape readback task. And the method also comprises the step of updating the idle driver, namely, after the driver is determined to finish executing tasks in a driver message queue and the state is updated to be idle, assigning tasks to the idle driver.

As an alternative implementation manner, when the drive task is updated to be the readback task, the drive task management module may select to execute the drive from the drives whose drive task states are to be preempted and/or idle.

As another alternative embodiment, when the driver task is updated to be an idle driver, the driver task management module may select a driver whose driver task state is idle as the executing driver.

And step S30, adding the execution command of the tape task to be executed into a command queue corresponding to the execution driver.

In this embodiment, the driver task management module performs control and task scheduling of the driver through the command queue. The task management module of the driver can terminate the task currently executed by the driver through a task termination command.

As an alternative implementation manner, when the tape task to be executed is a file dump task, the driver task management module triggers a dump operation based on the file to be dumped received by the server, and adds the file to be dumped to a dump file list. And the driver task management module sends a notification self-idle command to the driver task when checking that the dump file list is not empty. And the driver task receives the idle command of the driver task, and sends a task completion message to the message queue. And the driver task management module receives the driver task completion message, dispatches the magnetic tape to the driver, and sends a dump command to the driver. The driver task receives the dump command, switches to the driver dump task, takes the file information to be dumped from the dump file list, dumps the file information to the tape, and records the file dump information.

Specifically, after receiving the dump command, the driver task module switches the driver task to the dump task, acquires the driver tape information, and loads the tape onto the driver so that the driver performs read-write operation on the tape. And if the tape is in the initialized state, formatting the tape and switching to a writable state. The driver task module receives the information from the information queue in a periodic circulation mode, and marks the magnetic tape as a non-writable state and the circulation is exited if the task interrupt is received, the residual space of the magnetic disk is smaller than a set threshold value, the driver fails, the driver is dirty or the magnetic tape fails and the like. And sending the message to a message queue according to the cycle exit reason, and switching the drive to the idle state again.

As another alternative, when the tape task to be performed is a file read back task, the drive first determines whether there is a file to be read in the system cache data. And when the file is not present, acquiring a tape where the file is dumped based on dump information of the file to be read, and inserting the tape into a readback task. At this point, the required schedule of the read tape task is marked as false. The tape library system inserts the information of the tape file which needs to be read back into a read-back file list of the tape read-back task as a file item which needs to be read back, and waits for the read-back file to be processed.

Specifically, under the condition that no workload exists in the data storage sub-module, the driver task management module checks that the tape read-back task needs to be scheduled and marked as a false driver and an idle driver, marks the tape read-back task to be scheduled and marked as true, sends a self idle notification command to the driver, and the driver task receives the self idle notification command and sends a task processing completion message to the driver task management module. And under the condition that the dump load exists in the data storage submodule, the driver task management module checks that the tape read-back task needs to schedule the driver marked as false and being dumped, marks the tape read-back task needs to schedule the mark as true, and sends a task interrupt command to the dump driver. The dump driver task receives the task interrupt command, exits from the dump task, and sends a task processing completion message to the driver task management module.

Further, the drive task management module receives the task processing completion message, and if there is a read task that needs to be scheduled and marked as true, loads the requested tape library resource management subsystem onto the drive, marks the tape read task as scheduled, sets tape information in the drive state table as the read-back tape, and sets the drive state as the read-back state. A read back command is sent to the drive. The method comprises the steps that a driver task receives a readback command, obtains magnetic tape information on the driver according to a driver state table, finds a magnetic tape reading task, processes according to file items in the magnetic tape reading task, namely, reads a file from the magnetic tape back to a cache, and wakes up a readback file waiting process. Waiting for the flow to wake up, deleting the readback file item, and reading back the file content from the cache.

Optionally, a read-back command is received at the drive task module, the drive task is switched to the read-back task, the drive tape information is acquired, and the tape is loaded onto the drive, so that the drive performs read-write operation on the tape. The driver task module receives the messages in the message queue in the same cycle mode as the dump mode, and sends the exit reason to the driver message queue when exiting the cycle.

According to the embodiment of the application, the driver task management module is arranged in the data storage subsystem of the tape library system, so that the driver task can be scheduled after the high-priority read-write task appears or the driver finishes the task, the response speed of the driver to the high-priority tape request is improved in a mode of actively adjusting the processing task of the driver, and the response waiting time of the high-priority tape request is reduced.

Based on the same inventive concept, the present application further provides a second embodiment, and referring to fig. 3, fig. 3 is a schematic flow chart of a second embodiment of a method for managing tasks of a drive of a tape library system according to the present application.

In this embodiment, the drive task management of the tape library system includes steps S21 to S24:

s21, acquiring the driver state table and determining the driver task state of a driver in the driver state table;

Step S22, selecting the executing driver from the drivers with the driver task state to be preempted and/or idle when the driver task is updated to be the readback task;

Step S23, or when the driver task is updated to be an idle driver, selecting the driver with the idle driver task state as the executing driver;

And step S24, based on the tape task to be executed, updating the driver task state of the executing driver in the driver state table.

In this embodiment, the drive task management module may determine, based on the drive status table, a drive task status corresponding to all loaded drives of the tape library system. The driver can update the read-back task or the idle driver based on the driver task state, so that the driver is distributed more reasonably.

Further, after the allocation of the execution driver for the driver task update is completed, the driver task management module updates the driver task state of the execution driver to a driver task state consistent with the tape task to be executed in the driver state table.

Since the system described in the second embodiment of the present application is a system for implementing the method in the first embodiment of the present application, based on the method described in the first embodiment of the present application, a person skilled in the art can understand the specific structure and the modification of the system, and therefore, the description thereof is omitted herein. All systems used in the method according to the first embodiment of the present application are within the scope of the present application.

Based on the same inventive concept, the present application further provides a third embodiment, and referring to fig. 4, fig. 4 is a schematic flow chart of a third embodiment of a method for managing tasks of a drive of a tape library system according to the present application.

In this embodiment, the task management of the drive of the tape library system includes steps S01 to S03:

Step S01, obtaining driver information, and initializing a driver state table and a driver message queue in the driver task management module;

step S02, generating a command queue of each driver according to the driver information, and starting a driver task for the driver;

and step S03, associating the driver task with a driver task state in the driver task management module.

In this embodiment, the driver task management module needs to perform an initialization operation before performing driver task scheduling.

Specifically, the driver task module initializes a driver state table of memory states to represent the state of each driver. Including the current task state of the drive, current tape information on the drive, and whether the drive is malfunctioning. When the driver state table is initialized, each driver task state is in an idle state, the tape information is empty, if the driver is in a fault state already specified in the parameters of the driver configured by the data storage subsystem, the driver in the driver state table is marked as fault, otherwise, the driver is marked as normal.

Further, the driver task management module initializes an empty message queue, a command queue, and initiates a driver task for each configuration driver. The message queue is used for sending a message to the driver task management module by the driver task, the command queue is used for sending a command to the driver task module by the driver task management module, and the driver task management module enters a running state after initialization is completed.

Since the system described in the third embodiment of the present application is a system for implementing the method of the first embodiment of the present application, based on the method described in the first embodiment of the present application, a person skilled in the art can understand the specific structure and the modification of the system, and therefore, the description thereof is omitted herein. All systems used in the method according to the first embodiment of the present application are within the scope of the present application.

Based on the same inventive concept, the present application further provides a fourth embodiment, and referring to fig. 5, fig. 5 is a flowchart of a fourth embodiment of a method for managing tasks of a drive of a tape library system according to the present application.

In this embodiment, the drive task management of the tape library system includes steps S41 to S44:

step S41, in a driver task module of an executing driver, determining a target tape task currently executed by the executing driver;

step S42, determining the tape information of the target tape task;

step S43, determining the tape task to be executed corresponding to the tape information in the task queue to be executed;

and step S44, adding the tape task execution command to be executed into a command queue of the execution driver.

In this embodiment, in order to avoid the situation that the subsequent task still needs to schedule the tape after the driver completes the tape file operation and uninstalls the tape, and thus causes resource waste, the driver task module may control the tape to complete all tasks based on the tape task to be executed, and then uninstall the tape.

For example, assume that a certain period of time is applied to issue a read tape a file a1, a tape B file B1, and a tape a file a2, and that the maximum number of read-back tasks is set to 1, because the read-back task of tape a arrives first, the drive task management module schedules a certain drive to load tape a for processing. The file read-back task of the magnetic tape B is limited by the resource of the drive, although the read-back task is submitted, the read-back task of the magnetic tape B cannot be scheduled until the magnetic tape A finishes processing, the read-back task of the drive sequentially processes the files a1 and a2 on the magnetic tape A, and after the processing, all file items of the read-back task of the magnetic tape A are deleted, and the read-back task of the drive is ended. The driver management module receives the driver processing task completion message, and further checks that a read-back file list of the magnetic tape on the driver is empty because the message source task state is read-back, and deletes the read-back magnetic tape A task, and at the moment, the read scheduling task is 0. It is checked that the current number of read-scheduled tasks is less than the maximum number of read-back tasks 1, and at this time, there are read tasks for tape B, and the subsequent tape B read tasks are scheduled. In this way, the task scheduling of the drive can avoid the problem of unloading tape A after the completion of the reading of a1, while still requiring the reading of a2 in tape A after the completion of the reading of B1 in tape B.

The application can avoid resource waste by reasonably distributing the tape processing resources through the driver task management module, thereby improving the processing efficiency of the tape request.

Since the system described in the fourth embodiment of the present application is a system for implementing the method of the first embodiment of the present application, based on the method described in the first embodiment of the present application, a person skilled in the art can understand the specific structure and the modification of the system, and therefore, the description thereof is omitted herein. All systems used in the method according to the first embodiment of the present application are within the scope of the present application.

The application provides a drive task management device of a tape library system, which comprises at least one processor and a memory in communication connection with the at least one processor, wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the drive task management method of the tape library system in the first embodiment.

Referring now to FIG. 6, there is shown a schematic diagram of a drive task management device suitable for use in a tape library system embodying embodiments of the present application. The drive task management device of the tape library system in the embodiment of the present application may include, but is not limited to, a mobile terminal such as a mobile phone, a notebook computer, a digital broadcast receiver, a PDA (Personal DIGITAL ASSISTANT: personal digital assistant), a PAD (Portable Application Description: tablet), a PMP (Portable MEDIA PLAYER: portable multimedia player), an in-vehicle terminal (e.g., an in-vehicle navigation terminal), and the like, a fixed terminal such as a digital TV, a desktop computer, and the like. The drive task management device of the tape library system shown in fig. 6 is merely an example, and should not impose any limitation on the functionality and scope of use of embodiments of the present application.

As shown in fig. 6, the drive task management device of the tape library system may include a processing means 1001 (e.g., a core processor, a graphic processor, etc.), which may perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 1002 or a program loaded from a storage means 1003 into a random access Memory (RAM: random Access Memory) 1004. In the RAM1004, various programs and data required for the operation of the drive task management device of the tape library system are also stored. The processing device 1001, the ROM1002, and the RAM1004 are connected to each other by a bus 1005. An input/output (I/O) interface 1006 is also connected to the bus. In general, a system including an input device 1007 such as a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc., an output device 1008 including a Liquid crystal display (LCD: liquid CRYSTAL DISPLAY), a speaker, a vibrator, etc., a storage device 1003 including a magnetic tape, a hard disk, etc., and a communication device 1009 may be connected to the I/O interface 1006. The communicator 1009 may allow the drive task management device of the tape library system to communicate wirelessly or by wire with other devices to exchange data. While a drive task management device is shown for a tape library system having various systems, it should be understood that not all of the illustrated systems are required to be implemented or provided. More or fewer systems may alternatively be implemented or provided.

In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through a communication device, or installed from the storage device 1003, or installed from the ROM 1002. The above-described functions defined in the method of the disclosed embodiment of the application are performed when the computer program is executed by the processing device 1001.

The driver task management device of the tape library system provided by the application adopts the driver task management method of the tape library system in the embodiment, and can solve the technical problem that the continuous dump of the tape is not actively released by the dump task under the high dump load state of the tape library system, so that the response waiting time of a read-back task request is overlong. Compared with the prior art, the beneficial effects of the driver task management device of the tape library system provided by the application are the same as those of the driver task management method of the tape library system provided by the embodiment, and other technical features of the driver task management device of the tape library system are the same as those disclosed in the method of the previous embodiment, which are not described in detail herein.

It is to be understood that portions of the present disclosure may be implemented in hardware, software, firmware, or a combination thereof. In the description of the above embodiments, particular features, structures, materials, or characteristics may be combined in any suitable manner in any one or more embodiments or examples.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

The present application provides a computer readable storage medium having computer readable program instructions (i.e., a computer program) stored thereon for performing the drive task management method of the tape library system in the above-described embodiments.

The computer readable storage medium provided by the present application may be, for example, a U disk, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, or device, or a combination of any of the foregoing. More specific examples of a computer-readable storage medium may include, but are not limited to, an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access Memory (RAM: random Access Memory), a Read-Only Memory (ROM), an erasable programmable Read-Only Memory (EPROM: erasable Programmable Read Only Memory or flash Memory), an optical fiber, a portable compact disc Read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In this embodiment, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, or device. Program code embodied on a computer readable storage medium may be transmitted using any appropriate medium, including but not limited to electrical wiring, fiber optic cable, RF (Radio Frequency) and the like, or any suitable combination of the foregoing.

The computer readable storage medium may be included in the drive task management device of the tape library system or may exist alone without being assembled into the drive task management device of the tape library system.

The computer readable storage medium is loaded with one or more programs, and when the one or more programs are executed by the driver task management device of the tape library system, the driver task management device of the tape library system determines a tape task to be executed in a task queue to be executed after triggering the update of the driver task, acquires a driver state table, selects an execution driver of the tape task to be executed according to the driver state table and the driver task update, and adds an execution command of the tape task to be executed into a command queue corresponding to the execution driver.

Computer program code for carrying out operations of the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of remote computers, the remote computer may be connected to the user's computer through any kind of network, including a local area network (LAN: local Area Network) or a wide area network (WAN: wide Area Network), or may be connected to an external computer (for example, through the Internet using an Internet service provider).

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The modules involved in the embodiments of the present application may be implemented in software or in hardware. Wherein the name of the module does not constitute a limitation of the unit itself in some cases.

The readable storage medium provided by the application is a computer readable storage medium, and the computer readable storage medium stores computer readable program instructions (namely computer program) for executing the method for managing the task of the driver of the tape library system, so that the technical problem that the response waiting time of a read-back task request is overlong because a dump task does not actively release the continuous dump of a tape when the tape library system is in a high dump load state can be solved. Compared with the prior art, the beneficial effects of the computer readable storage medium provided by the application are the same as the beneficial effects of the drive task management method of the tape library system provided by the above embodiment, and are not described in detail herein.

The foregoing description is only a partial embodiment of the present application, and is not intended to limit the scope of the present application, and all the equivalent structural changes made by the description and the accompanying drawings under the technical concept of the present application, or the direct/indirect application in other related technical fields are included in the scope of the present application.

Claims

1. A method for managing drive tasks of a tape library system, the method being applied to a drive task management module disposed in a data storage subsystem of the tape library system, the method comprising the steps of:

2. The method of claim 1, wherein after triggering the drive task update, before the step of determining a tape task to be performed in the task queue to be performed, further comprising:

determining a message source driver for the driver message;

3. The method of claim 2, wherein after the step of determining to trigger the driver task update when the task queue to be executed is not empty, further comprising:

4. The method of claim 1, wherein after triggering the drive task update, before the step of determining a tape task to be performed in the task queue to be performed, further comprising:

taking the priority execution task as the tape task to be executed;

and triggering the driver task update based on the tape task to be executed.

5. The method of claim 4, wherein prior to the step of triggering the drive task update based on the tape task to be performed, further comprising:

6. The method of claim 5, wherein triggering the drive task update based on the tape task to be performed further comprises:

And removing the non-writing tape task in the temporary processing queue.

7. The method of claim 1, wherein after triggering the driver task update, before the step of determining the tape task to be performed in the task queue to be performed, further comprising:

8. The method of claim 1, wherein after the step of adding the execution command of the tape task to be executed to the command queue corresponding to the execution driver, further comprising:

determining tape information of a target tape task;

9. A drive task management device of a tape library system, characterized in that the device comprises a memory, a processor and a computer program stored on the memory and executable on the processor, the computer program being configured to implement the steps of the drive task management method of a tape library system according to any one of claims 1 to 8.

10. A storage medium, wherein the storage medium is a computer readable storage medium, and wherein the storage medium has stored thereon a computer program which, when executed by a processor, implements the steps of the drive task management method of the tape library system of any of claims 1 to 8.