After I rebooted my GlusterFS servers I can’t connect from clients any more.
The volume is running, but I have to do a volume start FORCE on all server hosts to make it work again.
I am running glusterfs 3.12.1 on Ubuntu 16.04.
Is this a bug?
Here are more details:
"gluster volume status" returns:
Status of volume: gv0
Gluster process TCP Port RDMA Port Online Pid
------------------------------------------------------------------------------
Brick glusterfs-vm-01:/mnt/data/brick N/A N/A N N/A
Brick glusterfs-vm-02:/mnt/data/brick N/A N/A N N/A
Brick glusterfs-vm-03:/mnt/data/brick N/A N/A N N/A
Self-heal Daemon on localhost N/A N/A Y 1864
Self-heal Daemon on glusterfs-vm-03 N/A N/A Y 2343
Self-heal Daemon on glusterfs-vm-02 N/A N/A Y 1900
Task Status of Volume gv0
------------------------------------------------------------------------------
There are no active volume tasks
"gluster volume start gv0" returns:
volume start: gv0: failed: Volume gv0 already started
After I use the force flag ("gluster volume start gv0 force") a "gluster volume status" returns this:
gluster volume status
Status of volume: gv0
Gluster process TCP Port RDMA Port Online Pid
------------------------------------------------------------------------------
Brick glusterfs-vm-01:/mnt/data/brick 49153 0 Y 2629
Brick glusterfs-vm-02:/mnt/data/brick 49153 0 Y 2619
Brick glusterfs-vm-03:/mnt/data/brick 49153 0 Y 2570
Self-heal Daemon on localhost N/A N/A Y 2650
Self-heal Daemon on glusterfs-vm-03 N/A N/A Y 2591
Self-heal Daemon on glusterfs-vm-02 N/A N/A Y 2640
Task Status of Volume gv0
------------------------------------------------------------------------------
There are no active volume tasks
After that clients can connect again!
The volume is running, but I have to do a volume start FORCE on all server hosts to make it work again.
I am running glusterfs 3.12.1 on Ubuntu 16.04.
Is this a bug?
Here are more details:
"gluster volume status" returns:
Status of volume: gv0
Gluster process TCP Port RDMA Port Online Pid
------------------------------------------------------------------------------
Brick glusterfs-vm-01:/mnt/data/brick N/A N/A N N/A
Brick glusterfs-vm-02:/mnt/data/brick N/A N/A N N/A
Brick glusterfs-vm-03:/mnt/data/brick N/A N/A N N/A
Self-heal Daemon on localhost N/A N/A Y 1864
Self-heal Daemon on glusterfs-vm-03 N/A N/A Y 2343
Self-heal Daemon on glusterfs-vm-02 N/A N/A Y 1900
Task Status of Volume gv0
------------------------------------------------------------------------------
There are no active volume tasks
"gluster volume start gv0" returns:
volume start: gv0: failed: Volume gv0 already started
After I use the force flag ("gluster volume start gv0 force") a "gluster volume status" returns this:
gluster volume status
Status of volume: gv0
Gluster process TCP Port RDMA Port Online Pid
------------------------------------------------------------------------------
Brick glusterfs-vm-01:/mnt/data/brick 49153 0 Y 2629
Brick glusterfs-vm-02:/mnt/data/brick 49153 0 Y 2619
Brick glusterfs-vm-03:/mnt/data/brick 49153 0 Y 2570
Self-heal Daemon on localhost N/A N/A Y 2650
Self-heal Daemon on glusterfs-vm-03 N/A N/A Y 2591
Self-heal Daemon on glusterfs-vm-02 N/A N/A Y 2640
Task Status of Volume gv0
------------------------------------------------------------------------------
There are no active volume tasks
After that clients can connect again!
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
