US20060090058A1 - Method and data storage system for providing multiple partition support - Google Patents
Method and data storage system for providing multiple partition support Download PDFInfo
- Publication number
- US20060090058A1 US20060090058A1 US10/973,485 US97348504A US2006090058A1 US 20060090058 A1 US20060090058 A1 US 20060090058A1 US 97348504 A US97348504 A US 97348504A US 2006090058 A1 US2006090058 A1 US 2006090058A1
- Authority
- US
- United States
- Prior art keywords
- data storage
- partition
- partitions
- lba
- address
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0638—Organizing or formatting or addressing of data
- G06F3/0644—Management of space entities, e.g. partitions, extents, pools
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0604—Improving or facilitating administration, e.g. storage management
- G06F3/0605—Improving or facilitating administration, e.g. storage management by facilitating the interaction with a user or administrator
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/0671—In-line storage system
- G06F3/0673—Single storage device
- G06F3/0674—Disk device
- G06F3/0676—Magnetic disk device
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0638—Organizing or formatting or addressing of data
- G06F3/0643—Management of files
Definitions
- the present invention relates generally to data storage. More particularly, the invention relates to methods and apparatus which allow host devices without multiple partition support to utilize the full storage capacity of multiple partition data storage systems.
- FAT16 file systems Systems using a file allocation table (FAT) which employs 16 bits for addressing clusters of data are known as “FAT16 file systems”.
- a FAT16 file system is limited to 2 Gbytes per partition. Storage devices with a capacity of more than 2 Gbytes, and with which a FAT16 file system is used, therefore tend to have multiple partitions, each with no more than 2 Gbytes of capacity.
- the 2 Gbyte barrier of the FAT16 file system partition limit is imposed by the maximum number of clusters and the largest cluster size supported by the FAT16 file system.
- the FAT16 file system is limited to 65,525 clusters.
- the size of a cluster must be a power of 2, and be less than 65,536 bytes. This results in a maximum cluster size of 32,768 bytes (32 Kbytes). Multiplying the maximum number of clusters (65,525) by the maximum cluster size (32,768) equals 2 Gbytes.
- the first partition is typically referred to as the “primary partition.” Everything not stored in the primary partition is stored in an “extended partition.”
- a utility program for example the “Fdisk” utility program, is used to create, delete or modify partitions on a storage system.
- the Fdisk utility program is a DOS utility used to configure and partition storage systems to prepare them for DOS use.
- the Fdisk utility software creates only one primary DOS partition (commonly referred to as “PRI DOS”) on a physical disc of a disc drive data storage system.
- PRI DOS primary DOS partition
- Other utility programs can also be used to create, delete or modify partitions.
- FAT32 file allocation table which employs 32 bits for addressing clusters of data
- a host device does not support multiple partitions for FAT16, it can only access the primary partition of its associated storage device. This in turn wastes the capacity of the storage device beyond the 2 Gbyte limit.
- Embodiments of the present invention provide solutions to these and/or other problems, and offer other advantages over the prior art.
- An apparatus of the present invention includes partition selection circuitry configured to selectably provide individual access to multiple ones of a plurality of partitions of a data storage component by a host device without multiple partition support.
- the apparatus can also include the data storage component and/or the host device.
- the partition selection circuitry uses a logical block addressing (LBA) address generated by the host device, and an operating mode indicator indicative of a particular partition, to allow the partitions of the data storage component to be accessed by the host device without multiple partition support. Methods implemented by the apparatus are also disclosed.
- LBA logical block addressing
- FIG. 1 is an isometric view of a disc drive type data storage system.
- FIGS. 2 and 3 are block diagrams illustrating systems, apparatus and components in which the present invention can be embodied.
- FIG. 3-1 is a diagrammatic illustration of a first method embodiment of the present invention, in conjunction with components of a system of the present invention.
- FIG. 3-2 is a mapping table which maps combinations of LBA addresses and partition or mode numbers to a storage component's native LBA addresses.
- FIG. 4-1 is a diagrammatic illustration of a second method embodiment of the present invention, in conjunction with components of a system of the present invention.
- FIG. 4-2 is a translation table which demonstrates how the translation engine shown in FIG. 4-1 translates LBA addresses and partition numbers into native LBA addresses.
- FIG. 5 is a flow diagram illustrating a general method of the present invention.
- FIG. 1 is an isometric view of a disc drive 100 with which embodiments of the present invention are useful.
- Disc drive 100 represent a data storage device or component which can be partitioned and accessed by a host device.
- Disc drive 100 includes a housing with a base 102 and a top cover (not shown).
- Disc drive 100 further includes a disc pack 106 , which is mounted on a spindle motor (not shown) by a disc clamp 108 .
- Disc pack 106 includes a plurality of individual discs, which are mounted for co-rotation about central axis 109 .
- Each disc surface has an associated disc head slider 110 which is mounted to disc drive 100 for communication with the disc surface.
- FIG. 1 is an isometric view of a disc drive 100 with which embodiments of the present invention are useful.
- Disc drive 100 represent a data storage device or component which can be partitioned and accessed by a host device.
- Disc drive 100 includes a housing with a base 102 and
- sliders 110 are supported by suspensions 112 which are in turn attached to track accessing arms 114 of an actuator 116 .
- the actuator shown in FIG. 1 is of the type known as a rotary moving coil actuator and includes a voice coil motor (VCM), shown generally at 118 .
- VCM voice coil motor
- Voice coil motor 118 rotates actuator 116 with its attached heads 110 about a pivot shaft 120 to position heads 110 over a desired data track along an arcuate path 122 between a disc inner diameter 124 and a disc outer diameter 126 .
- Voice coil motor 118 is driven by servo electronics 130 based on signals generated by heads 110 and a host computer (not shown).
- disc drive 100 is intended to represent any of a variety of data storage devices or components in which, or with which, the methods and apparatus of the present invention can be implemented.
- disc drive 100 can be other types of magnetic disc drives, or can be other types of non-magnetic disc drives such as an optical disc drive, a magneto-optical disc drive, etc.
- system 250 includes a host device 210 and a data storage device or component 200 .
- host device 210 represents any type of host device with a legacy FAT16 file systems (i.e., without multiple partition support).
- the present invention is not limited to host devices with FAT16 file systems, but instead is extendible, for example for use with any host device without multiple partition support.
- Data storage component 200 is a data storage system or device, such as disc drive 100 , having a data storage capacity in excess of the maximum partition size with which the host device is configured to work.
- data storage component 200 has a capacity in excess of the 2 Gbyte per partition limit described above.
- data storage component 200 is configured to provide multiple partitions.
- Partition selection circuitry 220 of system 250 can include hardware and/or software switches or other components or modules which are used to selectably provide to host device 210 individual access to multiple ones of the partitions of data storage component 200 . Partition selection circuitry 220 , and related methods of the present invention, are described below particularly with reference to FIGS. 3-1 , 3 - 2 , 4 - 1 , 4 - 2 and 5 .
- partition selection circuitry 220 can be implemented independently, with the host device, or with the data storage component.
- dashed lines surrounding host device 210 and partition selection circuitry 220 represent that these components can be combined into a single system or apparatus 230 .
- dashed lines surrounding data storage component 200 and partition selection circuitry 220 represent that these components can be combined into a single system or apparatus 240 of a larger system 260 .
- the present invention includes methods, and corresponding apparatus, which allow host devices with legacy FAT16 file systems (i.e., without multiple partition support) to utilize the full storage capacity of a disc drive or other data storage device.
- These methods can be implemented, for example, in the various components and apparatus illustrated in FIGS. 2-1 and 2 - 2 .
- the capacity of the data storage device is divided into multiple partitions, each of which cannot exceed 2 Gbytes in size.
- Partition selection circuitry for example in the form of software and/or hardware switches, allows a user of the host device and data storage device to switch between the different partitions.
- Software switches can be embodied in suitably programmed processing circuitry.
- Hardware switches can be jumpers (i.e., jumper settings) or dipswitches which can be manipulated by the user to set the mode of operation in the manner described below. Other types of hardware switches can be used as well. Hardware switches provide the advantage, relative to software switches, of not requiring the data storage device to be programmed before switching between different partitions. Software switches provide the advantage, relative to hardware switches, of not requiring extra hardware. Further, in one particular example embodiment, the number of jumpers/dipswitches used limits the number of partitions which can be supported. This is not true for software switches.
- the host device (and/or the user) must provide both the logical block addressing (LBA) address and an operating mode indicator (for example through switches) which represents the partition number to be accessed. If the operating mode indicator or partition number is not specified, then a default partition is assumed.
- LBA logical block addressing
- an operating mode indicator for example through switches
- a first method embodiment is diagrammatically illustrated in conjunction with corresponding components of a host device, partition selection circuitry, and a data storage component.
- the disc drive or other data storage component treats each partition as an independent storage unit. All partitions share the same partition LBA address space (as opposed to the “native” LBA address space of the storage component), as is illustrated in FIG. 3-1 .
- storage component or device 200 with a capacity of 5 Gbytes is used. It is divided into three partitions which are less than the 2 Gbyte limit, partition 1 (reference number 302 ), partition 2 (reference number 304 ) and partition 3 (reference number 306 ).
- a fourth partition, partition 0 (reference number 308 ) includes the entire 5 Gbytes of the data storage component.
- the partition LBA address space of the smaller partitions is 0 to 0x3FFAC4 (partition 1 ), 0 to 0x3FFAC4 (partition 2 ), and 0 to 0x201CC6 (partition 3 ), respectively, as is shown in FIG. 3-1 .
- Table 1 shown in FIG. 3-2 is a mapping table which maps combinations of host generated LBA addresses (for a FAT16 system) and partition or mode numbers to the storage component's native LBA addresses. If host device 210 has a legacy FAT16 file system, the host generated LBA address can range from 0-3F,FAC4.
- the host generated LBA address can have a different range (for example the illustrated 0-A0,1250).
- All three partitions 302 / 304 / 306 are formatted as the primary partition, as at any one time there is only one single partition accessible when switching between the three.
- the LBA address space for the single larger partition (partition 0 ), encompassing the three smaller partitions, is in this particular example 0 to A0,1250.
- a software/hardware switch 310 allows the user/host device to switch between the different partitions 302 / 304 / 306 of the data storage component. This limits drive capacity to 5, 2, 2 and 1 Gbyte when switching between partitions 0 through 3 , respectively.
- the software/hardware switch 310 forms at least a portion of partition selection circuitry 220 shown in FIGS. 2-1 and 2 - 2 .
- partition 0 the full capacity of the data storage component from LBA 0 to 0xA0,1250 will always be assumed. Thereafter, the host device provides the LBA address and this same LBA address will be used to access the data sector with the specific (or default) partition.
- the LBA address is provided by address generating circuitry, modules or components 320 of host device 210 .
- the mode or partition number can be provided by partition designating circuitry, modules or components 325 of host device 210 .
- the partition number is provided to the storage component 200 by the user through switches 310 , for example in the form of jumper settings. In any event, switches 310 use the partition number to determine which partition of component 200 that the provided LBA address corresponds to.
- circuitry 320 shown in FIG. 3-1 is illustrated as generating an LBA address of between 0 and A0,1250 (i.e., for a FAT32 system), for a FAT16 system the LBA addresses generated by the host device will be between 0 and 3F,FAC4.
- FIG. 4-1 a second method embodiment is diagrammatically illustrated in conjunction with corresponding components of a host device, partition selection circuitry, and a data storage component.
- the data storage component 200 again has a capacity of 5 Gbytes.
- the data storage component 200 is still divided into three partitions which are each less than the 2 Gbyte limit, but with each partition having different partition LBA address spaces, and the address spaces from one partition to the next being continuous.
- the three partitions are illustrated as partition 1 (reference number 402 ), partition 2 (reference number 404 ) and partition 3 (reference number 406 ). Overall, the three partitions span an address space from 0 to 0xA01250. The address spaces of these three partitions are illustrated in FIG. 4-1 .
- an address translation engine 410 accepts the host device generated LBA address and partition number (for example through switches) from host device 210 (and/or from the user in the case of the partition number in some embodiments), and converts them into a drive native LBA address.
- the translation engine forms, in some embodiments, at least a portion of partition selection circuitry 220 shown in FIGS. 2-1 and 2 - 2 .
- translation engine 410 is integrated or included with data storage component 200 . However, in other embodiments, translation engine 410 is separate from the data storage component.
- the first 2 Gbyte partition 402 is formatted as the primary partition, and the other partitions (i.e., 404 and 406 ) are formatted as extended partitions with individual logic volume.
- Other drive configurations can also be used, such as formatting the 5 Gbyte storage component into five partitions with 1 Gbyte size each.
- Table 2 shown in FIG. 4-2 is a translation table which demonstrates how the translation engine 410 translates host generated LBA addresses, and partition numbers, into native LBA addresses. Again, if the partition number is not specified, the default mode 0 (partition 0 represented at 408 ) corresponding to the entire 5 Gbytes of the data storage component 200 is assumed by translation engine 410 . When a partition other than partition 0 is specified, translation engine 410 translates the host generated LBA address and partition number into a native LBA address to allow access by the host device 210 to the corresponding partition or partition extension. For example, when mode 2 (partition 2 represented at 404 ) is chosen, the first partition of the extended partition of data storage component 200 is accessible by host device 210 .
- All LBA addresses generated by the host device are therefore offset by address translation engine 410 by the size of the first or primary partition 402 , which in this example is 0x3FFAC5.
- This can be computed using the first partition table information available in the primary Master Boot Record (MBR).
- MBR Primary Master Boot Record
- the capacity of the storage device will be capped by the size of the currently selected partition, which can be found in the first partition table information in the extended MBR (at 0x3FFAC5). This avoids reading/writing beyond the partition capacity.
- the two method embodiments described above with reference to FIGS. 3-1 , 3 - 2 , 4 - 1 and 4 - 2 provide little difference for host devices, such as digital cameras or other electronic devices, which use FAT16 file systems without multiple partition support.
- the data storage component will appear to the host to be a single 2 Gbyte (maximum) storage device.
- the first method and apparatus embodiments e.g., FIG. 3-1
- all partitions are formatted as the primary partition.
- One issue which arises using this method is that once the storage is reset to the default configuration (mode or partition 0 in this example), only the default partition is accessible, even for host devices which support multiple partitions. Examples of host devices which are likely to have multiple partition support include personal digital (or data) assistants (PDAs) and personal computers (PCs).
- PDAs personal digital (or data) assistants
- PCs personal computers
- the first method embodiment can result in certain inconveniences in some practical applications. For example, consider the case of the data storage component being used with a digital camera (or other host device) without multiple partition support, with the second 2 Gbyte partition (partition 2 ) being selected.
- the data storage component is reset to the default configuration and plugged into a PDA, a PC or other host device for further processing. Since the data is stored in the second partition, but the other host device sees only the default partition, extra steps may be necessary to retrieve the data.
- the drive is formatted into two main partitions.
- the first 2 Gbyte partition is formatted as the primary partition and the rest of the capacity as the extended partition.
- the extended partition is further divided into more partitions, each with a maximum size of 2 Gbyte, if the overall extended partition capacity is still greater than 2 Gbyte.
- the method is shown to include the step of generating a logical block addressing (LBA) address and an operating mode indicator for a host device without multiple partition support.
- the method includes the step of accessing a data storage component having a plurality of partitions using the host device without multiple partition support as a function of the generated LBA address and operating mode.
- the operating mode can be a partition number or a designator indicative of a partition number.
- the step of generating the LBA address and the operating mode indicator for the host device can include generating the LBA address and the operating mode for a host device having a FAT16 file system.
- the step of accessing the data storage unit as a function of the generated LBA address and the operating mode further includes selecting one of the plurality of partitions based upon the operating mode, and accessing the selected one of the plurality of partitions using the generated LBA address.
- the step of accessing the data storage unit as a function of the generated LBA address and the operating mode further includes translating the generated LBA address and the operating mode into a native LBA address for the data storage component, and accessing the selected one of the plurality of partitions using the native LBA address.
Abstract
Description
- The present invention relates generally to data storage. More particularly, the invention relates to methods and apparatus which allow host devices without multiple partition support to utilize the full storage capacity of multiple partition data storage systems.
- Systems using a file allocation table (FAT) which employs 16 bits for addressing clusters of data are known as “FAT16 file systems”. A FAT16 file system is limited to 2 Gbytes per partition. Storage devices with a capacity of more than 2 Gbytes, and with which a FAT16 file system is used, therefore tend to have multiple partitions, each with no more than 2 Gbytes of capacity.
- The 2 Gbyte barrier of the FAT16 file system partition limit is imposed by the maximum number of clusters and the largest cluster size supported by the FAT16 file system. The FAT16 file system is limited to 65,525 clusters. The size of a cluster must be a power of 2, and be less than 65,536 bytes. This results in a maximum cluster size of 32,768 bytes (32 Kbytes). Multiplying the maximum number of clusters (65,525) by the maximum cluster size (32,768) equals 2 Gbytes.
- In storage systems using multiple partitions, the first partition is typically referred to as the “primary partition.” Everything not stored in the primary partition is stored in an “extended partition.” A utility program, for example the “Fdisk” utility program, is used to create, delete or modify partitions on a storage system. The Fdisk utility program is a DOS utility used to configure and partition storage systems to prepare them for DOS use. The Fdisk utility software creates only one primary DOS partition (commonly referred to as “PRI DOS”) on a physical disc of a disc drive data storage system. Other utility programs can also be used to create, delete or modify partitions.
- Consequently, digital cameras and other host devices must use a “FAT32” file system (i.e., a file allocation table which employs 32 bits for addressing clusters of data) in order to allow reading and writing of data above the 2 Gbyte limit on an associated data storage system or device. When a host device does not support multiple partitions for FAT16, it can only access the primary partition of its associated storage device. This in turn wastes the capacity of the storage device beyond the 2 Gbyte limit.
- Embodiments of the present invention provide solutions to these and/or other problems, and offer other advantages over the prior art.
- An apparatus of the present invention includes partition selection circuitry configured to selectably provide individual access to multiple ones of a plurality of partitions of a data storage component by a host device without multiple partition support. The apparatus can also include the data storage component and/or the host device. The partition selection circuitry uses a logical block addressing (LBA) address generated by the host device, and an operating mode indicator indicative of a particular partition, to allow the partitions of the data storage component to be accessed by the host device without multiple partition support. Methods implemented by the apparatus are also disclosed.
- Other features and benefits that characterize embodiments of the present invention will be apparent upon reading the following detailed description and review of the associated drawings.
-
FIG. 1 is an isometric view of a disc drive type data storage system. -
FIGS. 2 and 3 are block diagrams illustrating systems, apparatus and components in which the present invention can be embodied. -
FIG. 3-1 is a diagrammatic illustration of a first method embodiment of the present invention, in conjunction with components of a system of the present invention. -
FIG. 3-2 is a mapping table which maps combinations of LBA addresses and partition or mode numbers to a storage component's native LBA addresses. -
FIG. 4-1 is a diagrammatic illustration of a second method embodiment of the present invention, in conjunction with components of a system of the present invention. -
FIG. 4-2 is a translation table which demonstrates how the translation engine shown inFIG. 4-1 translates LBA addresses and partition numbers into native LBA addresses. -
FIG. 5 is a flow diagram illustrating a general method of the present invention. -
FIG. 1 is an isometric view of adisc drive 100 with which embodiments of the present invention are useful.Disc drive 100 represent a data storage device or component which can be partitioned and accessed by a host device.Disc drive 100 includes a housing with abase 102 and a top cover (not shown).Disc drive 100 further includes adisc pack 106, which is mounted on a spindle motor (not shown) by adisc clamp 108.Disc pack 106 includes a plurality of individual discs, which are mounted for co-rotation aboutcentral axis 109. Each disc surface has an associateddisc head slider 110 which is mounted todisc drive 100 for communication with the disc surface. In the example shown inFIG. 1 ,sliders 110 are supported bysuspensions 112 which are in turn attached to track accessingarms 114 of anactuator 116. The actuator shown inFIG. 1 is of the type known as a rotary moving coil actuator and includes a voice coil motor (VCM), shown generally at 118.Voice coil motor 118 rotatesactuator 116 with its attachedheads 110 about apivot shaft 120 to positionheads 110 over a desired data track along anarcuate path 122 between a discinner diameter 124 and a discouter diameter 126.Voice coil motor 118 is driven by servoelectronics 130 based on signals generated byheads 110 and a host computer (not shown). - While a particular disc drive is shown,
disc drive 100 is intended to represent any of a variety of data storage devices or components in which, or with which, the methods and apparatus of the present invention can be implemented. For example, in other embodiments,disc drive 100 can be other types of magnetic disc drives, or can be other types of non-magnetic disc drives such as an optical disc drive, a magneto-optical disc drive, etc. - Referring now to
FIGS. 2-1 and 2-2, shown are alternative embodiments of systems in accordance with some embodiments of the present invention. InFIG. 2-1 ,system 250 includes ahost device 210 and a data storage device orcomponent 200. In an example embodiment,host device 210 represents any type of host device with a legacy FAT16 file systems (i.e., without multiple partition support). However, the present invention is not limited to host devices with FAT16 file systems, but instead is extendible, for example for use with any host device without multiple partition support.Data storage component 200 is a data storage system or device, such asdisc drive 100, having a data storage capacity in excess of the maximum partition size with which the host device is configured to work. In the example of a host device with a legacy FAT16 file system,data storage component 200 has a capacity in excess of the 2 Gbyte per partition limit described above. As will be described below in greater detail,data storage component 200 is configured to provide multiple partitions. -
Partition selection circuitry 220 ofsystem 250 can include hardware and/or software switches or other components or modules which are used to selectably provide tohost device 210 individual access to multiple ones of the partitions ofdata storage component 200.Partition selection circuitry 220, and related methods of the present invention, are described below particularly with reference toFIGS. 3-1 , 3-2, 4-1, 4-2 and 5. - In various embodiments,
partition selection circuitry 220 can be implemented independently, with the host device, or with the data storage component. For example, inFIG. 2-1 , dashed lines surroundinghost device 210 andpartition selection circuitry 220 represent that these components can be combined into a single system orapparatus 230. In contrast, inFIG. 2-2 , dashed lines surroundingdata storage component 200 andpartition selection circuitry 220 represent that these components can be combined into a single system orapparatus 240 of alarger system 260. - The present invention includes methods, and corresponding apparatus, which allow host devices with legacy FAT16 file systems (i.e., without multiple partition support) to utilize the full storage capacity of a disc drive or other data storage device. These methods can be implemented, for example, in the various components and apparatus illustrated in
FIGS. 2-1 and 2-2. In exemplary embodiments of these methods, the capacity of the data storage device is divided into multiple partitions, each of which cannot exceed 2 Gbytes in size. Partition selection circuitry, for example in the form of software and/or hardware switches, allows a user of the host device and data storage device to switch between the different partitions. Software switches can be embodied in suitably programmed processing circuitry. Hardware switches can be jumpers (i.e., jumper settings) or dipswitches which can be manipulated by the user to set the mode of operation in the manner described below. Other types of hardware switches can be used as well. Hardware switches provide the advantage, relative to software switches, of not requiring the data storage device to be programmed before switching between different partitions. Software switches provide the advantage, relative to hardware switches, of not requiring extra hardware. Further, in one particular example embodiment, the number of jumpers/dipswitches used limits the number of partitions which can be supported. This is not true for software switches. - Using the methods and apparatus of the present invention, to access the partitions of the data storage device, the host device (and/or the user) must provide both the logical block addressing (LBA) address and an operating mode indicator (for example through switches) which represents the partition number to be accessed. If the operating mode indicator or partition number is not specified, then a default partition is assumed. Two embodiments of the methods and apparatus of the present invention are described below with reference to
FIGS. 3-1 and 4-1, with the two embodiments differing in the manner that the partitions are addressed and formatted. - Referring now to
FIG. 3-1 , a first method embodiment is diagrammatically illustrated in conjunction with corresponding components of a host device, partition selection circuitry, and a data storage component. Using this first method embodiment, the disc drive or other data storage component treats each partition as an independent storage unit. All partitions share the same partition LBA address space (as opposed to the “native” LBA address space of the storage component), as is illustrated inFIG. 3-1 . In the illustrated example, assume that storage component ordevice 200 with a capacity of 5 Gbytes is used. It is divided into three partitions which are less than the 2 Gbyte limit, partition 1 (reference number 302), partition 2 (reference number 304) and partition 3 (reference number 306). A fourth partition, partition 0 (reference number 308), includes the entire 5 Gbytes of the data storage component. - The partition LBA address space of the smaller partitions is 0 to 0x3FFAC4 (partition 1), 0 to 0x3FFAC4 (partition 2), and 0 to 0x201CC6 (partition 3), respectively, as is shown in
FIG. 3-1 . Table 1 shown inFIG. 3-2 is a mapping table which maps combinations of host generated LBA addresses (for a FAT16 system) and partition or mode numbers to the storage component's native LBA addresses. Ifhost device 210 has a legacy FAT16 file system, the host generated LBA address can range from 0-3F,FAC4. If the host device has a different FAT files system (for example a FAT32 file system), the host generated LBA address can have a different range (for example the illustrated 0-A0,1250). All threepartitions 302/304/306 are formatted as the primary partition, as at any one time there is only one single partition accessible when switching between the three. The LBA address space for the single larger partition (partition 0), encompassing the three smaller partitions, is in this particular example 0 to A0,1250. - A software/
hardware switch 310 allows the user/host device to switch between thedifferent partitions 302/304/306 of the data storage component. This limits drive capacity to 5, 2, 2 and 1 Gbyte when switching betweenpartitions 0 through 3, respectively. The software/hardware switch 310 forms at least a portion ofpartition selection circuitry 220 shown inFIGS. 2-1 and 2-2. Before thehost device 210 accesses the data storage component, it (or the user) must program or switch the partition number. Otherwise,partition 0, the full capacity of the data storage component fromLBA 0 to 0xA0,1250 will always be assumed. Thereafter, the host device provides the LBA address and this same LBA address will be used to access the data sector with the specific (or default) partition. - In some embodiments, the LBA address is provided by address generating circuitry, modules or
components 320 ofhost device 210. Similarly, the mode or partition number can be provided by partition designating circuitry, modules orcomponents 325 ofhost device 210. In other embodiments, the partition number is provided to thestorage component 200 by the user throughswitches 310, for example in the form of jumper settings. In any event, switches 310 use the partition number to determine which partition ofcomponent 200 that the provided LBA address corresponds to. As mentioned above, whilecircuitry 320 shown inFIG. 3-1 is illustrated as generating an LBA address of between 0 and A0,1250 (i.e., for a FAT32 system), for a FAT16 system the LBA addresses generated by the host device will be between 0 and 3F,FAC4. - Referring now to
FIG. 4-1 , a second method embodiment is diagrammatically illustrated in conjunction with corresponding components of a host device, partition selection circuitry, and a data storage component. In this example, thedata storage component 200 again has a capacity of 5 Gbytes. Using this method embodiment, thedata storage component 200 is still divided into three partitions which are each less than the 2 Gbyte limit, but with each partition having different partition LBA address spaces, and the address spaces from one partition to the next being continuous. InFIG. 4-1 , the three partitions are illustrated as partition 1 (reference number 402), partition 2 (reference number 404) and partition 3 (reference number 406). Overall, the three partitions span an address space from 0 to 0xA01250. The address spaces of these three partitions are illustrated inFIG. 4-1 . - In this embodiment, instead of switches being used, an
address translation engine 410 accepts the host device generated LBA address and partition number (for example through switches) from host device 210 (and/or from the user in the case of the partition number in some embodiments), and converts them into a drive native LBA address. The translation engine forms, in some embodiments, at least a portion ofpartition selection circuitry 220 shown inFIGS. 2-1 and 2-2. In exemplary embodiments,translation engine 410 is integrated or included withdata storage component 200. However, in other embodiments,translation engine 410 is separate from the data storage component. In the illustrated example, the first 2Gbyte partition 402 is formatted as the primary partition, and the other partitions (i.e., 404 and 406) are formatted as extended partitions with individual logic volume. Other drive configurations can also be used, such as formatting the 5 Gbyte storage component into five partitions with 1 Gbyte size each. - Table 2 shown in
FIG. 4-2 is a translation table which demonstrates how thetranslation engine 410 translates host generated LBA addresses, and partition numbers, into native LBA addresses. Again, if the partition number is not specified, the default mode 0 (partition 0 represented at 408) corresponding to the entire 5 Gbytes of thedata storage component 200 is assumed bytranslation engine 410. When a partition other thanpartition 0 is specified,translation engine 410 translates the host generated LBA address and partition number into a native LBA address to allow access by thehost device 210 to the corresponding partition or partition extension. For example, when mode 2 (partition 2 represented at 404) is chosen, the first partition of the extended partition ofdata storage component 200 is accessible byhost device 210. All LBA addresses generated by the host device are therefore offset byaddress translation engine 410 by the size of the first orprimary partition 402, which in this example is 0x3FFAC5. This can be computed using the first partition table information available in the primary Master Boot Record (MBR). The capacity of the storage device will be capped by the size of the currently selected partition, which can be found in the first partition table information in the extended MBR (at 0x3FFAC5). This avoids reading/writing beyond the partition capacity. - The two method embodiments described above with reference to
FIGS. 3-1 , 3-2, 4-1 and 4-2 provide little difference for host devices, such as digital cameras or other electronic devices, which use FAT16 file systems without multiple partition support. Using either method embodiment, and the corresponding apparatus described above, the data storage component will appear to the host to be a single 2 Gbyte (maximum) storage device. - Using the first method and apparatus embodiments (e.g.,
FIG. 3-1 ), all partitions are formatted as the primary partition. One issue which arises using this method is that once the storage is reset to the default configuration (mode orpartition 0 in this example), only the default partition is accessible, even for host devices which support multiple partitions. Examples of host devices which are likely to have multiple partition support include personal digital (or data) assistants (PDAs) and personal computers (PCs). Thus, the first method embodiment can result in certain inconveniences in some practical applications. For example, consider the case of the data storage component being used with a digital camera (or other host device) without multiple partition support, with the second 2 Gbyte partition (partition 2) being selected. Assume further that once reading/writing is completed, the data storage component is reset to the default configuration and plugged into a PDA, a PC or other host device for further processing. Since the data is stored in the second partition, but the other host device sees only the default partition, extra steps may be necessary to retrieve the data. - Using the second method and apparatus embodiments (e.g.,
FIG. 4-1 ), it is possible to provide hosts with multiple partition support for FAT16 file systems, such that they can access all partitions as individual logical devices. To this end, the drive is formatted into two main partitions. The first 2 Gbyte partition is formatted as the primary partition and the rest of the capacity as the extended partition. The extended partition is further divided into more partitions, each with a maximum size of 2 Gbyte, if the overall extended partition capacity is still greater than 2 Gbyte. This method allows the full capacity of the storage device to be used in a single partition environment, and yet allows it to be used in a multiple partition support device as well. With this method, the above-described inconvenience related to retrieving data can be overcome. - Referring now to
FIG. 5 , shown is a flow diagram illustrating a general method in accordance with the present invention as described above. Atblock 505, the method is shown to include the step of generating a logical block addressing (LBA) address and an operating mode indicator for a host device without multiple partition support. Then, atblock 510, the method includes the step of accessing a data storage component having a plurality of partitions using the host device without multiple partition support as a function of the generated LBA address and operating mode. The operating mode can be a partition number or a designator indicative of a partition number. In the method, the step of generating the LBA address and the operating mode indicator for the host device can include generating the LBA address and the operating mode for a host device having a FAT16 file system. - In one embodiment, the step of accessing the data storage unit as a function of the generated LBA address and the operating mode further includes selecting one of the plurality of partitions based upon the operating mode, and accessing the selected one of the plurality of partitions using the generated LBA address. In another embodiment, the step of accessing the data storage unit as a function of the generated LBA address and the operating mode further includes translating the generated LBA address and the operating mode into a native LBA address for the data storage component, and accessing the selected one of the plurality of partitions using the native LBA address.
- It is to be understood that even though numerous characteristics and advantages of various embodiments of the invention have been set forth in the foregoing description, together with details of the structure and function of various embodiments of the invention, this disclosure is illustrative only, and changes may be made in detail, especially in matters of structure and arrangement of parts within the principles of the present invention to the full extent indicated by the broad general meaning of the terms in which the appended claims are expressed. For example, the particular elements may vary depending on the particular application for the storage components, while maintaining substantially the same functionality without departing from the scope and spirit of the present invention. In addition, although embodiments described herein are directed toward use in, or with, a disc drive data storage system, it will be appreciated by those skilled in the art that the teachings of the present invention can be applied to other data storages systems and components without departing from the scope and spirit of the present invention.
Claims (21)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/973,485 US20060090058A1 (en) | 2004-10-26 | 2004-10-26 | Method and data storage system for providing multiple partition support |
US13/538,479 US8607021B2 (en) | 2004-10-26 | 2012-06-29 | Method and data storage system for providing multiple partition support |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/973,485 US20060090058A1 (en) | 2004-10-26 | 2004-10-26 | Method and data storage system for providing multiple partition support |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/538,479 Continuation US8607021B2 (en) | 2004-10-26 | 2012-06-29 | Method and data storage system for providing multiple partition support |
Publications (1)
Publication Number | Publication Date |
---|---|
US20060090058A1 true US20060090058A1 (en) | 2006-04-27 |
Family
ID=36207352
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/973,485 Abandoned US20060090058A1 (en) | 2004-10-26 | 2004-10-26 | Method and data storage system for providing multiple partition support |
US13/538,479 Active US8607021B2 (en) | 2004-10-26 | 2012-06-29 | Method and data storage system for providing multiple partition support |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/538,479 Active US8607021B2 (en) | 2004-10-26 | 2012-06-29 | Method and data storage system for providing multiple partition support |
Country Status (1)
Country | Link |
---|---|
US (2) | US20060090058A1 (en) |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090037941A1 (en) * | 2007-08-02 | 2009-02-05 | International Business Machines Corporation | Multiple partition adjunct instances interfacing multiple logical partitions to a self-virtualizing input/output device |
US20120210044A1 (en) * | 2007-08-02 | 2012-08-16 | International Business Machines Corporation | Partition adjunct for data processing system |
US20130275661A1 (en) * | 2011-09-30 | 2013-10-17 | Vincent J. Zimmer | Platform storage hierarchy with non-volatile random access memory with configurable partitions |
US8819203B1 (en) * | 2007-09-28 | 2014-08-26 | Emc Corporation | Techniques for providing an application service to an application from an appliance-style application services platform |
US20220058080A1 (en) * | 2020-08-18 | 2022-02-24 | Changxin Memory Technologies, Inc. | Method and device for determining fail bit repair scheme |
US11791010B2 (en) | 2020-08-18 | 2023-10-17 | Changxin Memory Technologies, Inc. | Method and device for fail bit repairing |
US11791012B2 (en) | 2021-03-31 | 2023-10-17 | Changxin Memory Technologies, Inc. | Standby circuit dispatch method, apparatus, device and medium |
US11853152B2 (en) | 2020-08-18 | 2023-12-26 | Changxin Memory Technologies, Inc. | Fail bit repair method and device |
US11881278B2 (en) | 2021-03-31 | 2024-01-23 | Changxin Memory Technologies, Inc. | Redundant circuit assigning method and device, apparatus and medium |
US11887685B2 (en) | 2020-08-18 | 2024-01-30 | Changxin Memory Technologies, Inc. | Fail Bit repair method and device |
Citations (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6041395A (en) * | 1997-12-03 | 2000-03-21 | Dell Usa, L.P. | System and method for changing partition mappings to logical drives in a computer memory |
US6185666B1 (en) * | 1999-09-11 | 2001-02-06 | Powerquest Corporation | Merging computer partitions |
US6233105B1 (en) * | 1999-03-29 | 2001-05-15 | Inventec Corporation | Method of disk formatting |
US6247128B1 (en) * | 1997-07-22 | 2001-06-12 | Compaq Computer Corporation | Computer manufacturing with smart configuration methods |
US6298427B1 (en) * | 1999-01-26 | 2001-10-02 | Dell Usa, L.P. | Method and apparatus for mapping hard disk partitions and block devices to logical drives in a computer system |
US6330653B1 (en) * | 1998-05-01 | 2001-12-11 | Powerquest Corporation | Manipulation of virtual and live computer storage device partitions |
US6383615B2 (en) * | 1999-06-18 | 2002-05-07 | The Procter & Gamble Company | Absorbent sheet material having cut-resistant layer and method for making the same |
US6453383B1 (en) * | 1999-03-15 | 2002-09-17 | Powerquest Corporation | Manipulation of computer volume segments |
US20020157027A1 (en) * | 2001-04-24 | 2002-10-24 | International Business Machines Corporation | Method and system for providing a trusted boot source in a partition |
US20030065866A1 (en) * | 2001-10-01 | 2003-04-03 | Spencer Andrew M. | Memory controller for memory card manages file allocation table |
US20040044871A1 (en) * | 2002-08-29 | 2004-03-04 | Weber Bret S. | Method and apparatus for mapping storage partitions of storage elements to host systems |
US20040088692A1 (en) * | 2002-10-30 | 2004-05-06 | Robert Stutton | Virtual partition |
US20050027978A1 (en) * | 2003-08-01 | 2005-02-03 | Hewlett-Packard Development Company, L.P. | Data processing system and method |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6195650B1 (en) | 2000-02-02 | 2001-02-27 | Hewlett-Packard Company | Method and apparatus for virtualizing file access operations and other I/O operations |
-
2004
- 2004-10-26 US US10/973,485 patent/US20060090058A1/en not_active Abandoned
-
2012
- 2012-06-29 US US13/538,479 patent/US8607021B2/en active Active
Patent Citations (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6247128B1 (en) * | 1997-07-22 | 2001-06-12 | Compaq Computer Corporation | Computer manufacturing with smart configuration methods |
US6041395A (en) * | 1997-12-03 | 2000-03-21 | Dell Usa, L.P. | System and method for changing partition mappings to logical drives in a computer memory |
US6330653B1 (en) * | 1998-05-01 | 2001-12-11 | Powerquest Corporation | Manipulation of virtual and live computer storage device partitions |
US6298427B1 (en) * | 1999-01-26 | 2001-10-02 | Dell Usa, L.P. | Method and apparatus for mapping hard disk partitions and block devices to logical drives in a computer system |
US6453383B1 (en) * | 1999-03-15 | 2002-09-17 | Powerquest Corporation | Manipulation of computer volume segments |
US6233105B1 (en) * | 1999-03-29 | 2001-05-15 | Inventec Corporation | Method of disk formatting |
US6383615B2 (en) * | 1999-06-18 | 2002-05-07 | The Procter & Gamble Company | Absorbent sheet material having cut-resistant layer and method for making the same |
US6185666B1 (en) * | 1999-09-11 | 2001-02-06 | Powerquest Corporation | Merging computer partitions |
US20020157027A1 (en) * | 2001-04-24 | 2002-10-24 | International Business Machines Corporation | Method and system for providing a trusted boot source in a partition |
US20030065866A1 (en) * | 2001-10-01 | 2003-04-03 | Spencer Andrew M. | Memory controller for memory card manages file allocation table |
US20040044871A1 (en) * | 2002-08-29 | 2004-03-04 | Weber Bret S. | Method and apparatus for mapping storage partitions of storage elements to host systems |
US20040088692A1 (en) * | 2002-10-30 | 2004-05-06 | Robert Stutton | Virtual partition |
US20050027978A1 (en) * | 2003-08-01 | 2005-02-03 | Hewlett-Packard Development Company, L.P. | Data processing system and method |
Cited By (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9317453B2 (en) | 2007-08-02 | 2016-04-19 | International Business Machines Corporation | Client partition scheduling and prioritization of service partition work |
US20120210044A1 (en) * | 2007-08-02 | 2012-08-16 | International Business Machines Corporation | Partition adjunct for data processing system |
US8495632B2 (en) * | 2007-08-02 | 2013-07-23 | International Business Machines Corporation | Partition adjunct for data processing system |
US20090037941A1 (en) * | 2007-08-02 | 2009-02-05 | International Business Machines Corporation | Multiple partition adjunct instances interfacing multiple logical partitions to a self-virtualizing input/output device |
US8645974B2 (en) | 2007-08-02 | 2014-02-04 | International Business Machines Corporation | Multiple partition adjunct instances interfacing multiple logical partitions to a self-virtualizing input/output device |
US8819203B1 (en) * | 2007-09-28 | 2014-08-26 | Emc Corporation | Techniques for providing an application service to an application from an appliance-style application services platform |
US20130275661A1 (en) * | 2011-09-30 | 2013-10-17 | Vincent J. Zimmer | Platform storage hierarchy with non-volatile random access memory with configurable partitions |
EP2761468B1 (en) * | 2011-09-30 | 2019-12-11 | Intel Corporation | Platform storage hierarchy with non-volatile random access memory having configurable partitions |
US20220058080A1 (en) * | 2020-08-18 | 2022-02-24 | Changxin Memory Technologies, Inc. | Method and device for determining fail bit repair scheme |
US11791010B2 (en) | 2020-08-18 | 2023-10-17 | Changxin Memory Technologies, Inc. | Method and device for fail bit repairing |
US11797371B2 (en) * | 2020-08-18 | 2023-10-24 | Changxin Memory Technologies, Inc. | Method and device for determining fail bit repair scheme |
US11853152B2 (en) | 2020-08-18 | 2023-12-26 | Changxin Memory Technologies, Inc. | Fail bit repair method and device |
US11887685B2 (en) | 2020-08-18 | 2024-01-30 | Changxin Memory Technologies, Inc. | Fail Bit repair method and device |
US11791012B2 (en) | 2021-03-31 | 2023-10-17 | Changxin Memory Technologies, Inc. | Standby circuit dispatch method, apparatus, device and medium |
US11881278B2 (en) | 2021-03-31 | 2024-01-23 | Changxin Memory Technologies, Inc. | Redundant circuit assigning method and device, apparatus and medium |
Also Published As
Publication number | Publication date |
---|---|
US20120271994A1 (en) | 2012-10-25 |
US8607021B2 (en) | 2013-12-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8607021B2 (en) | Method and data storage system for providing multiple partition support | |
US6848034B2 (en) | Dense server environment that shares an IDE drive | |
US10769059B2 (en) | Apparatus and system for object-based storage solid-state device | |
US8402152B2 (en) | Apparatus and system for object-based storage solid-state drive | |
US6938123B2 (en) | System and method for raid striping | |
US20080229046A1 (en) | Unified support for solid state storage | |
JP4283288B2 (en) | Method and apparatus for optimizing OSD deterministic object fragmentation in a disk drive | |
US7987328B2 (en) | Data archive system | |
US8244975B2 (en) | Command queue ordering by flipping active write zones | |
US6502178B1 (en) | Method, system, and program for mapping logical addresses to high performance zones on a storage medium | |
US20080005458A1 (en) | Command queue ordering with directional and floating write bands | |
US8014095B2 (en) | Mixed format disk drive | |
US6026463A (en) | Method for improving data transfer rates for user data stored on a disk storage device | |
US20220164145A1 (en) | Apparatus and system for object-based storage solid-state device | |
US20090006804A1 (en) | Bi-level map structure for sparse allocation of virtual storage | |
US6202118B1 (en) | Apparatus for address translation to selectively improve data transfer rates on a disk storage device | |
IE20160095A1 (en) | Realm partitioning in hard drives | |
US20030028719A1 (en) | Disc drives divided into multiple logical containers | |
US7185020B2 (en) | Generating one or more block addresses based on an identifier of a hierarchical data structure | |
JP2009015840A (en) | Data structure for highly efficient data query | |
US20090164719A1 (en) | Storage performance improvement using data replication on a disk | |
US20080172387A1 (en) | Speeding up traversal of a file system tree | |
WO2007097716A1 (en) | Method and apparatus for removable, ide-ata or scsi flash memory based data storage in a portable computer device |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SEAGATE TECHNOLOGY LLC, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CHNG, YONGPENG;TAN, LIANYONG;THAM, YAMPHENG;AND OTHERS;REEL/FRAME:015939/0481 Effective date: 20041018 |
|
AS | Assignment |
Owner name: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT Free format text: SECURITY AGREEMENT;ASSIGNORS:MAXTOR CORPORATION;SEAGATE TECHNOLOGY LLC;SEAGATE TECHNOLOGY INTERNATIONAL;REEL/FRAME:022757/0017 Effective date: 20090507 Owner name: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATE Free format text: SECURITY AGREEMENT;ASSIGNORS:MAXTOR CORPORATION;SEAGATE TECHNOLOGY LLC;SEAGATE TECHNOLOGY INTERNATIONAL;REEL/FRAME:022757/0017 Effective date: 20090507 |
|
AS | Assignment |
Owner name: SEAGATE TECHNOLOGY LLC, CALIFORNIA Free format text: RELEASE;ASSIGNOR:JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:025662/0001 Effective date: 20110114 Owner name: SEAGATE TECHNOLOGY INTERNATIONAL, CALIFORNIA Free format text: RELEASE;ASSIGNOR:JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:025662/0001 Effective date: 20110114 Owner name: SEAGATE TECHNOLOGY HDD HOLDINGS, CALIFORNIA Free format text: RELEASE;ASSIGNOR:JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:025662/0001 Effective date: 20110114 Owner name: MAXTOR CORPORATION, CALIFORNIA Free format text: RELEASE;ASSIGNOR:JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:025662/0001 Effective date: 20110114 |
|
AS | Assignment |
Owner name: THE BANK OF NOVA SCOTIA, AS ADMINISTRATIVE AGENT, Free format text: SECURITY AGREEMENT;ASSIGNOR:SEAGATE TECHNOLOGY LLC;REEL/FRAME:026010/0350 Effective date: 20110118 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO PAY ISSUE FEE |
|
AS | Assignment |
Owner name: SEAGATE TECHNOLOGY INTERNATIONAL, CAYMAN ISLANDS Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATERAL AGENT AND SECOND PRIORITY REPRESENTATIVE;REEL/FRAME:030833/0001 Effective date: 20130312 Owner name: SEAGATE TECHNOLOGY LLC, CALIFORNIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATERAL AGENT AND SECOND PRIORITY REPRESENTATIVE;REEL/FRAME:030833/0001 Effective date: 20130312 Owner name: EVAULT INC. (F/K/A I365 INC.), CALIFORNIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATERAL AGENT AND SECOND PRIORITY REPRESENTATIVE;REEL/FRAME:030833/0001 Effective date: 20130312 Owner name: SEAGATE TECHNOLOGY US HOLDINGS, INC., CALIFORNIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATERAL AGENT AND SECOND PRIORITY REPRESENTATIVE;REEL/FRAME:030833/0001 Effective date: 20130312 |