[Bugs] [Bug 1368312] New: Value of `replica.split-brain-status' attribute of a directory in metadata split-brain in a dist-rep volume reads that it is not in split-brain
bugzilla at redhat.com
bugzilla at redhat.com
Fri Aug 19 04:37:23 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1368312
Bug ID: 1368312
Summary: Value of `replica.split-brain-status' attribute of a
directory in metadata split-brain in a dist-rep volume
reads that it is not in split-brain
Product: GlusterFS
Version: mainline
Component: replicate
Severity: medium
Assignee: bugs at gluster.org
Reporter: moagrawa at redhat.com
CC: asriram at redhat.com, atalur at redhat.com,
bugs at gluster.org, moagrawa at redhat.com,
pkarampu at redhat.com, rhs-bugs at redhat.com,
sankarshan at redhat.com, ssampat at redhat.com,
storage-qa-internal at redhat.com
Depends On: 1260779
Blocks: 1255689
+++ This bug was initially created as a clone of Bug #1260779 +++
Description of problem:
-----------------------
In a distribute-replicate volume, the `replica.split-brain-status' attribute of
a directory in metadata split-brain reports that the file is not in
split-brain.
For e.g. the output of `gluster volume heal info' reports that a directory is
in split-brain but the `replica.split-brain-status' reports that the file is
not in split-brain -
On the server -
# gluster v heal 2-test info
Brick server1:/rhs/brick1/b1/
/dir - Is in split-brain
Number of entries: 1
Brick server2:/rhs/brick1/b1/
/dir - Is in split-brain
Number of entries: 1
Brick server3:/rhs/brick1/b1/
Number of entries: 0
Brick server4:/rhs/brick1/b1/
Number of entries: 0
On the client -
# getfattr -n replica.split-brain-status dir
# file: dir
replica.split-brain-status="The file is not under data or metadata split-brain"
Version-Release number of selected component (if applicable):
-------------------------------------------------------------
glusterfs-3.7.1-14.el7rhgs.x86_64
How reproducible:
------------------
100%
Steps to Reproduce:
-------------------
1. Create a directory using a fuse client in a distribute-replicate volume.
2. Kill one brick of one of the replica sets in the volume and modify the
permissions of the directory.
3. Start volume with force option.
4. Kill the other brick in the same replica set and modify permissions of the
directory again.
5. Start volume with force option. Examine the output of `gluster volume heal
<vol-name> info' command on the server and the output of `getfattr -n
replica.split-brain-status <path-to-dir>' on the client.
Actual results:
---------------
`getfattr -n replica.split-brain-status <path-to-dir>' reports that the file is
not in split-brain even though it is in split-brain.
Expected results:
-----------------
The value of `replica.split-brain-status' attribute should read that the file
is in metadata split-brain.
--- Additional comment from Anjana Suparna Sriram on 2015-09-18 05:53:18 EDT
---
Hi Pranith,
Could you please review the edited doc text and sign off to be included in the
Known Issues chapter.
Regards,
Anjana
--- Additional comment from Pranith Kumar K on 2015-09-18 06:27:07 EDT ---
hi Anjana,
This feature is Anuradha's baby. I changed Needinfo to Anuradha.
Pranith
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1260779
[Bug 1260779] Value of `replica.split-brain-status' attribute of a
directory in metadata split-brain in a dist-rep volume reads that it is not
in split-brain
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list