[Lustre-discuss] Path lost when accessing files
cap at nsc.liu.se
Thu Jun 16 16:01:56 PDT 2011
On Thursday, June 16, 2011 03:30:38 PM Sebastien Piechurski wrote:
> This problem is documented in bug 23978
> (http://bugzilla.lustre.org/show_bug.cgi?id=23978). To summarize: the
> fortran runtime is making a call to getcwd() to get the full path to a
> file which was given as a relative path. Lustre sometimes fail to answer
> to this syscall, which returns a non initialized buffer and an error code,
> BUT the fortran runtime does not test the getcwd() return code, and uses
> the buffer as-is.
> The uninitialized buffer is what you see as " @", followed by the relative
> A patch is currently inspected.
Perfectly summarized I'll just add two things.
1) The patch didn't help :-(
2) There are two work-arounds listed in the bz, patch the kernel to retry the
getcwd or build and use an LD_PRELOAD wrapper to retry the getcwd.
> > From: lustre-discuss-bounces at lists.lustre.org
> > we actually a little problems with jobs running on our
> > cluster and using Lustre. Sometimes, we have these errors :
> > forrtl: No such file or directory
> > forrtl: severe (29): file not found, unit 213, file @/suivi.d000
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 198 bytes
Desc: This is a digitally signed message part.
More information about the lustre-discuss