28.12.2016 08:05, likun пишет:
Ok, how to explain “kernel: CPU: 15 PID: 40090 Comm: glusterfsd Not
tainted”, and the fact we are running glusterfsd in docker, has any
different?
Anyway this is kernel bug, imho.
Likun
*发件人:*gluster-users-boun...@gluster.org
Hi Kaleb,
I can give the karma. Do you know where these builds are listed in Centos
Update system?
Regards,
Ramesh
- Original Message -
> From: "Kaleb S. KEITHLEY"
> To: "Grant Ridder" , gluster-users@gluster.org
> Sent: Wednesday,
Ok, how to explain “kernel: CPU: 15 PID: 40090 Comm: glusterfsd Not tainted”,
and the fact we are running glusterfsd in docker, has any different?
Likun
发件人: gluster-users-boun...@gluster.org
[mailto:gluster-users-boun...@gluster.org] 代表 Dmitry Melekhov
发送时间: 2016年12月27日 18:42
收件人:
Hello developers,
The community meeting wasn't held this week either. Because of a lack
of volunteers (to host the meeting) and a lack of attendance.
Considering this, we decided to have Bug Traige meeting from New Year (3rd
Jan).
Last week:
Minutes:
27.12.2016 14:32, likun пишет:
I don’t have any hint about the cause of the crash, any help is
appreciated.
afaik, gluster is completely userspace,
you have kernel crash, so it is not gluster related at all..
___
Gluster-users mailing list
Hi, everyone
I’m running glusterfs 3.8.5 container with kubernetes in a coreos 1185.5.0
environment.
I had a 20 server’s glusterfs cluster, 7 bricks each server, totally a
132-bricks distributed 3-replicated volume.
Here is the volume info:
Type: Distributed-Replicate
Volume ID: