Search Images Maps Play YouTube News Gmail Drive More »
Sign in
Screen reader users: click this link for accessible mode. Accessible mode has the same essential features but works better with your reader.

Patents

  1. Advanced Patent Search
Publication numberUS20040044800 A1
Publication typeApplication
Application numberUS 10/231,331
Publication dateMar 4, 2004
Filing dateAug 27, 2002
Priority dateAug 27, 2002
Also published asUS6704810
Publication number10231331, 231331, US 2004/0044800 A1, US 2004/044800 A1, US 20040044800 A1, US 20040044800A1, US 2004044800 A1, US 2004044800A1, US-A1-20040044800, US-A1-2004044800, US2004/0044800A1, US2004/044800A1, US20040044800 A1, US20040044800A1, US2004044800 A1, US2004044800A1
InventorsStanley Krehbiel, David Ulrich
Original AssigneeKrehbiel Stanley E., Ulrich David J.
Export CitationBiBTeX, EndNote, RefMan
External Links: USPTO, USPTO Assignment, Espacenet
Method for handling persistent reservation registrations in a storage device
US 20040044800 A1
Abstract
Persistent reservations may be processed on an as-needed basis after a power cycle sequence. A computer storage device may have persistent reservations for various volumes that are to be deleted after a power cycle but before accepting any reservation I/O requests for those volumes. After a start up sequence, the device comes on-line prior to deleting the required registrations. Prior to the first reservation I/O request for the particular volume, the registrations are processed for that volume and the necessary registrations are deleted.
Images(4)
Previous page
Next page
Claims(8)
What is claimed is:
1. A method for processing persistent reservations after a power cycle in a computer storage device with multiple volumes comprising:
completing a power-on sequence after a power cycle;
setting the status of said storage device to receive I/O requests;
receiving a reservation I/O request for a volume of said storage device, said volume having at least one persistent reservation that is to persist through a restart but not a power cycle;
determining that a power cycle has occurred and that said reservation is not to persist after said power cycle;
performing at least some processing on said reservation; and
processing said reservation I/O request.
2. The method of claim 1 wherein said power-on sequence comprises setting a power-on bit for each of said multiple volumes, said power-on bit being used to indicate if at least one registration for said volume must be deleted prior to accepting said I/O request.
3. The method of claim 1 wherein said computer storage device is a SCSI device.
4. The method of claim 1 wherein said processing on said reservation comprises deleting at least one registration.
5. A computer storage device of multiple volumes with reservations that persist after a reset but not a power cycle comprising:
a storage medium comprising multiple volumes; and
a controller for said storage device adapted to completing a power-on sequence after a power cycle, setting the status of said storage device to receive I/O requests, receiving a reservation I/O request for a volume of said storage device, said volume having at least one persistent reservation that is to persist through a restart but not a power cycle, determining that a power cycle has occurred and that said reservation is not to persist after said power cycle, performing at least some processing on said reservation, and processing said reservation I/O request.
6. The computer storage device of claim 5 further comprising:
a power-on bit for each of said multiple volumes wherein said power-on bit indicates if at least one registration must be deleted prior to processing a reservation I/O request for said volume.
7. The computer storage device of claim 5 wherein said computer storage device is a SCSI device.
8. The computer storage device of claim 5 wherein said processing on said reservation comprises deleting at least one registration.
Description
BACKGROUND OF THE INVENTION

[0001] a. Field of the Invention

[0002] The present invention pertains generally to disk storage devices and specifically to the management of reservations with disk storage devices.

[0003] b. Description of the Background

[0004] Reservations are used in storage devices for allowing only certain users or computers to execute commands to the devices. For example, a reservation may allow certain users, also known as an initiator port or host, to read or write to a volume on a device. In some cases, a host may be given exclusive permission to write to a volume while several other hosts may be given permission to read the volume.

[0005] Persistent reservations are a way for hosts to reserve space on a storage device in a way that the reservation can survive a reset or a power cycle. In order for a storage device to support this type of activity, it must make certain information persistent. In some instances, persistent reservations may be required to survive a reset but not a power cycle. Such reservations must therefore be processed and deleted or removed when the power cycle occurs.

[0006] For a reservation to be set for a particular host, the host must first be registered with the volume. Registration involves logging the particular host with the volume. Such logs of registrations may be quite lengthy and complex in some instances. The commands used for processing registrations may be a subset of the reservation commands. When a reservation is to persist through a reset but not a power cycle, both the reservations and the registrations must be cleared after the power cycle.

