Hi, I'm re-adding lustre-discuss (I mistakenly replied directly to Kurt).
It's interesting that you can't re-export the 2.5.3 system on the client which is able to export the 1.8.9. The support for the lustre 2 quotas has been added to the 1.8 client somewhere between 1.8.7 and 1.8.9. There are a few more commits to the 1.8 branch in Whamcloud's git, but unfortunately there is not much activity anymore. Important fixes which haven't been landed on 1.8 are in LU-3596 and LU-1126. best regards, Martin On 05/21/2015 07:03 PM, Kurt Strosahl wrote: > Hi, > > The purpose of it was to allow access to the lustre file system to any > system that can mount over nfs (also because our lustre system runs over IB, > and this allows peoples desktops to get to the system). > > The thing is that the export of lustre 1.8.9 over the 1.8.7 client has > been working for years (it was set up back in 2009 I believe, before I was on > the project). It is only the lustre 2.5.3 system that mounts but is not > reachable via NFS. > > Today I compiled the 2.5.3 client for a new system that has IB but does > not need access to the lustre file system, mounted the new lustre system, and > was able to export successfuly. So the problem clearly lies with some > combination of the old OS (RHEL5), old client (1.8.7) and new lustre (2.5.3). > > This isn't the first oddity I've encountered. Early in the testing > process I discovered that the quotas in 2.5.3 are not visible to the 1.8.7 > clients (but are visible to the 1.8.9 clients). > > At this point I'm probably going to try building a new gateway (with new > hardware and the new OS), mount the new lustre with the client I know works, > and export the new area that way. > > I was just hoping that someone would say "oh, just mount it with the derp > option". > > thanks, > Kurt > > ----- Original Message ----- > From: "Martin Hecht" > To: "Kurt Strosahl" > Sent: Thursday, May 21, 2015 12:51:41 PM > Subject: Re: [lustre-discuss] Exporting a lustre mounted directory via nfs > > Hi Kurt, > > some time ago we had a client re-exporting a lustre 1.8.x in rhel5. It > worked quite well, but I believe you shouldn't run too many nfs clients > with this construct. > > What's the reason for the reexport? If your lustre is on an infiniband > and you want to make it available on clients which have no IB card, lnet > routing over a tcp-network might be a better option than the nfs re-export. > > If the reason is that you can't build the lustre client... well... the > nfs reexport might be worth trying, but I don't have any experience with > re-exporting a lustre 2 file system (although I think the client version > is more important in this scenario). > > best regards, > Martin > > On 05/20/2015 09:14 PM, Kurt Strosahl wrote: >> Sorry, left off some important info... >> >> the system is rhel5, with client 1.8.7... the lustre file system is 2.5.3 >> (the system already exports a 1.8.9 lustre file system). >> >> w/r, >> Kurt >> >> ----- Original Message ----- >> From: "Kurt Strosahl" >> To: lustre-discuss@lists.lustre.org >> Sent: Wednesday, May 20, 2015 2:55:39 PM >> Subject: Exporting a lustre mounted directory via nfs >> >> Good Afternoon, >> >> I'm attempting to use nfs to export a lustre mount point on a client box >> (essentially acting as a gateway for systems that don't have the lustre >> client). I've mounted lustre, and added it to the nfs exports file (it >> shows up as exported) but when I try to mount the nfs point the system >> hangs. On the server side (the lustre gateway) I do see the test system >> authenticating. >> >> w/r, >> Kurt >> _______________________________________________ >> lustre-discuss mailing list >> lustre-discuss@lists.lustre.org >> http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org _______________________________________________ lustre-discuss mailing list lustre-discuss@lists.lustre.org http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
