Hide Forgot
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.
Created attachment 1204095 [details] client
Created attachment 1204096 [details] server
Created attachment 1204097 [details] server
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.