On 09/03/2015 07:22 AM, E.S. Rosenberg wrote: > On Wed, Sep 2, 2015 at 8:47 PM, Wahl, Edward <ew...@osc.edu> wrote: > >> That would be my guess here. Any chance this is across NFS? Seen that a >> great deal with this error, it used to cause crashes. >> > Strictly speaking it is not, but it may be because a part of the path the > server 'sees'/'knows' is a symlink to the lustre filesystem which lives on > nfs... > Ah, I can remember a problem we had some years ago, when users with their $HOME on NFS were accessing many files in directories on lustre via symlink. Somehow the NAS box serving the nfs file system didn't immediately notice that the files weren't on its own file system and repeatedly had to look up in its cache, just to notice that the files are somewhere else behind a symlink. If I recall correctly, the problem could be avoided by: - Either access the file via absolute path, or cd into the directory (both via mount point, not (!) via symlink) - Or make the symlink an absolute one (I'm not 100% sure, but I believe the problem was only with relative links pointing out of the NFS upwards across the mountpoint and down again into the lustre file system). It could be something similar here. Do you have any chance to access the files via absolute path in your setup and web server configuration?
best regards, Martin
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ lustre-discuss mailing list lustre-discuss@lists.lustre.org http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
