I''ve read you can export lustre via nfs but I''m running into some trouble. I tried nfs3 but when I would check a directory, all the files where labeled red and ls -al showed no username or permissions, just "?" This was on the server nfsd: non-standard errno: -43 LustreError: 11-0: an error occurred while communicating with 192.168.5.104 at tcp. The mds_getxattr operation failed with -43 nfsd: non-standard errno: -43 LustreError: 11-0: an error occurred while communicating with 192.168.5.104 at tcp. The mds_getxattr operation failed with -43 nfsd: non-standard errno: -43 So then I tried out nfs4 and trying to navigate or ls into the nfs mount would hang and I would on get the mds_getxattr error. Something I''m doing wrong? -- Personally, I liked the university. They gave us money and facilities, we didn''t have to produce anything! You''ve never been out of college! You don''t know what it''s like out there! I''ve worked in the private sector. They expect results. -Ray Ghostbusters
Hi David, David Noriega wrote:> I''ve read you can export lustre via nfs but I''m running into some > trouble. I tried nfs3 but when I would check a directory, all the > files where labeled red and ls -al showed no username or permissions, > just "?" This was on the server > > nfsd: non-standard errno: -43 > LustreError: 11-0: an error occurred while communicating with > 192.168.5.104 at tcp. The mds_getxattr operation failed with -43 > nfsd: non-standard errno: -43 > LustreError: 11-0: an error occurred while communicating with > 192.168.5.104 at tcp. The mds_getxattr operation failed with -43 > nfsd: non-standard errno: -43We see these when the user trying to access the file system on the NFS client is not known on the MDS. This also sometimes happens to us if the NFS server is exporting with root_squash enabled (good!) and the user on the client is root but the mapped user is not know on the MDS... This will the result in the described display on the NFS client.> So then I tried out nfs4 and trying to navigate or ls into the nfs > mount would hang and I would on get the mds_getxattr error.Sorry, no experience with NFS4 (yet). Hope this helps, Frederik -- Frederik Ferner Computer Systems Administrator phone: +44 1235 77 8624 Diamond Light Source Ltd. mob: +44 7917 08 5110 (Apologies in advance for the lines below. Some bits are a legal requirement and I have no control over them.)
On Thu, 2010-09-02 at 11:22 -0500, David Noriega wrote:> > nfsd: non-standard errno: -43 > LustreError: 11-0: an error occurred while communicating with > 192.168.5.104 at tcp. The mds_getxattr operation failed with -43This means that your clients and MDS do not have their password and group databases in sync. Synchronize them (either with sneakernet or a centralized database like NIS or LDAP) and this should go away. Of course, you need to keep them in sync, so changes to a sneakernet maintained database need to be propagated -- which is why NIS or LDAP become useful if changes are more than infrequent. b. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part Url : http://lists.lustre.org/pipermail/lustre-discuss/attachments/20100902/3ebf9286/attachment.bin