[Gluster-users] Revisit: FORTRAN Codes and File I/O

[Brian Smith]

I received these in my debug output during a run that failed:

[2010-06-30 12:34:25] D [read-ahead.c:468:ra_readv] readahead:
unexpected offset (8192 != 1062) resetting
[2010-06-30 12:34:25] D [read-ahead.c:468:ra_readv] readahead:
unexpected offset (8192 != 1062) resetting
[2010-06-30 12:34:25] D [read-ahead.c:468:ra_readv] readahead:
unexpected offset (8192 != 1062) resetting
[2010-06-30 12:34:25] D [read-ahead.c:468:ra_readv] readahead:
unexpected offset (8192 != 1062) resetting

I disabled the read-ahead translator as well as the three other
performance translators commented out in my vol file (I'm on GigE; the
docs say I can still reach link max anyway) and my processes appear to
be running smoothly.  I'll go ahead and submit the bug report with
tracing enabled as well.

-Brian


-- 
Brian Smith
Senior Systems Administrator
IT Research Computing, University of South Florida
4202 E. Fowler Ave. ENB204
Office Phone: +1 813 974-1467
Organization URL: http://rc.usf.edu


On Tue, 2010-06-29 at 21:45 -0700, Harshavardhana wrote:
> On 06/29/2010 04:36 PM, Brian Smith wrote:
> > It's obviously been a while since I brought this issue up, but it has
> > cropped up again for us.  We're now on 3.0.3 and I've included my
> > glusterfs*.vol files below.  We end up with file i/o errors like the
> > ones below:
> >
> > forrtl: File exists
> > forrtl: severe (10): cannot overwrite existing file, unit 18,
> > file /work/b/brs/vdWSi/CHGCAR
> >
> > Even if the file existed, it shouldn't really be a problem.  Other file
> > systems work just fine.  I'll get some more verbose logging going and
> > share my output.  glusterfsd.vol is the same in the referenced e-mails
> > below.
> >
> > Thanks in advance,
> > -Brian
> >
> >    
> Hi Brian,
> 
>       We would need debug or trace logs from the client side? . This 
> seems to be a race and i assume you are using "vasp" application which 
> creates the file CHGCAR, DOSCAR etc files.
> Since we don't have vasp in house, would you mind opening a bug at 
> http://bugs.gluster.com/
> and also "trace" logs from the client side attached with it.
> 
> Regards
>