Hi Raghavendra and Ben,
thanks for your answers.
The volume is a backend of nova instances of Openstack infrastructure,
and as wrote by Raghavendra not seems, but I'm sure the compute node has
been writing to gluster volume after a potential network problem, but in
our monitoring system we did
i"
> To: gluster-us...@gluster.org, gluster-devel@gluster.org
> Sent: Monday, October 27, 2014 9:51:37 AM
> Subject: [Gluster-devel] gluster write million of lines: WRITE => -1
> (Transport endpoint is not connected)
>
> Hi all,
> One server Redhat 6 with this rpms s
Seems like there were on-going write operations. On errors we log and
network disconnect has resulted in these logs.
On Mon, Oct 27, 2014 at 7:21 PM, Sergio Traldi
wrote:
> Hi all,
> One server Redhat 6 with this rpms set:
>
> [ ~]# rpm -qa | grep gluster | sort
> glusterfs-3.5.2-1.el6.x86_64
>
Hi all,
One server Redhat 6 with this rpms set:
[ ~]# rpm -qa | grep gluster | sort
glusterfs-3.5.2-1.el6.x86_64
glusterfs-api-3.5.2-1.el6.x86_64
glusterfs-cli-3.5.2-1.el6.x86_64
glusterfs-fuse-3.5.2-1.el6.x86_64
glusterfs-geo-replication-3.5.2-1.el6.x86_64
glusterfs-libs-3.5.2-1.el6.x86_64
glust