[0007] When a storage device of this type is reset or powered-on, a great deal of activity occurs in preparing the device for I/O activity. Additionally, the device must be ready to respond to I/O requests within a short time. For a device with 256 volumes and 512 host ports, over 524,000 registrations may need to be managed during the start up period. The time consumed with management of such a large amount of records may be prohibitive when performing a start-of-day routine. Such devices with persistent reservations may be SCSI storage devices such as hard disks or storage systems with removable media such as a disk changer.

[0008] It would therefore be advantageous to provide a method for handling a large amount of registrations during a power-on phase of a storage device. It would be further advantageous if the method were able to bring the device into useful service as quickly as possible, while being able to handle large amounts of registration processing.

SUMMARY OF THE INVENTION

[0009] The present invention overcomes the disadvantages and limitations of the prior art by providing a device and method for managing a large amount of registrations after restarting the device by processing the registrations on an as-needed basis. As a volume responds to a reservation request for the first time after power-on, the registrations for that volume will be processed in preparation for the first input or output command. Further, during periods of inactivity, volumes that have not been processed may be processed.

[0010] The present invention may therefore comprise a method for processing persistent reservations after a power cycle in a computer storage device with multiple volumes comprising: completing a power-on sequence after a power cycle; setting the status of the storage device to receive I/O requests; receiving a reservation I/O request for a volume of the storage device, the volume having at least one persistent reservation that is to persist through a restart but not a power cycle; determining that a power cycle has occurred and that the reservation is not to persist after the power cycle; performing at least some processing on the reservation; and processing the reservation I/O request.

[0011] The present invention may further comprise a computer storage device of multiple volumes with reservations that persist after a reset but not a power cycle comprising: a storage medium comprising multiple volumes; and a controller for the storage device adapted to completing a power-on sequence after a power cycle, setting the status of the storage device to receive I/O requests, receiving a reservation I/O request for a volume of the storage device, the volume having at least one persistent reservation that is to persist through a restart but not a power cycle, determining that a power cycle has occurred and that the reservation is not to persist after the power cycle, performing at least some processing on the reservation, and processing the reservation I/O request.

[0012] The advantages of the present invention are that the storage device may resume handling of input and output commands quickly after restart. Rather than performing all of the registration processing prior to resuming the first I/O command, little or no registration processing is performed prior to resuming I/O commands. Thus, the device may come on-line as fast as possible. Further, during periods of inactivity after coming on-line, any registration processing that is required for other volumes may be performed, eliminating any processing prior to the first access of those volumes.

BRIEF DESCRIPTION OF THE DRAWINGS

[0013] In the drawings,

[0014]FIG. 1 is an illustration of a work flow diagram of an embodiment of the present invention wherein persistent reservations are handled after the power-on sequence is completed.

[0015]FIG. 2 is an illustration of an embodiment of the present invention wherein the status of three volumes of a storage device is shown during several phases of startup and operation.

[0016]FIG. 3 is an illustration of a work flow diagram of an embodiment of the present invention wherein persistent reservations are processed.

DETAILED DESCRIPTION OF THE INVENTION

[0017]FIG. 1 illustrates a work flow diagram of an embodiment 100 of the present invention wherein persistent reservations are handled after the power-on sequence is completed. After the power-on sequence in step 102, the storage device is brought online in step 104. If there is no reservation I/O request in step 106, reservations and/or registrations may optionally be processed during idle time in step 108. When an I/O request is received in step 106, and the I/O request is not a reservation request in step 109, the I/O request is processed in step 111. When an I/O request is received in step 106, and the I/O request is a reservation request in step 109, and the reservations and/or registrations for the particular volume has not been processed in step 110, the reservations and/or registrations are processed in step 112 before the reservation I/O request is performed in step 114. If the reservations and/or registrations have already been processed in step 110, the reservation 110 request is performed in step 114.

[0018] The embodiment 100 provides a method whereby registrations are processed for each volume when the first reservation I/O request is received for that volume. A reservation I/O request is one that effects the reservation or registration of the particular volume. General I/O requests, such as read and write requests, would be handled as if no reservation exists, since the reservation was not to persist through the power cycle.

[0019] During the power on sequence of step 102, the reservation was deleted. However, the registration list, which may be quite lengthy, has not been deleted and other clean-up processing has not occurred.

[0020] It is necessary that the registrations be processed before a reservation I/O request is executed. However, to process all of the registrations prior to bringing the device online may add considerable time to the startup process. This delay may be substantial, possibly on the order of a few minutes, and may be unacceptable. The embodiment 100 brings the device on-line prior to processing the registrations, and only processes those registrations for each volume as reservation I/O commands are received for that volume. The embodiment 100 essentially spreads the lengthy processing time for the registrations across reservation I/O requests for each individual volume. The processing time for each volume may be a matter of a few seconds, which may be almost unnoticeable. Further, after the initial processing is completed for a volume, the processing will not be required again.

