On Thursday, June 16, 2011 03:30:38 PM Sebastien Piechurski wrote: > Hi, > > 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 > path. > > 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. /Peter > > From: lustre-discuss-boun...@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 ...
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Lustre-discuss mailing list Lustre-discuss@lists.lustre.org http://lists.lustre.org/mailman/listinfo/lustre-discuss
