or reporting this issue.
>
> Thanks Joe Julian for giving the crucial piece of lead which helped me
> identify
> the issue.
>
> ~kp
>
> >
> >
> > > Gesendet: Montag, 09. März 2015 um 04:13 Uhr
> > > Von: "Joe Julian"
> > > A
Gesendet: Montag, 09. März 2015 um 04:13 Uhr
> > Von: "Joe Julian"
> > An: gluster-users@gluster.org
> > Betreff: Re: [Gluster-users] Upgrade from 3.5 to 3.6: issue with socket
> >
> > I've seen this when the subprocesses running glustershd and nfs were not
4:13 Uhr
> Von: "Joe Julian"
> An: gluster-users@gluster.org
> Betreff: Re: [Gluster-users] Upgrade from 3.5 to 3.6: issue with socket
>
> I've seen this when the subprocesses running glustershd and nfs were not
> restarted after the upgrade. I've also seen it if
I've seen this when the subprocesses running glustershd and nfs were not
restarted after the upgrade. I've also seen it if nfs is disabled on all
volumes.
On 03/08/2015 09:10 PM, Krishnan Parthasarathi wrote:
I just upgraded from 3.5.3 to 3.6.2 and have issues mounting my volume on a
client. O
>
> I just upgraded from 3.5.3 to 3.6.2 and have issues mounting my volume on a
> client. On the server side I found this error message which might be the
> cause of my issues:
Could you describe the issues you are facing?
>
> [2015-03-08 13:22:36.383715] W [socket.c:611:__socket_rwv] 0-managem
Hello,
I just upgraded from 3.5.3 to 3.6.2 and have issues mounting my volume on a
client. On the server side I found this error message which might be the cause
of my issues:
[2015-03-08 13:22:36.383715] W [socket.c:611:__socket_rwv] 0-management: readv
on /var/run/6b8f1f2526c6af8a87f1bb611a
