Bug 1378815

Summary: [Arbiter] Unable to create file/directory on root of the mount pt. when two bricks are down of a subvolume. (4x2+1)
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Karan Sandha <ksandha>
Component: arbiterAssignee: Ravishankar N <ravishankar>
Status: CLOSED NOTABUG QA Contact: Karan Sandha <ksandha>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhgs-3.2CC: rhs-bugs, storage-qa-internal
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-23 11:32:18 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:
Attachments:
Description Flags
server
none
client
none
server
none
server none

Description Karan Sandha 2016-09-23 10:08:53 UTC 
Created attachment 1204094 [details]
server

Description of problem:
Volume goes into read only mode when two bricks are down from an arbiter subvolume of 4*(2+1) volume. Files cannot be created on root of the mounted directory.

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

[root@dhcp46-231 3.8.2server]# gluster --version
glusterfs 3.8.4 built on Sep 20 2016 07:17:14
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GlusterFS under the terms of the GNU General Public License.


How reproducible:
100%


Steps to Reproduce:
1. Create a 4x(2+1) arbiter volume - testvol
2. Mount it on client
3. Create 10 files and a directory on the mount point.
4. Now kill 2 bricks from the first subvolume i.e Data & Arbiter brick.
5. Create new files on the / of the mount point. 

Actual results:
Mount point goes into read-only mode. No files can be created after killing the bricks.

Expected results:
File creation should work for other bricks except the killed bricks subvolume.

Additional info:
if we create a directory and create files in that directory  it succeed. 
tried this on 2*3 volume and directory creation is successful.
Comment 2 Karan Sandha 2016-09-23 10:10:46 UTC 
Created attachment 1204095 [details]
client
Comment 3 Karan Sandha 2016-09-23 10:11:42 UTC 
Created attachment 1204096 [details]
server
Comment 4 Karan Sandha 2016-09-23 10:12:33 UTC 
Created attachment 1204097 [details]
server
Comment 5 Ravishankar N 2016-09-23 11:32:18 UTC 
The volume was initially created as a plain arbiter, i.e. 1x(2+1) and bricks were added to make it distributed. Since no rebalace/ fix layout was carried out, all creates were going to replicate-0 and hence failing. Things worked fine after a fix layout was performed.