Jump to content

Non-RAID drive architectures

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Omegatron (talk | contribs) at 16:46, 1 February 2021 ("mulip" → "multiple"). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

The most widespread standard for configuring multiple hard disk drives is RAID (Redundant Array of Inexpensive/Independent Disks), which comes in a number of standard configurations and non-standard configurations. Non-RAID drive architectures also exist, and are referred to by acronyms with similarity to RAID, several tongue-in-cheek

  • JBOD (derived from "just a bunch of disks"): described multiple hard disk drives operated as individual independent hard disk drives.
  • SPAN or BIG: A method of combining the free space on multiple hard disk drives from "JBoD" to create a spanned volume. Such a concatenation is sometimes also called BIG/SPAN. A SPAN or BIG is generally a spanned volume only, as it often contains mismatched types and sizes of hard disk drives.[1]
  • MAID (derived from "massive array of idle drives"): an architecture using hundreds to thousands of hard disk drives for providing nearline storage of data, primarily designed for "Write Once, Read Occasionally" (WORO) applications, in which increased storage density and decreased cost are traded for increased latency and decreased redundancy.

JBOD

JBOD (abbreviated from "Just a Bunch Of Disks"/"Just a Bunch Of Drives") is an architecture using multiple hard drives exposed as individual devices. Hard drives may be treated independently or may be combined into one or more logical volumes using a volume manager like LVM or mdadm, or a device-spanning filesystem like btrfs; such volumes are usually called "spanned" or "linear | SPAN | BIG".[2][3][4] A spanned volume provides no redundancy, so failure of a single hard drive amounts to failure of the whole logical volume.[5][6] Redundancy for resilience and/or bandwidth improvement may be provided, in software, at a higher level.

Concatenation (SPAN, BIG)

Diagram of a SPAN/BIG ("JBOD") setup.

Concatenation or spanning of drives is not one of the numbered RAID levels, but it is a popular method for combining multiple physical disk drives into a single logical disk. It provides no data redundancy. Drives are merely concatenated together, end to beginning, so they appear to be a single large disk. It may be referred to as SPAN or BIG (meaning just the words "span" or "big", not as acronyms).[citation needed]

In the adjacent diagram, data are concatenated from the end of disk 0 (block A63) to the beginning of disk 1 (block A64); end of disk 1 (block A91) to the beginning of disk 2 (block A92). If RAID 0 were used, then disk 0 and disk 2 would be truncated to 28 blocks, the size of the smallest disk in the array (disk 1) for a total size of 84 blocks.[citation needed]

What makes a SPAN or BIG different from RAID configurations is the possibility for the selection of drives. While RAID usually requires all drives to be of similar capacity[a] and it is preferred that the same or similar drive models are used for performance reasons, a spanned volume does not have such requirements.[1][7]

Implementations

The initial release of Microsoft's Windows Home Server employs drive extender technology, whereby an array of independent drives are combined by the OS to form a single pool of available storage. This storage is presented to the user as a single set of network shares. Drive extender technology expands on the normal features of concatenation by providing data redundancy through software – a shared folder can be marked for duplication, which signals to the OS that a copy of the data should be kept on multiple physical drives, whilst the user will only ever see a single instance of their data.[8] This feature was removed from Windows Home Server in its subsequent major release.[9]

The btrfs filesystem can span multiple devices of different sizes, including RAID 0/1/10 configurations, storing 1 to 4 redundant copies of both data and metadata.[10] (A flawed RAID 5/6 also exists, but can result in data loss.)[10] For RAID 1, the devices must have complementary sizes. For example, a filesystem spanning two 500 GB devices and one 1 TB device could provide RAID1 for all data, while a filesystem spanning a 1 TB device and a single 500 GB device could only provide RAID1 for 500 GB of data.

The ZFS filesystem can likewise pool multiple devices of different sizes and implement RAID, though it is less flexible, requiring the creation of virtual devices of fixed size on each device before pooling.[11]

MAID

MAID (abbreviated from "massive array of idle drives") is an architecture using hundreds to thousands of hard drives for providing nearline storage of data. MAID is designed for "Write Once, Read Occasionally" (WORO) applications.[12][13][14]

Compared to RAID technology, MAID has increased storage density, and decreased cost, electrical power, and cooling requirements. However, these advantages are at the cost of much increased latency, significantly lower throughput, and decreased redundancy. Drives designed for multiple spin-up/down cycles (e.g. laptop drives) are significantly more expensive.[15] Latency may be as high as tens of seconds.[16] MAID can supplement or replace tape libraries in hierarchical storage management.[13]

To allow a more gradual tradeoff between access time and power savings, some MAIDs such as Nexsan's AutoMAID incorporate drives capable of spinning down to a lower speed.[17] Large scale disk storage systems based on MAID architectures allow dense packaging of drives and are designed to have only 25% of disks spinning at any one time.[16]

See also

Notes

  1. ^ Otherwise, in most cases only the drive portions equaling to the size of the smallest RAID set member would be used.

References

  1. ^ a b "Explanation of Spanned Volumes".
  2. ^ Rouse, Margaret (September 2005). "JBOD (just a bunch of disks or just a bunch of drives)". SearchStorage.TechTarget.com. TechTarget. Retrieved 2013-10-31.
  3. ^ Manage spanned volumes
  4. ^ Using spanned volumes
  5. ^ "LVM HOWTO, Section 3.7. mapping modes (linear/striped)". TLDP.org. Retrieved 2013-12-31.
  6. ^ "Linux RAID setup". Kernel.org. Linux Kernel Organization. 2013-10-05. Retrieved 2013-12-31.
  7. ^ "RAID Requirements".
  8. ^ "Windows Home Server Drive Extender Technical Brief". Microsoft.com. Retrieved 2009-03-12.
  9. ^ "Windows Home Server code name "Vail"– Update".
  10. ^ a b "Using Btrfs with Multiple Devices - btrfs Wiki". btrfs.wiki.kernel.org. Retrieved 2021-01-19.
  11. ^ "Five Years of Btrfs | MarkMcB". markmcb.com. Retrieved 2021-01-19.
  12. ^ "MAID (massive array of idle disks)". TechTarget.com. January 2009. Retrieved 2013-12-31.
  13. ^ a b Dennis Colarelli; Dirk Grunwald (2002-07-26). "Massive Arrays of Idle Disks For Storage Archives" (PDF). University of Colorado. Retrieved 2013-12-31.
  14. ^ "What does WORO stand for?". TheFreeDictionary.com. Retrieved 2013-12-31.
  15. ^ SGI (2012). "Enterprise MAID Quick Reference Guide" (PDF). Archived from the original (PDF) on 2014-07-14. Retrieved 12 July 2014.
  16. ^ a b Cook, Rick (2004-07-12). "Backup budgets have it MAID with cheap disk" Retrieved on 2008-07-15
  17. ^ "AutoMAID Energy Saving Technology". 2011. Archived from the original on 2014-09-19. Retrieved 7 April 2011.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Non-RAID_drive_architectures&oldid=1004224984"