Bug 1145090 - [SNAPSHOT]: If the snapshoted brick has xfs options set as part of its creation, they are not automount upon reboot
Summary: [SNAPSHOT]: If the snapshoted brick has xfs options set as part of its creati...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 3.6.0
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Sachin Pandit
QA Contact:
URL:
Whiteboard: SNAPSHOT
Depends On: 1132058 1132451
Blocks: 1124583
TreeView+ depends on / blocked
 
Reported: 2014-09-22 11:06 UTC by Sachin Pandit
Modified: 2015-07-26 22:05 UTC (History)
7 users (show)

Fixed In Version: glusterfs-3.6.0beta2
Clone Of: 1132451
Environment:
Last Closed: 2014-11-11 08:39:50 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Anand Avati 2014-09-22 11:34:13 UTC
REVIEW: http://review.gluster.org/8803 (glusterd: Parsing key/value pair with value containing '=') posted (#1) for review on release-3.6 by Sachin Pandit (spandit)

Comment 2 Anand Avati 2014-09-22 11:52:00 UTC
REVIEW: http://review.gluster.org/8803 (glusterd: Parsing key/value pair with value containing '='.) posted (#2) for review on release-3.6 by Sachin Pandit (spandit)

Comment 3 Anand Avati 2014-09-23 10:12:48 UTC
COMMIT: http://review.gluster.org/8803 committed in release-3.6 by Vijay Bellur (vbellur) 
------
commit f46f406d3b010fd0ad1a03d5cfe1658904967be0
Author: Vijaikumar M <vmallika>
Date:   Thu Aug 21 17:07:25 2014 +0530

    glusterd: Parsing key/value pair with value containing '='.
    
    Parsing key/value pair in the brickinfo file, where value contains '='
    would truncate everything after '=' in value.
    
    For example:
    A key/value pair
    mnt-opts=rw,noatime,allocsize=1MiB,noattr2
    
    is parsed as:
    mnt-opts=rw,noatime,allocsize
    
    Change-Id: I4e279c2a356a8a16eb20d4358d7c8a8cc5724b65
    BUG: 1145090
    Signed-off-by: Vijaikumar M <vmallika>
    Reviewed-on: http://review.gluster.org/8507
    Reviewed-by: Atin Mukherjee <amukherj>
    Reviewed-by: Rajesh Joseph <rjoseph>
    Reviewed-by: Sachin Pandit <spandit>
    Reviewed-by: Krishnan Parthasarathi <kparthas>
    Tested-by: Krishnan Parthasarathi <kparthas>
    Signed-off-by: Sachin Pandit <spandit>
    Reviewed-on: http://review.gluster.org/8803
    Tested-by: Gluster Build System <jenkins.com>

Comment 4 Niels de Vos 2014-09-25 08:27:57 UTC
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta2 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018883.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

Comment 5 Niels de Vos 2014-11-11 08:39:50 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.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users


Note You need to log in before you can comment on or make changes to this bug.