[0021] The processing of step 112 may include deleting registrations that do not persist after a power cycle. In addition, cleaning up the database records of the various registrations and reservations associated with the volume may be finalized at this time. Those skilled in the arts may incorporate other volume-specific processing tasks or routines while maintaining within the scope and intent of the present invention.

[0022] The embodiment 100 provides a method whereby registrations may be optionally processed during idle time in step 108. This optional processing may allow the registrations of some volumes to be processed after the device is brought on-line. By using idle time after startup to process registrations, the device may be on-line sooner and also avoid the delay of processing of step 112.

[0023]FIG. 2 illustrates the status of three volumes of a device during several phases of startup and operation with an embodiment of the present invention. The normal operating conditions 202 of the various volumes 204 are shown. For volumes 1 and 3, the remove after power-on bit 206 is set to true. This means that the reservations for those volumes should be deleted only after cycling the power of the device, but not if a ‘warm boot’ or reset is performed. The remove after power-on bit 206 is set to false for volume 2. This means that the reservations for volume 2 are to persist even after a complete power cycle. The power up bit 208 is a flag that indicates if the registration list for the particular volume needs to be processed prior to executing a reservation I/O command. The registration list column 210 indicates the status of the registration lists.

[0024] Immediately after startup 212, the processing of the registration lists have not occurred. The power up bit 218 for volumes 1 and 3 are set to true, indicating that no reservation I/O requests can be executed until the registration lists 220 are processed. The registration list for volume 2 does not need to be processed, since the remove after power-on bit 216 is set to false. Thus, the power up bit 218 is likewise set to false, indicating that no further processing is necessary.

[0025] When a reservation I/O request is received for volume 3 in table 222, the registration list 230 for volume 3 is processed with new data and the power up bit 228 is set to false. At this point, no reservation I/O requests have been received for volume 1, and thus the power up bit 228 for volume 1 is set to true. When a reservation 110 request is received for volume 1, the registration list 230 would be processed and the status would return to normal operating conditions 202.

[0026]FIG. 3 illustrates an embodiment 300 of the present invention in a work flow diagram. The start of day processing is completed in step 302. If the start of day processing was due to a power-on condition in step 304, the power up flag is set to true for all volumes where the remove after power-on bit is set to true in step 306. If the start of day processing was due to something other than a power-on condition, such as a warm restart, the step 306 is skipped. When a reservation I/O request is received in step 308 and the remove after power-on bit is set to true in step 310, the registration list is cleared in step 312 and the reservation I/O request is processed in step 314.

[0027] The foregoing description of the invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed, and other modifications and variations may be possible in light of the above teachings. The embodiment was chosen and described in order to best explain the principles of the invention and its practical application to thereby enable others skilled in the art to best utilize the invention in various embodiments and various modifications as are suited to the particular use contemplated. It is intended that the appended claims be construed to include other alternative embodiments of the invention except insofar as limited by the prior art.

Referenced by
Citing PatentFiling datePublication dateApplicantTitle
US7370128 *Oct 29, 2004May 6, 2008Intel CorporationExpander device capable of communication protocol translation
US7418545Oct 28, 2004Aug 26, 2008Intel CorporationIntegrated circuit capable of persistent reservations
Classifications
U.S. Classification710/1
International ClassificationG11C7/20, G11C7/24
Cooperative ClassificationG11C7/20, G11C7/24
European ClassificationG11C7/24, G11C7/20
Legal Events
DateCodeEventDescription
Jun 6, 2014ASAssignment
Effective date: 20070406
Free format text: CHANGE OF NAME;ASSIGNOR:LSI LOGIC CORPORATION;REEL/FRAME:033102/0270
Owner name: LSI CORPORATION, CALIFORNIA
May 8, 2014ASAssignment
Free format text: PATENT SECURITY AGREEMENT;ASSIGNORS:LSI CORPORATION;AGERE SYSTEMS LLC;REEL/FRAME:032856/0031
Effective date: 20140506
Owner name: DEUTSCHE BANK AG NEW YORK BRANCH, AS COLLATERAL AG
Sep 2, 2011FPAYFee payment
Year of fee payment: 8
Jun 20, 2007FPAYFee payment
Year of fee payment: 4
Aug 27, 2002ASAssignment
Owner name: LSI LOGIC CORPORATION, CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KREHBIEL, STANLEY E., JR.;ULRICH, DAVID J.;REEL/FRAME:013254/0928
Effective date: 20020822
Owner name: LSI LOGIC CORPORATION 1551 MCCARTHY BOULEVARD MAIL
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KREHBIEL, STANLEY E., JR. /AR;REEL/FRAME:013254/0928