Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 871986

Summary:	[RFE] Striping should have optional parity/checksum
Product:	[Community] GlusterFS	Reporter:	Dynamic Packet <git>
Component:	stripe	Assignee:	Nagaprasad Sathyanarayana <nsathyan>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	mainline	CC:	gluster-bugs, rwheeler, smohan
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-09-27 13:21:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dynamic Packet 2012-10-31 22:30:41 UTC

Description of problem:

 Striping currently behaves only like RAID-0. It would be great if there could be an option to have a parity brick. The idea is to behave more like RAID-5 (or possibly RAID-6), which would tolerate the failure of 1 or more bricks. This enhancement would allow increased data integrity and increased usable storage as compared to current options (like replica 2).

Comment 1 Amar Tumballi 2012-11-02 07:18:45 UTC

Hello Dynamic Packet... 

Please have a look at http://www.gluster.org/community/documentation/index.php/Planning34/Disperse 

We will keep the current stripe translator as is, and will come up with new translator to handle the request you asked for.

Comment 3 Niels de Vos 2014-09-27 13:21:07 UTC

This is included in glusterfs-3.6 as disperse aka ec (erasure coding).

More details here:
- http://www.gluster.org/community/documentation/index.php/Features/disperse

*** This bug has been marked as a duplicate of bug 1118629 ***