Thanks everybody for the answers!
I'll follow the suggestions outlined below.. when the LAB here is back
up :O
v
On Wed 26 Feb 2014 09:57:31, Xavier Hernandez wrote:
Hi Viktor,
if you want to stop gluster completely in a controlled way:
* umount all current mounted volumes
this
If you just want to shut down one server in a controlled way, go ahead
and /bin/shutdown.
Take a look at /etc/rc.d/rc0.d. glusterd and glusterfsd are both in
there and stop will be run on each. There used to be a glusternfs
service as well that would be stopped, but apparently it was decided
Ok.. so you claim this is a feature :)
So, how do you stop Gluster when you want to stop it then?
v
On Tue 25 Feb 2014 15:31:18, Joe Julian wrote:
Why is that a problem? Having the ability to restart management daemon
without interrupting clients is a common and useful thing.
On February
In 3.3, when we run service glusterd stop, it will stop glusterd and all
glusterfsd (server's processes for volumes) and not stop glusterfs
processes (client processes).
But in my installation of 3.4.2, it could only stop glsuterd, all
glusterfsd processes (server processes) are still alive (this
I have tried a clean installation and a upgradation from 3.3, I have seen
the same problem.
Of coz, I rebooted.
On Wed, Feb 26, 2014 at 1:20 AM, Khoi Mai khoi...@up.com wrote:
When you tried gluster3.4.2-1. did you mean you upgraded it in place while
glusterd was running? Are you missing
I have trid the lastest glusterfs 3.4.2
but I found that I could start the service by *service glusterd status*,
and all volumes are up.
while I ran service glusterd status
it report the glusterd is stopped.
but when I called service glusterd status, I got
glusterd dead but subsys locked
I found
