Joshua, That is correct. If at the time you try to mount the volume the server is down, then you won't be able to mount the volume in the first place. If this is a concern, you can set up something like ucarp to handle IP failover so your mount command will work, but usually mounting is something that is not done frequently, right? Or you could have a round robin DNS entry that points to all of your storage nodes so that your mount command is essentially hitting a different server each time. -Jacob -----Original Message----- From: Joshua Baker-LePain [mailto:jlb17 at duke.edu] Sent: Thursday, December 09, 2010 2:25 PM To: Jacob Shucart Cc: 'gluster-users' Subject: RE: GlusterFS 3.1.1 - local volume mount On Thu, 9 Dec 2010 at 4:19pm, Jacob Shucart wrote > When mounting as a glusterfs, the mount command below is used to establish > the connection to the cluster, but once the connection is established to > the cluster the client system has connections open to all of the servers > and not just the one used to mount, so there is still no single point of > failure. But if the server listed in the mount command is down *when the client attempts to establish the connection* (i.e. at mount time), then the client won't be able to discover the rest of the cluster and the mount will fail. Right? -- Joshua Baker-LePain QB3 Shared Cluster Sysadmin UCSF
