Browse Prior Art Database

Method to supply additional disk capacity on demand Disclosure Number: IPCOM000022451D
Original Publication Date: 2004-Mar-15
Included in the Prior Art Database: 2004-Mar-15
Document File: 1 page(s) / 5K

Publishing Venue



Low cost hard drives with larger capacities can be procured and inserted into systems. Drives can be customized to ship with smaller size configurations for custom bids without having many different size hard drives on hand, thus providing IBM with a cost savings. If the customer runs out of hard drive space, the un-used space can be recovered with no loss of down-time due to migration concerns. Since this method follows the sweet spot on the hard drives, inventory of obsolete hard drives is drastically reduced as the sweet spot drives are clipped to produce lower size drives required by large enterprise customers.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 100% of the total text.

Page 1 of 1

Method to supply additional disk capacity on demand

Hard drives on systems are configured to use all the space available. When the hard drive fills up, either files must be deleted or the hard drive is upgraded to a larger model and the data must be painfully migrated from the smaller drive to the larger drive. Additionally, when hard drives are procured from different vendors, different size hard drives are available. Older and/or smaller drives may incur a cost above the current industry standard or cost sweet-spot. To insure consistency, the vendors are required to bios strip the drives to a common configuration size.

Using the SetMax command built into IDE devices for PARTIES enablement, we can clip the disk capacity locally without requiring the hard drive vendor to clip the disk space with a custom firmware adjustment. This can be accomplished with setting a password with the SetMax command. This could be achieved by generating a password defined by using the drive serial number or another disk characteristic. An alternative to using vendor specific data can be achieved by using a public/private key and encoding the drive password using either the private or public half of the key. The disk can be sold to the customer in a reduced capacity as part of a system, with the option for the customer to upgrade the size when they need it at the time they need it. When the customer chooses to update, they would buy the password to unlock the remaining capacity.