Description of problem:
=======================
By default we append nouuid xfs option for every snapshot brick during creation. But if the original volume brick already has nouuid option set and during snapshot creation another nouuid option is appended than we endup in having 2 nouuid option for same brick.
For example:
=============
Original volume brick xfs options:
/dev/mapper/RHS_vg2-RHS_lv2 on /rhs/brick2 type xfs (rw,noatime,allocsize=1MiB,noattr2,barrier,nogrpid,ihashsize=0,noikeep,inode64,largeio,logbufs=4,noalign,nouuid,osyncisosync,quota,gquota,swalloc)
Snapshoted brick xfs options:
/dev/mapper/RHS_vg2-8e87d5ac707343c4b42ea779befc53b2_0 on /var/run/gluster/snaps/8e87d5ac707343c4b42ea779befc53b2/brick1 type xfs (rw,noatime,allocsize=1MiB,noattr2,barrier,nogrpid,ihashsize=0,noikeep,inode64,largeio,logbufs=4,noalign,nouuid,osyncisosync,quota,gquota,swalloc,nouuid)
Version-Release number of selected component (if applicable):
=============================================================
glusterfs-3.6.0.27-1.el6rhs.x86_64
How reproducible:
=================
always
Steps to Reproduce:
===================
1. Create a ThinLv brick with nouuid option
2. Create a volume having the above brick
3. Create a snapshot of the volume
Actual results:
===============
Newly created snapshoted brick will have entries of nouuid
Expected results:
==================
If the parent(original) brick already has nouuid, we dont need to add it explicitly.
Version : glusterfs-3.7.1-8.el6rhs.x86_64
Craeted a thin LV brick with no uuid option, created a volume out of it.
Take a snapshot of the volume
Original brick :
mount |grep brick1
/dev/mapper/RHS_vg1-RHS_lv1 on /rhs/brick1 type xfs (rw,noatime,nodiratime,inode64,nouuid)
Snapshotted brick :
/dev/mapper/RHS_vg1-a04983a54f5042b7a728077ff2fd4efa_0 on /var/run/gluster/snaps/a04983a54f5042b7a728077ff2fd4efa/brick1 type xfs (rw,noatime,nodiratime,inode64,nouuid)
If the original brick nas nouuid option set during snapshot creation another nouuid option is not appended to it.
Marking the bug 'Verified'
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHSA-2015-1495.html