![]() ![]() Over time Chunklet mellowed out, he realised hey it’s good to share and instead of demanding a whole disk to himself he was happy with 1GB of any given disk. This traditional and inflexible approach is shown in the diagram below: So on a traditional storage array to set up a simple RAID 5 2+1 set, you would need 3 disks, 2 data and 1 parity each of which was dedicated entirely to being part of that RAID set. ![]() He existed on a traditional storage array and since he didn’t get on with anyone he demanded a whole disk to himself. ![]() Things were not always so good for Chunklet, back in the day Chunklet was a bad dude with a bad attitude. Let’s introduce Chunklet, as its Chunklet that enables 3PAR to have a unique architecture and enable many of its capabilities. The perfect place to start is by looking at the 3PAR architecture, and specifically how 3PAR uses layers of abstraction to deliver a unique and flexible approach to RAID. I wanted to start a series of posts looking at 3PAR 101, a back to basics/ beginners guide to 3PAR. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |