EMC CX500I Configuration Guide - Page 36
Second Disk, Third Disk, Fourth Disk, Stripe, Element, User Data, Parity Data, Data Block, Bytes - cx500 flare
View all EMC CX500I manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 36 highlights
RAID Types and Trade-offs Figure 2-3 shows user and parity data with a data block size of 2 Kbytes in a RAID 3 Group. Notice that the byte addresses proceed from the first disk to the second, third, and fourth, then the first, and so on. Stripe Element Size Data Block Bytes First Disk 0-511 2048-2559 4096-4607 6144-6655 8192-8603 ... Second Disk 512-1023 2560-3071 4608-5119 6656-7167 8604-9115 ... Stripe Size Third Disk 1024-1535 3072-3583 5120-5631 7168-7679 9116-9627 ... Fourth Disk 1536-2047 3584-4095 5632-6143 7680-8191 9628-10139 ... Parity Parity Fifth Disk Parity Parity Parity ... User Data Parity Data EMC1816 Figure 2-3 RAID 3 Group RAID 3 differs from RAID 5 in one major way. With a RAID 3 Group, the parity information is stored on one disk; with a RAID 5 Group, it is stored on all disks. RAID 3 can perform sequential I/O better than RAID 5, but does not handle random access as well. FLARE™ Operating Environment 2.07 improved RAID 3 processing in several ways: ◆ Use of the write cache is now equivalent to RAID 5 ◆ I/O sizes to disk have been increased ◆ Maximum host transfer size has been increased. RAID 3 is best thought of as a specialized RAID 5, where the expectation is either large or sequential I/O. However, with write cache active for RAID 3, RAID 3 is more flexible than in previous releases, and can handle some level of concurrency. A RAID 3 Group works well for applications that use I/Os of blocks 64 Kbytes and 2-6 EMC CLARiiON CX300, CX500, CX500i, and CX700 Storage Systems Configuration Planning Guide