Gluster users - Jan 2017 - WRITE => -1 (Input/output error)

None that I am aware of, would I be looking in Gluster logs to see EIO? 

I had a look at the source code for fuse_writev_cbk to see if I could give me
some hints as to where the issue is however no joy.

Would there be somewhere that would tell me what operation is failing what file
etc? Maybe I can turn up logging level.
> On 13 Jan 2017, at 12:14, Mohammed Rafi K C <rkavunga at redhat.com>
wrote:
> 
> the writes might have failed with EIO. Was there any network failure
> back and forth ?
> 
> 
> RafI KC
> 
> 
> On 01/12/2017 07:50 PM, Stephen Martin wrote:
>> Hi looking for help with an error I?m getting.
>> 
>> I?m new to Gluster but have gone though most of the getting started and
overview documentation.
>> 
>> I have been given a production server that uses Gluster and although
its up and running and fuctioning I see lots of errors in the logs
>> 
>>    [2017-01-12 13:19:37.326562] W [fuse-bridge.c:2167:fuse_writev_cbk]
0-glusterfs-fuse: 5852034: WRITE => -1 (Input/output error)
>> 
>> I don't really know what action caused it, I get lots of these
logged how can I start a diagnostic?
>> 
>> Thanks
>> 
>> .
>> _______________________________________________
>> Gluster-users mailing list
>> Gluster-users at gluster.org
>> http://www.gluster.org/mailman/listinfo/gluster-users
>

I debug fuse mounts by running glusterfs binary directly with the below
command. I find it works best to incorporate this command into a test
script.

'glusterfs --volfile-server=$onevolumeserver --log-file=$logfile
--log-level=$level --volfile-id=$volname $mountpoint`

I like to use '--no-daemon', or the '--debug'[1]. For $level,
start
with DEBUG, then try TRACE. TRACE is _very_ verbose.

For more info, see: 'glusterfs --help' or 'man glusterfs'.

The mount.glusterfs handler may be reviewed via:  'less -S $(which
mount.glusterfs)'

[1] Run in debug mode.  This option sets --no-daemon, --log-level to DEBUG,
and --log-file to console.

On Fri, Jan 13, 2017 at 7:25 AM, Stephen Martin <sm at hypersrv.com>
wrote:
> None that I am aware of, would I be looking in Gluster logs to see EIO?
>
> I had a look at the source code for fuse_writev_cbk to see if I could give
> me some hints as to where the issue is however no joy.
>
> Would there be somewhere that would tell me what operation is failing what
> file etc? Maybe I can turn up logging level.
>
> > On 13 Jan 2017, at 12:14, Mohammed Rafi K C <rkavunga at
redhat.com> wrote:
> >
> > the writes might have failed with EIO. Was there any network failure
> > back and forth ?
> >
> >
> > RafI KC
> >
> >
> > On 01/12/2017 07:50 PM, Stephen Martin wrote:
> >> Hi looking for help with an error I?m getting.
> >>
> >> I?m new to Gluster but have gone though most of the getting
started and
> overview documentation.
> >>
> >> I have been given a production server that uses Gluster and
although
> its up and running and fuctioning I see lots of errors in the logs
> >>
> >>    [2017-01-12 13:19:37.326562] W
[fuse-bridge.c:2167:fuse_writev_cbk]
> 0-glusterfs-fuse: 5852034: WRITE => -1 (Input/output error)
> >>
> >> I don't really know what action caused it, I get lots of these
logged
> how can I start a diagnostic?
> >>
> >> Thanks
> >>
> >> .
> >> _______________________________________________
> >> Gluster-users mailing list
> >> Gluster-users at gluster.org
> >> http://www.gluster.org/mailman/listinfo/gluster-users
> >
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20170113/f67336cd/attachment.html>