Hi Markus, Distributed dispersed volume is just LVM's linear LV -> so in case of brick failiure - you loose the data on it. Raid 6 requires 2 disks for parity, so you can make a large RAID6 and use that as a single brick - so the disks that hold the parity data are only 6 ( 3 nodes x 2 disks). Of course if you have too many disks for a single raid controller ,that you can consider a replica volume with an arbiter. Best Regards, Strahil Nikolov On Jan 14, 2020 13:36, Markus Kern <gluster@xxxxxxxxxxx> wrote: > > > Greetings again! > > After reading RedHat documentation regarding optimizing Gluster storage > another question comes to my mind: > > Let's presume that I want to go the distributed dispersed volume way. > Three nodes which two bricks each. > According to RedHat's recommendation, I should use RAID6 as underlying > RAID for my planned workload. > I am frightened by that "waste" of disks in such a case: > When each brick is a RAID6, I would "loose" two disks per brick - 12 > lossed disks in total. > In addition to this, distributed dispersed volume adds another layer of > lossed disk space. > > Am I wrong here? Maybe I didn't understand the recommendations wrong? > > Markus > ________ > > Community Meeting Calendar: > > APAC Schedule - > Every 2nd and 4th Tuesday at 11:30 AM IST > Bridge: https://bluejeans.com/441850968 > > NA/EMEA Schedule - > Every 1st and 3rd Tuesday at 01:00 PM EDT > Bridge: https://bluejeans.com/441850968 > > Gluster-users mailing list > Gluster-users@xxxxxxxxxxx > https://lists.gluster.org/mailman/listinfo/gluster-users ________ Community Meeting Calendar: APAC Schedule - Every 2nd and 4th Tuesday at 11:30 AM IST Bridge: https://bluejeans.com/441850968 NA/EMEA Schedule - Every 1st and 3rd Tuesday at 01:00 PM EDT Bridge: https://bluejeans.com/441850968 Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
