Bug 1140861

Summary:	A new xattr is needed to store ec parameters
Product:	[Community] GlusterFS	Reporter:	Xavi Hernandez <jahernan>
Component:	disperse	Assignee:	Xavi Hernandez <jahernan>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1140862 (view as bug list)		Environment:
Last Closed:	2015-05-14 17:27:40 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:
Bug Depends On:
Bug Blocks:	1140862

Description Xavi Hernandez 2014-09-11 21:23:01 UTC

Description of problem:

Current ec implementation uses a special matrix with a fixed stripe size. This works fine, but most probably this will need to be changed or tweaked in the future to add features or performance. Since any change to this data involves changes in the encoding/decoding, it's necessary to store this information in each file to be able to recover it using the right configuration.

To do so, it's necessary to create a new xattr that will store this information and will allow backward compatibility.

Version-Release number of selected component (if applicable): master


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Anand Avati 2014-09-18 14:58:01 UTC

REVIEW: http://review.gluster.org/8770 (ec: Add config information in an xattr) posted (#1) for review on master by Xavier Hernandez (xhernandez)

Comment 2 Anand Avati 2014-09-23 09:01:23 UTC

REVIEW: http://review.gluster.org/8770 (ec: Add config information in an xattr) posted (#2) for review on master by Xavier Hernandez (xhernandez)

Comment 3 Anand Avati 2014-09-23 16:12:40 UTC

COMMIT: http://review.gluster.org/8770 committed in master by Vijay Bellur (vbellur) 
------
commit 5f79d6e08fbb930aa67dd59eb39cbece6f138b59
Author: Xavier Hernandez <xhernandez>
Date:   Thu Sep 18 16:50:47 2014 +0200

    ec: Add config information in an xattr
    
    To simplify backward compatibility of the ec xlator when some
    parameter or the implementation itself is changed, a new xattr
    is added to each file with the configuration needed to recover
    it.
    
    The new attribute is called 'trusted.ec.config', and it's a 64-bit
    value containing the following information:
    
        8 bits: version of the config information (currently always 0)
        8 bits: algorithm used to encode the file (currently always 0)
        8 bits: size of the galois field (currently always 8)
        8 bits: number of bricks
        8 bits: redundancy
       24 bits: chunk size (currently 512)
    
    This new xattr could allow, in a future version, to have different
    configurations per file.
    
    Change-Id: I8c12d40ff546cc201fc66caa367484be3d48aeb4
    BUG: 1140861
    Signed-off-by: Xavier Hernandez <xhernandez>
    Reviewed-on: http://review.gluster.org/8770
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Dan Lambright <dlambrig>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 4 Niels de Vos 2015-05-14 17:27:40 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 5 Niels de Vos 2015-05-14 17:35:36 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 6 Niels de Vos 2015-05-14 17:37:58 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 7 Niels de Vos 2015-05-14 17:43:42 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user