On Fri, May 6, 2011 at 9:14 PM, Martin Schenker <martin.schenker at profitbricks.com> wrote: > So if I get this right, you'll have to rip the heart out (kill all gluster > processes; server AND client) in order to get to the local server > filesystem. > > I had hoped that the client part could be left running (to the second mirror > brick) when doing repairs etc. Looks like a wrong assumption, I guess... You can do that. I just did it with 3.0.2 on my test [cg]luster. Two nodes, one volume mirrored, both acting as server and client with a local mount. I killed glusterfs (the server demon) on one machine, then checked with "find /mount_point | xargs lsof': no open files. Then unmounted successfully and checked the file system with fsck -f. In the meantime I could create and edit files on the mirrored volume without issues. After I brought up the node's server again files were updated properly and both servers were back in sync. > Are client/server hybrids ONLY connected to the LOCAL server?
