Yes, this is repeating. We’ve ascertained that it has nothing to do at all with file operations on the GPFS side.
Randomly throughout the filesystem mounted via NFS, ls or file access will give ” > ls: reading directory /gpfs/filessystem/test/testdir: Invalid argument “ Trying again later might work on that folder, but might fail somewhere else. We have tried exporting the same filesystem via a standard kernel NFS instead of the CES Ganesha-NFS, and then the problem doesn’t exist. So it is definitely related to the Ganesha NFS server, or its interaction with the file system. Will see if I can get a tcpdump of the issue. Regards, Andreas _____________________________________________ Andreas Mattsson Systems Engineer MAX IV Laboratory Lund University P.O. Box 118, SE-221 00 Lund, Sweden Visiting address: Fotongatan 2, 224 84 Lund Mobile: +46 706 64 95 44 <mailto:[email protected]> [email protected] <http://www.maxiv.se/> www.maxiv.se Från: [email protected] <[email protected]> För Malahal R Naineni Skickat: den 22 november 2018 11:32 Till: [email protected] Kopia: [email protected] Ämne: Re: [gpfsug-discuss] Filesystem access issues via CES NFS We have seen empty lists (ls showing nothing). If this repeats, please take tcpdump from the client and we will investigate. Regards, Malahal. ----- Original message ----- From: Andreas Mattsson <[email protected]> Sent by: [email protected] To: "[email protected]" <[email protected]> Cc: Subject: [gpfsug-discuss] Filesystem access issues via CES NFS Date: Tue, Nov 20, 2018 8:47 PM On one of our clusters, from time to time if users try to access files or folders via the direct full path over NFS, the NFS-client gets invalid information from the server. For instance, if I run “ls /gpfs/filesystem/test/test2/test3” over NFS-mount, result is just full of ???????? If I recurse through the path once, for instance by ls’ing or cd’ing through the folders one at a time or running ls –R, I can then access directly via the full path afterwards. This seem to be intermittent, and I haven’t found how to reliably recreate the issue. Possibly, it can be connected to creating or changing files or folders via a GPFS mount, and then accessing them through NFS, but it doesn’t happen consistently. Is this a known behaviour or bug, and does anyone know how to fix the issue? These NSD-servers currently run Scale 4.2.2.3, while the CES is on 5.0.1.1. GPFS clients run Scale 5.0.1.1, and NFS clients run CentOS 7.5. Regards, Andreas Mattsson _____________________________________________ Andreas Mattsson Systems Engineer MAX IV Laboratory Lund University P.O. Box 118, SE-221 00 Lund, Sweden Visiting address: Fotongatan 2, 224 84 Lund Mobile: +46 706 64 95 44 <mailto:[email protected]> [email protected] <http://www.maxiv.se/> www.maxiv.se _______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org <http://gpfsug.org/mailman/listinfo/gpfsug-discuss> http://gpfsug.org/mailman/listinfo/gpfsug-discuss
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
