* [NFS] Redhat WS4 mount default changed to tcp ?
@ 2008-01-14 16:41 Sev Binello
[not found] ` <478B90A1.5000900-IGkKxAqZmp0@public.gmane.org>
0 siblings, 1 reply; 23+ messages in thread
From: Sev Binello @ 2008-01-14 16:41 UTC (permalink / raw)
To: nfs
Does anyone know the reason Redhat changed the default mount protocol to
tcp ?
Can anything be inferred from this change ?
Should we be mounting file systems tcp now ?
Thank
-Sev
--
Sev Binello
Brookhaven National Laboratory
Upton, New York
631-344-5647
sev-IGkKxAqZmp0@public.gmane.org
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
^ permalink raw reply [flat|nested] 23+ messages in thread[parent not found: <478B90A1.5000900-IGkKxAqZmp0@public.gmane.org>]
* Re: [NFS] Redhat WS4 mount default changed to tcp ? [not found] ` <478B90A1.5000900-IGkKxAqZmp0@public.gmane.org> @ 2008-01-14 17:06 ` Trond Myklebust [not found] ` <1200330387.7470.11.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org> 0 siblings, 1 reply; 23+ messages in thread From: Trond Myklebust @ 2008-01-14 17:06 UTC (permalink / raw) To: Sev Binello; +Cc: nfs On Mon, 2008-01-14 at 11:41 -0500, Sev Binello wrote: > Does anyone know the reason Redhat changed the default mount protocol to > tcp ? It is a more robust protocol than UDP, specially when you are using large values for rsize/wsize (by 'large' I mean 'significantly greater than the MTU for your network'). > Can anything be inferred from this change ? > Should we be mounting file systems tcp now ? If you have no performance problems with UDP, then by all means keep using it... Cheers Trond ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that nfs@lists.sourceforge.net is being discontinued. Please subscribe to linux-nfs@vger.kernel.org instead. http://vger.kernel.org/vger-lists.html#linux-nfs ^ permalink raw reply [flat|nested] 23+ messages in thread
[parent not found: <1200330387.7470.11.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>]
* Re: [NFS] Redhat WS4 mount default changed to tcp ? [not found] ` <1200330387.7470.11.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org> @ 2008-01-14 17:22 ` Sev Binello [not found] ` <478B9A64.5030903-IGkKxAqZmp0@public.gmane.org> 0 siblings, 1 reply; 23+ messages in thread From: Sev Binello @ 2008-01-14 17:22 UTC (permalink / raw) To: Trond Myklebust; +Cc: nfs Trond Myklebust wrote: > On Mon, 2008-01-14 at 11:41 -0500, Sev Binello wrote: > >> Does anyone know the reason Redhat changed the default mount protocol to >> tcp ? >> > > It is a more robust protocol than UDP, specially when you are using > large values for rsize/wsize (by 'large' I mean 'significantly greater > than the MTU for your network'). > > Wasn't that always the case ? Was wondering Why now ? >> Can anything be inferred from this change ? >> Should we be mounting file systems tcp now ? >> > > If you have no performance problems with UDP, then by all means keep > using it... > > Cheers > Trond > > -- Sev Binello Brookhaven National Laboratory Upton, New York 631-344-5647 sev-IGkKxAqZmp0@public.gmane.org ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that nfs@lists.sourceforge.net is being discontinued. Please subscribe to linux-nfs@vger.kernel.org instead. http://vger.kernel.org/vger-lists.html#linux-nfs ^ permalink raw reply [flat|nested] 23+ messages in thread
[parent not found: <478B9A64.5030903-IGkKxAqZmp0@public.gmane.org>]
* Re: [NFS] Redhat WS4 mount default changed to tcp ? [not found] ` <478B9A64.5030903-IGkKxAqZmp0@public.gmane.org> @ 2008-01-14 17:39 ` Trond Myklebust 2008-11-07 17:44 ` [NFS] export dir thru 2 diff path names Sev Binello 1 sibling, 0 replies; 23+ messages in thread From: Trond Myklebust @ 2008-01-14 17:39 UTC (permalink / raw) To: Sev Binello; +Cc: nfs On Mon, 2008-01-14 at 12:22 -0500, Sev Binello wrote: > Trond Myklebust wrote: > > On Mon, 2008-01-14 at 11:41 -0500, Sev Binello wrote: > > > >> Does anyone know the reason Redhat changed the default mount protocol to > >> tcp ? > >> > > > > It is a more robust protocol than UDP, specially when you are using > > large values for rsize/wsize (by 'large' I mean 'significantly greater > > than the MTU for your network'). > > > > > Wasn't that always the case ? Was wondering Why now ? The reason why it wasn't made a default earlier is that TCP server support was not too good throughout most of the 2.4.x series of kernels. It has been improved in more recent kernels to the point where everyone feels comfortable with having it as a default. Trond ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that nfs@lists.sourceforge.net is being discontinued. Please subscribe to linux-nfs@vger.kernel.org instead. http://vger.kernel.org/vger-lists.html#linux-nfs ^ permalink raw reply [flat|nested] 23+ messages in thread
* [NFS] export dir thru 2 diff path names [not found] ` <478B9A64.5030903-IGkKxAqZmp0@public.gmane.org> 2008-01-14 17:39 ` Trond Myklebust @ 2008-11-07 17:44 ` Sev Binello [not found] ` <49147E79.6000508-IGkKxAqZmp0@public.gmane.org> 1 sibling, 1 reply; 23+ messages in thread From: Sev Binello @ 2008-11-07 17:44 UTC (permalink / raw) To: nfs Can anyone tell me if it's ok to export the same file system through 2 different paths ( one is a link) ? Thanks -Sev -- Sev Binello Brookhaven National Laboratory Upton, New York 631-344-5647 sev-IGkKxAqZmp0@public.gmane.org ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that nfs@lists.sourceforge.net is being discontinued. Please subscribe to linux-nfs@vger.kernel.org instead. http://vger.kernel.org/vger-lists.html#linux-nfs ^ permalink raw reply [flat|nested] 23+ messages in thread
[parent not found: <49147E79.6000508-IGkKxAqZmp0@public.gmane.org>]
* Re: [NFS] export dir thru 2 diff path names [not found] ` <49147E79.6000508-IGkKxAqZmp0@public.gmane.org> @ 2008-11-09 15:58 ` J. Bruce Fields 2008-11-10 15:55 ` Sev Binello 0 siblings, 1 reply; 23+ messages in thread From: J. Bruce Fields @ 2008-11-09 15:58 UTC (permalink / raw) To: Sev Binello; +Cc: nfs On Fri, Nov 07, 2008 at 12:44:25PM -0500, Sev Binello wrote: > Can anyone tell me if it's ok to export the same file system > through 2 different paths ( one is a link) ? I actually don't know. You could try it and tell us what you find out.... If you're exporting something *containing* the symlink and expecting the client to traverse into the filesystem, be aware that symlinks over NFS are actually interpreted (and followed) on the client--so they're interpreted as *client-side* paths, not server-side. If the path you're exporting is itself a symlink--it probably depends on how nfs-utils treats symlinks found in /etc/exports. I'd have to try it or check the code. Another way to export the filesystem in two different places would be with mount --bind. --b. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that nfs@lists.sourceforge.net is being discontinued. Please subscribe to linux-nfs@vger.kernel.org instead. http://vger.kernel.org/vger-lists.html#linux-nfs ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [NFS] export dir thru 2 diff path names 2008-11-09 15:58 ` J. Bruce Fields @ 2008-11-10 15:55 ` Sev Binello [not found] ` <49185984.8010500-IGkKxAqZmp0@public.gmane.org> 0 siblings, 1 reply; 23+ messages in thread From: Sev Binello @ 2008-11-10 15:55 UTC (permalink / raw) To: J. Bruce Fields; +Cc: nfs Well the simplest approach doesn't work. i.e put symb link and actual path in the export file & try exporting it Exportfs dereferences the link and states that duplicates are not allowed. -Sev J. Bruce Fields wrote: > On Fri, Nov 07, 2008 at 12:44:25PM -0500, Sev Binello wrote: > >> Can anyone tell me if it's ok to export the same file system >> through 2 different paths ( one is a link) ? >> > > I actually don't know. You could try it and tell us what you find > out.... > > If you're exporting something *containing* the symlink and expecting the > client to traverse into the filesystem, be aware that symlinks over NFS > are actually interpreted (and followed) on the client--so they're > interpreted as *client-side* paths, not server-side. > > If the path you're exporting is itself a symlink--it probably depends on > how nfs-utils treats symlinks found in /etc/exports. I'd have to try it > or check the code. > > Another way to export the filesystem in two different places would be > with mount --bind. > > --b. > -- Sev Binello Brookhaven National Laboratory Upton, New York 631-344-5647 sev-IGkKxAqZmp0@public.gmane.org ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that nfs@lists.sourceforge.net is being discontinued. Please subscribe to linux-nfs@vger.kernel.org instead. http://vger.kernel.org/vger-lists.html#linux-nfs ^ permalink raw reply [flat|nested] 23+ messages in thread
[parent not found: <49185984.8010500-IGkKxAqZmp0@public.gmane.org>]
* Re: [NFS] export dir thru 2 diff path names [not found] ` <49185984.8010500-IGkKxAqZmp0@public.gmane.org> @ 2008-11-10 16:49 ` J. Bruce Fields 2008-11-10 17:05 ` Sev Binello 0 siblings, 1 reply; 23+ messages in thread From: J. Bruce Fields @ 2008-11-10 16:49 UTC (permalink / raw) To: Sev Binello; +Cc: nfs On Mon, Nov 10, 2008 at 10:55:48AM -0500, Sev Binello wrote: > Well the simplest approach doesn't work. > i.e put symb link and actual path in the export file & try exporting it > Exportfs dereferences the link and states that duplicates are not allowed. OK, makes sense. You could mount --bind the filesystem at the other location instead of symlinking. The filehandles given to the client will be the same across the two exports. If you mount both from the same client, behavior may vary across different clients (for example, as to whether they attempt to share caches between the two), but I think it'd work. (The question "why??!!??" does come to mind, though.) --b. > > -Sev > > J. Bruce Fields wrote: >> On Fri, Nov 07, 2008 at 12:44:25PM -0500, Sev Binello wrote: >> >>> Can anyone tell me if it's ok to export the same file system >>> through 2 different paths ( one is a link) ? >>> >> >> I actually don't know. You could try it and tell us what you find >> out.... >> >> If you're exporting something *containing* the symlink and expecting the >> client to traverse into the filesystem, be aware that symlinks over NFS >> are actually interpreted (and followed) on the client--so they're >> interpreted as *client-side* paths, not server-side. >> >> If the path you're exporting is itself a symlink--it probably depends on >> how nfs-utils treats symlinks found in /etc/exports. I'd have to try it >> or check the code. >> >> Another way to export the filesystem in two different places would be >> with mount --bind. >> >> --b. >> > > > -- > > Sev Binello > Brookhaven National Laboratory > Upton, New York > 631-344-5647 > sev-IGkKxAqZmp0@public.gmane.org > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that nfs@lists.sourceforge.net is being discontinued. Please subscribe to linux-nfs@vger.kernel.org instead. http://vger.kernel.org/vger-lists.html#linux-nfs ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [NFS] export dir thru 2 diff path names 2008-11-10 16:49 ` J. Bruce Fields @ 2008-11-10 17:05 ` Sev Binello [not found] ` <491869F0.1000505-IGkKxAqZmp0@public.gmane.org> 0 siblings, 1 reply; 23+ messages in thread From: Sev Binello @ 2008-11-10 17:05 UTC (permalink / raw) To: J. Bruce Fields, nfs J. Bruce Fields wrote: > On Mon, Nov 10, 2008 at 10:55:48AM -0500, Sev Binello wrote: > >> Well the simplest approach doesn't work. >> i.e put symb link and actual path in the export file & try exporting it >> Exportfs dereferences the link and states that duplicates are not allowed. >> > > OK, makes sense. > > You could mount --bind the filesystem at the other location instead of > symlinking. > > The filehandles given to the client will be the same across the two > exports. If you mount both from the same client, behavior may vary > across different clients (for example, as to whether they attempt to > share caches between the two), but I think it'd work. > > (The question "why??!!??" does come to mind, though.) > > Need to make a path change to how file systems are mounted and exported on the servers This then required a wholesale change to clients so they mount the correct path. Not an issue for linux. But since we don't administer windows pcs and they also mount the same file system, wanted to see if we could let them stay the way they were for now. We're just going to go ahead and have to coordinate this with windows guys. -Sev > --b. > > >> -Sev >> >> J. Bruce Fields wrote: >> >>> On Fri, Nov 07, 2008 at 12:44:25PM -0500, Sev Binello wrote: >>> >>> >>>> Can anyone tell me if it's ok to export the same file system >>>> through 2 different paths ( one is a link) ? >>>> >>>> >>> I actually don't know. You could try it and tell us what you find >>> out.... >>> >>> If you're exporting something *containing* the symlink and expecting the >>> client to traverse into the filesystem, be aware that symlinks over NFS >>> are actually interpreted (and followed) on the client--so they're >>> interpreted as *client-side* paths, not server-side. >>> >>> If the path you're exporting is itself a symlink--it probably depends on >>> how nfs-utils treats symlinks found in /etc/exports. I'd have to try it >>> or check the code. >>> >>> Another way to export the filesystem in two different places would be >>> with mount --bind. >>> >>> --b. >>> >>> >> -- >> >> Sev Binello >> Brookhaven National Laboratory >> Upton, New York >> 631-344-5647 >> sev-IGkKxAqZmp0@public.gmane.org >> >> ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that nfs@lists.sourceforge.net is being discontinued. Please subscribe to linux-nfs@vger.kernel.org instead. http://vger.kernel.org/vger-lists.html#linux-nfs ^ permalink raw reply [flat|nested] 23+ messages in thread
[parent not found: <491869F0.1000505-IGkKxAqZmp0@public.gmane.org>]
* Re: [NFS] export dir thru 2 diff path names [not found] ` <491869F0.1000505-IGkKxAqZmp0@public.gmane.org> @ 2008-11-10 18:08 ` J. Bruce Fields 2008-11-10 18:11 ` Murata, Dennis 1 sibling, 0 replies; 23+ messages in thread From: J. Bruce Fields @ 2008-11-10 18:08 UTC (permalink / raw) To: Sev Binello; +Cc: nfs On Mon, Nov 10, 2008 at 12:05:52PM -0500, Sev Binello wrote: > J. Bruce Fields wrote: > > OK, makes sense. > > > > You could mount --bind the filesystem at the other location instead of > > symlinking. > > > > The filehandles given to the client will be the same across the two > > exports. If you mount both from the same client, behavior may vary > > across different clients (for example, as to whether they attempt to > > share caches between the two), but I think it'd work. > > > > (The question "why??!!??" does come to mind, though.) > > > > > Need to make a path change to how file systems are mounted and exported > on the servers > This then required a wholesale change to clients so they mount the > correct path. > Not an issue for linux. > But since we don't administer windows pcs and they also mount the same > file system, > wanted to see if we could let them stay the way they were for now. Oh, OK, so you just to export at both paths just as a way to do a gradual migration of clients from one to the other. Fine. --b. > > We're just going to go ahead and have to coordinate this with windows guys. > > -Sev > > --b. > > > > > >> -Sev > >> > >> J. Bruce Fields wrote: > >> > >>> On Fri, Nov 07, 2008 at 12:44:25PM -0500, Sev Binello wrote: > >>> > >>> > >>>> Can anyone tell me if it's ok to export the same file system > >>>> through 2 different paths ( one is a link) ? > >>>> > >>>> > >>> I actually don't know. You could try it and tell us what you find > >>> out.... > >>> > >>> If you're exporting something *containing* the symlink and expecting the > >>> client to traverse into the filesystem, be aware that symlinks over NFS > >>> are actually interpreted (and followed) on the client--so they're > >>> interpreted as *client-side* paths, not server-side. > >>> > >>> If the path you're exporting is itself a symlink--it probably depends on > >>> how nfs-utils treats symlinks found in /etc/exports. I'd have to try it > >>> or check the code. > >>> > >>> Another way to export the filesystem in two different places would be > >>> with mount --bind. > >>> > >>> --b. > >>> > >>> > >> -- > >> > >> Sev Binello > >> Brookhaven National Laboratory > >> Upton, New York > >> 631-344-5647 > >> sev-IGkKxAqZmp0@public.gmane.org > >> > >> > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > NFS maillist - NFS@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nfs > _______________________________________________ > Please note that nfs@lists.sourceforge.net is being discontinued. > Please subscribe to linux-nfs@vger.kernel.org instead. > http://vger.kernel.org/vger-lists.html#linux-nfs > > -- > To unsubscribe from this list: send the line "unsubscribe linux-nfs" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that nfs@lists.sourceforge.net is being discontinued. Please subscribe to linux-nfs@vger.kernel.org instead. http://vger.kernel.org/vger-lists.html#linux-nfs ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [NFS] export dir thru 2 diff path names [not found] ` <491869F0.1000505-IGkKxAqZmp0@public.gmane.org> 2008-11-10 18:08 ` J. Bruce Fields @ 2008-11-10 18:11 ` Murata, Dennis [not found] ` <620E93B2E5CC3B46BD811165E3335B8702F374A0-9/h0XwadXgnyjpQT3Si/rsM9+qvyE0V4QQ4Iyu8u01E@public.gmane.org> 1 sibling, 1 reply; 23+ messages in thread From: Murata, Dennis @ 2008-11-10 18:11 UTC (permalink / raw) To: Sev Binello, J. Bruce Fields, nfs I just tested this on a SL4.7 (RHEL 4.7 variant) using a RHEL 4.4 nfs server. I did get the messages from exportfs about duplicate export entries. On the client I was able to mount both the symlink and the actual directory. They look like separate mounts. There are two entries in /proc/mounts and in /etc/mtab, one with the actual directory path, one with the symlink path. I am using autofs to mount the directories, not hardcoded. Are you using newer distributions? What problems will I cause by doing this? I am using the symlink path as the installation path for an application. The idea is a newer version can be installed into a different directory, then after testing the symlink will be changed to the new installation. Other applications that reference the application will always use the symlink path, as well as any user scripts. Wayne > -----Original Message----- > From: linux-nfs-owner@vger.kernel.org > [mailto:linux-nfs-owner@vger.kernel.org] On Behalf Of Sev Binello > Sent: Monday, November 10, 2008 11:06 AM > To: J. Bruce Fields; nfs@lists.sourceforge.net > Subject: Re: [NFS] export dir thru 2 diff path names > > J. Bruce Fields wrote: > > On Mon, Nov 10, 2008 at 10:55:48AM -0500, Sev Binello wrote: > > > >> Well the simplest approach doesn't work. > >> i.e put symb link and actual path in the export file & try > exporting > >> it Exportfs dereferences the link and states that > duplicates are not allowed. > >> > > > > OK, makes sense. > > > > You could mount --bind the filesystem at the other location > instead of > > symlinking. > > > > The filehandles given to the client will be the same across the two > > exports. If you mount both from the same client, behavior may vary > > across different clients (for example, as to whether they > attempt to > > share caches between the two), but I think it'd work. > > > > (The question "why??!!??" does come to mind, though.) > > > > > Need to make a path change to how file systems are mounted > and exported on the servers This then required a wholesale > change to clients so they mount the correct path. > Not an issue for linux. > But since we don't administer windows pcs and they also mount > the same file system, wanted to see if we could let them stay > the way they were for now. > > We're just going to go ahead and have to coordinate this > with windows guys. > > -Sev > > --b. > > > > > >> -Sev > >> > >> J. Bruce Fields wrote: > >> > >>> On Fri, Nov 07, 2008 at 12:44:25PM -0500, Sev Binello wrote: > >>> > >>> > >>>> Can anyone tell me if it's ok to export the same file system > >>>> through 2 different paths ( one is a link) ? > >>>> > >>>> > >>> I actually don't know. You could try it and tell us what > you find > >>> out.... > >>> > >>> If you're exporting something *containing* the symlink > and expecting > >>> the client to traverse into the filesystem, be aware that > symlinks > >>> over NFS are actually interpreted (and followed) on the > client--so > >>> they're interpreted as *client-side* paths, not server-side. > >>> > >>> If the path you're exporting is itself a symlink--it probably > >>> depends on how nfs-utils treats symlinks found in > /etc/exports. I'd > >>> have to try it or check the code. > >>> > >>> Another way to export the filesystem in two different > places would > >>> be with mount --bind. > >>> > >>> --b. > >>> > >>> > >> -- > >> > >> Sev Binello > >> Brookhaven National Laboratory > >> Upton, New York > >> 631-344-5647 > >> sev-IGkKxAqZmp0@public.gmane.org > >> > >> > > > -------------------------------------------------------------- > ----------- > This SF.Net email is sponsored by the Moblin Your Move > Developer's challenge Build the coolest Linux based > applications with Moblin SDK & win great prizes Grand prize > is a trip for two to an Open Source event anywhere in the > world http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > NFS maillist - NFS@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nfs > _______________________________________________ > Please note that nfs@lists.sourceforge.net is being discontinued. > Please subscribe to linux-nfs@vger.kernel.org instead. > http://vger.kernel.org/vger-lists.html#linux-nfs > > -- > To unsubscribe from this list: send the line "unsubscribe > linux-nfs" in the body of a message to > majordomo@vger.kernel.org More majordomo info at > http://vger.kernel.org/majordomo-info.html > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that nfs@lists.sourceforge.net is being discontinued. Please subscribe to linux-nfs@vger.kernel.org instead. http://vger.kernel.org/vger-lists.html#linux-nfs ^ permalink raw reply [flat|nested] 23+ messages in thread
[parent not found: <620E93B2E5CC3B46BD811165E3335B8702F374A0-9/h0XwadXgnyjpQT3Si/rsM9+qvyE0V4QQ4Iyu8u01E@public.gmane.org>]
* Re: [NFS] export dir thru 2 diff path names [not found] ` <620E93B2E5CC3B46BD811165E3335B8702F374A0-9/h0XwadXgnyjpQT3Si/rsM9+qvyE0V4QQ4Iyu8u01E@public.gmane.org> @ 2008-11-10 18:51 ` Sev Binello [not found] ` <491882AB.6070908-IGkKxAqZmp0@public.gmane.org> 0 siblings, 1 reply; 23+ messages in thread From: Sev Binello @ 2008-11-10 18:51 UTC (permalink / raw) To: Murata, Dennis; +Cc: J. Bruce Fields, nfs Murata, Dennis wrote: > I just tested this on a SL4.7 (RHEL 4.7 variant) using a RHEL 4.4 nfs > server. I did get the messages from exportfs about duplicate export > entries. On the client I was able to mount both the symlink and the > actual directory. They look like separate mounts. There are two > entries in /proc/mounts and in /etc/mtab, one with the actual directory > path, one with the symlink path. I am using autofs to mount the > directories, not hardcoded. Are you using newer distributions? > I tested on RHEL 4.6. Interesting that you can still mount either one. On the server an exportfs only shows the real path as exported. > What problems will I cause by doing this? I am using the symlink path > as the installation path for an application. The idea is a newer > version can be installed into a different directory, then after testing > the symlink will be changed to the new installation. Other applications > that reference the application will always use the symlink path, as well > as any user scripts. > > Wayne > > >> -----Original Message----- >> From: linux-nfs-owner@vger.kernel.org >> [mailto:linux-nfs-owner@vger.kernel.org] On Behalf Of Sev Binello >> Sent: Monday, November 10, 2008 11:06 AM >> To: J. Bruce Fields; nfs@lists.sourceforge.net >> Subject: Re: [NFS] export dir thru 2 diff path names >> >> J. Bruce Fields wrote: >> >>> On Mon, Nov 10, 2008 at 10:55:48AM -0500, Sev Binello wrote: >>> >>> >>>> Well the simplest approach doesn't work. >>>> i.e put symb link and actual path in the export file & try >>>> >> exporting >> >>>> it Exportfs dereferences the link and states that >>>> >> duplicates are not allowed. >> >>>> >>>> >>> OK, makes sense. >>> >>> You could mount --bind the filesystem at the other location >>> >> instead of >> >>> symlinking. >>> >>> The filehandles given to the client will be the same across the two >>> exports. If you mount both from the same client, behavior may vary >>> across different clients (for example, as to whether they >>> >> attempt to >> >>> share caches between the two), but I think it'd work. >>> >>> (The question "why??!!??" does come to mind, though.) >>> >>> >>> >> Need to make a path change to how file systems are mounted >> and exported on the servers This then required a wholesale >> change to clients so they mount the correct path. >> Not an issue for linux. >> But since we don't administer windows pcs and they also mount >> the same file system, wanted to see if we could let them stay >> the way they were for now. >> >> We're just going to go ahead and have to coordinate this >> with windows guys. >> >> -Sev >> >>> --b. >>> >>> >>> >>>> -Sev >>>> >>>> J. Bruce Fields wrote: >>>> >>>> >>>>> On Fri, Nov 07, 2008 at 12:44:25PM -0500, Sev Binello wrote: >>>>> >>>>> >>>>> >>>>>> Can anyone tell me if it's ok to export the same file system >>>>>> through 2 different paths ( one is a link) ? >>>>>> >>>>>> >>>>>> >>>>> I actually don't know. You could try it and tell us what >>>>> >> you find >> >>>>> out.... >>>>> >>>>> If you're exporting something *containing* the symlink >>>>> >> and expecting >> >>>>> the client to traverse into the filesystem, be aware that >>>>> >> symlinks >> >>>>> over NFS are actually interpreted (and followed) on the >>>>> >> client--so >> >>>>> they're interpreted as *client-side* paths, not server-side. >>>>> >>>>> If the path you're exporting is itself a symlink--it probably >>>>> depends on how nfs-utils treats symlinks found in >>>>> >> /etc/exports. I'd >> >>>>> have to try it or check the code. >>>>> >>>>> Another way to export the filesystem in two different >>>>> >> places would >> >>>>> be with mount --bind. >>>>> >>>>> --b. >>>>> >>>>> >>>>> >>>> -- >>>> >>>> Sev Binello >>>> Brookhaven National Laboratory >>>> Upton, New York >>>> 631-344-5647 >>>> sev-IGkKxAqZmp0@public.gmane.org >>>> >>>> >>>> >> -------------------------------------------------------------- >> ----------- >> This SF.Net email is sponsored by the Moblin Your Move >> Developer's challenge Build the coolest Linux based >> applications with Moblin SDK & win great prizes Grand prize >> is a trip for two to an Open Source event anywhere in the >> world http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> NFS maillist - NFS@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/nfs >> _______________________________________________ >> Please note that nfs@lists.sourceforge.net is being discontinued. >> Please subscribe to linux-nfs@vger.kernel.org instead. >> http://vger.kernel.org/vger-lists.html#linux-nfs >> >> -- >> To unsubscribe from this list: send the line "unsubscribe >> linux-nfs" in the body of a message to >> majordomo@vger.kernel.org More majordomo info at >> http://vger.kernel.org/majordomo-info.html >> >> -- Sev Binello Brookhaven National Laboratory Upton, New York 631-344-5647 sev-IGkKxAqZmp0@public.gmane.org ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that nfs@lists.sourceforge.net is being discontinued. Please subscribe to linux-nfs@vger.kernel.org instead. http://vger.kernel.org/vger-lists.html#linux-nfs ^ permalink raw reply [flat|nested] 23+ messages in thread
[parent not found: <491882AB.6070908-IGkKxAqZmp0@public.gmane.org>]
* Re: [NFS] export dir thru 2 diff path names [not found] ` <491882AB.6070908-IGkKxAqZmp0@public.gmane.org> @ 2008-11-10 18:58 ` Murata, Dennis [not found] ` <620E93B2E5CC3B46BD811165E3335B8702F37542-9/h0XwadXgnyjpQT3Si/rsM9+qvyE0V4QQ4Iyu8u01E@public.gmane.org> 0 siblings, 1 reply; 23+ messages in thread From: Murata, Dennis @ 2008-11-10 18:58 UTC (permalink / raw) To: Sev Binello; +Cc: J. Bruce Fields, nfs That is correct, exportfs only shows the actual directory. The client seems to be able to mount the directory with either. Wayne > -----Original Message----- > From: Sev Binello [mailto:sev-IGkKxAqZmp0@public.gmane.org] > Sent: Monday, November 10, 2008 12:51 PM > To: Murata, Dennis > Cc: J. Bruce Fields; nfs@lists.sourceforge.net > Subject: Re: [NFS] export dir thru 2 diff path names > > Murata, Dennis wrote: > > I just tested this on a SL4.7 (RHEL 4.7 variant) using a > RHEL 4.4 nfs > > server. I did get the messages from exportfs about > duplicate export > > entries. On the client I was able to mount both the > symlink and the > > actual directory. They look like separate mounts. There are two > > entries in /proc/mounts and in /etc/mtab, one with the actual > > directory path, one with the symlink path. I am using > autofs to mount > > the directories, not hardcoded. Are you using newer distributions? > > > I tested on RHEL 4.6. > Interesting that you can still mount either one. > On the server an exportfs only shows the real path as exported. > > > What problems will I cause by doing this? I am using the > symlink path > > as the installation path for an application. The idea is a newer > > version can be installed into a different directory, then after > > testing the symlink will be changed to the new installation. Other > > applications that reference the application will always use the > > symlink path, as well as any user scripts. > > > > Wayne > > > > > >> -----Original Message----- > >> From: linux-nfs-owner@vger.kernel.org > >> [mailto:linux-nfs-owner@vger.kernel.org] On Behalf Of Sev Binello > >> Sent: Monday, November 10, 2008 11:06 AM > >> To: J. Bruce Fields; nfs@lists.sourceforge.net > >> Subject: Re: [NFS] export dir thru 2 diff path names > >> > >> J. Bruce Fields wrote: > >> > >>> On Mon, Nov 10, 2008 at 10:55:48AM -0500, Sev Binello wrote: > >>> > >>> > >>>> Well the simplest approach doesn't work. > >>>> i.e put symb link and actual path in the export file & try > >>>> > >> exporting > >> > >>>> it Exportfs dereferences the link and states that > >>>> > >> duplicates are not allowed. > >> > >>>> > >>>> > >>> OK, makes sense. > >>> > >>> You could mount --bind the filesystem at the other location > >>> > >> instead of > >> > >>> symlinking. > >>> > >>> The filehandles given to the client will be the same > across the two > >>> exports. If you mount both from the same client, > behavior may vary > >>> across different clients (for example, as to whether they > >>> > >> attempt to > >> > >>> share caches between the two), but I think it'd work. > >>> > >>> (The question "why??!!??" does come to mind, though.) > >>> > >>> > >>> > >> Need to make a path change to how file systems are mounted and > >> exported on the servers This then required a wholesale change to > >> clients so they mount the correct path. > >> Not an issue for linux. > >> But since we don't administer windows pcs and they also mount the > >> same file system, wanted to see if we could let them stay the way > >> they were for now. > >> > >> We're just going to go ahead and have to coordinate this with > >> windows guys. > >> > >> -Sev > >> > >>> --b. > >>> > >>> > >>> > >>>> -Sev > >>>> > >>>> J. Bruce Fields wrote: > >>>> > >>>> > >>>>> On Fri, Nov 07, 2008 at 12:44:25PM -0500, Sev Binello wrote: > >>>>> > >>>>> > >>>>> > >>>>>> Can anyone tell me if it's ok to export the same file system > >>>>>> through 2 different paths ( one is a link) ? > >>>>>> > >>>>>> > >>>>>> > >>>>> I actually don't know. You could try it and tell us what > >>>>> > >> you find > >> > >>>>> out.... > >>>>> > >>>>> If you're exporting something *containing* the symlink > >>>>> > >> and expecting > >> > >>>>> the client to traverse into the filesystem, be aware that > >>>>> > >> symlinks > >> > >>>>> over NFS are actually interpreted (and followed) on the > >>>>> > >> client--so > >> > >>>>> they're interpreted as *client-side* paths, not server-side. > >>>>> > >>>>> If the path you're exporting is itself a symlink--it probably > >>>>> depends on how nfs-utils treats symlinks found in > >>>>> > >> /etc/exports. I'd > >> > >>>>> have to try it or check the code. > >>>>> > >>>>> Another way to export the filesystem in two different > >>>>> > >> places would > >> > >>>>> be with mount --bind. > >>>>> > >>>>> --b. > >>>>> > >>>>> > >>>>> > >>>> -- > >>>> > >>>> Sev Binello > >>>> Brookhaven National Laboratory > >>>> Upton, New York > >>>> 631-344-5647 > >>>> sev-IGkKxAqZmp0@public.gmane.org > >>>> > >>>> > >>>> > >> -------------------------------------------------------------- > >> ----------- > >> This SF.Net email is sponsored by the Moblin Your Move Developer's > >> challenge Build the coolest Linux based applications with > Moblin SDK > >> & win great prizes Grand prize is a trip for two to an Open Source > >> event anywhere in the world > >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ > >> _______________________________________________ > >> NFS maillist - NFS@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/nfs > >> _______________________________________________ > >> Please note that nfs@lists.sourceforge.net is being discontinued. > >> Please subscribe to linux-nfs@vger.kernel.org instead. > >> http://vger.kernel.org/vger-lists.html#linux-nfs > >> > >> -- > >> To unsubscribe from this list: send the line "unsubscribe > linux-nfs" > >> in the body of a message to majordomo@vger.kernel.org More > majordomo > >> info at http://vger.kernel.org/majordomo-info.html > >> > >> > > > -- > > Sev Binello > Brookhaven National Laboratory > Upton, New York > 631-344-5647 > sev-IGkKxAqZmp0@public.gmane.org > > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that nfs@lists.sourceforge.net is being discontinued. Please subscribe to linux-nfs@vger.kernel.org instead. http://vger.kernel.org/vger-lists.html#linux-nfs ^ permalink raw reply [flat|nested] 23+ messages in thread
[parent not found: <620E93B2E5CC3B46BD811165E3335B8702F37542-9/h0XwadXgnyjpQT3Si/rsM9+qvyE0V4QQ4Iyu8u01E@public.gmane.org>]
* Re: [NFS] export dir thru 2 diff path names [not found] ` <620E93B2E5CC3B46BD811165E3335B8702F37542-9/h0XwadXgnyjpQT3Si/rsM9+qvyE0V4QQ4Iyu8u01E@public.gmane.org> @ 2008-11-10 19:03 ` Sev Binello [not found] ` <4918859C.6080608-IGkKxAqZmp0@public.gmane.org> 0 siblings, 1 reply; 23+ messages in thread From: Sev Binello @ 2008-11-10 19:03 UTC (permalink / raw) To: Murata, Dennis; +Cc: J. Bruce Fields, nfs Hi - Yeah, I see. So it actually looks like you can do this. I'm not 100% sure if safe --though it looks it -- so I'll probably not use it for this application. Thanks -Sev Murata, Dennis wrote: > That is correct, exportfs only shows the actual directory. The client > seems to be able to mount the directory with either. > > Wayne > > >> -----Original Message----- >> From: Sev Binello [mailto:sev-IGkKxAqZmp0@public.gmane.org] >> Sent: Monday, November 10, 2008 12:51 PM >> To: Murata, Dennis >> Cc: J. Bruce Fields; nfs@lists.sourceforge.net >> Subject: Re: [NFS] export dir thru 2 diff path names >> >> Murata, Dennis wrote: >> >>> I just tested this on a SL4.7 (RHEL 4.7 variant) using a >>> >> RHEL 4.4 nfs >> >>> server. I did get the messages from exportfs about >>> >> duplicate export >> >>> entries. On the client I was able to mount both the >>> >> symlink and the >> >>> actual directory. They look like separate mounts. There are two >>> entries in /proc/mounts and in /etc/mtab, one with the actual >>> directory path, one with the symlink path. I am using >>> >> autofs to mount >> >>> the directories, not hardcoded. Are you using newer distributions? >>> >>> >> I tested on RHEL 4.6. >> Interesting that you can still mount either one. >> On the server an exportfs only shows the real path as exported. >> >> >>> What problems will I cause by doing this? I am using the >>> >> symlink path >> >>> as the installation path for an application. The idea is a newer >>> version can be installed into a different directory, then after >>> testing the symlink will be changed to the new installation. Other >>> applications that reference the application will always use the >>> symlink path, as well as any user scripts. >>> >>> Wayne >>> >>> >>> >>>> -----Original Message----- >>>> From: linux-nfs-owner@vger.kernel.org >>>> [mailto:linux-nfs-owner@vger.kernel.org] On Behalf Of Sev Binello >>>> Sent: Monday, November 10, 2008 11:06 AM >>>> To: J. Bruce Fields; nfs@lists.sourceforge.net >>>> Subject: Re: [NFS] export dir thru 2 diff path names >>>> >>>> J. Bruce Fields wrote: >>>> >>>> >>>>> On Mon, Nov 10, 2008 at 10:55:48AM -0500, Sev Binello wrote: >>>>> >>>>> >>>>> >>>>>> Well the simplest approach doesn't work. >>>>>> i.e put symb link and actual path in the export file & try >>>>>> >>>>>> >>>> exporting >>>> >>>> >>>>>> it Exportfs dereferences the link and states that >>>>>> >>>>>> >>>> duplicates are not allowed. >>>> >>>> >>>>>> >>>>>> >>>>>> >>>>> OK, makes sense. >>>>> >>>>> You could mount --bind the filesystem at the other location >>>>> >>>>> >>>> instead of >>>> >>>> >>>>> symlinking. >>>>> >>>>> The filehandles given to the client will be the same >>>>> >> across the two >> >>>>> exports. If you mount both from the same client, >>>>> >> behavior may vary >> >>>>> across different clients (for example, as to whether they >>>>> >>>>> >>>> attempt to >>>> >>>> >>>>> share caches between the two), but I think it'd work. >>>>> >>>>> (The question "why??!!??" does come to mind, though.) >>>>> >>>>> >>>>> >>>>> >>>> Need to make a path change to how file systems are mounted and >>>> exported on the servers This then required a wholesale change to >>>> clients so they mount the correct path. >>>> Not an issue for linux. >>>> But since we don't administer windows pcs and they also mount the >>>> same file system, wanted to see if we could let them stay the way >>>> they were for now. >>>> >>>> We're just going to go ahead and have to coordinate this with >>>> windows guys. >>>> >>>> -Sev >>>> >>>> >>>>> --b. >>>>> >>>>> >>>>> >>>>> >>>>>> -Sev >>>>>> >>>>>> J. Bruce Fields wrote: >>>>>> >>>>>> >>>>>> >>>>>>> On Fri, Nov 07, 2008 at 12:44:25PM -0500, Sev Binello wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>> Can anyone tell me if it's ok to export the same file system >>>>>>>> through 2 different paths ( one is a link) ? >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> I actually don't know. You could try it and tell us what >>>>>>> >>>>>>> >>>> you find >>>> >>>> >>>>>>> out.... >>>>>>> >>>>>>> If you're exporting something *containing* the symlink >>>>>>> >>>>>>> >>>> and expecting >>>> >>>> >>>>>>> the client to traverse into the filesystem, be aware that >>>>>>> >>>>>>> >>>> symlinks >>>> >>>> >>>>>>> over NFS are actually interpreted (and followed) on the >>>>>>> >>>>>>> >>>> client--so >>>> >>>> >>>>>>> they're interpreted as *client-side* paths, not server-side. >>>>>>> >>>>>>> If the path you're exporting is itself a symlink--it probably >>>>>>> depends on how nfs-utils treats symlinks found in >>>>>>> >>>>>>> >>>> /etc/exports. I'd >>>> >>>> >>>>>>> have to try it or check the code. >>>>>>> >>>>>>> Another way to export the filesystem in two different >>>>>>> >>>>>>> >>>> places would >>>> >>>> >>>>>>> be with mount --bind. >>>>>>> >>>>>>> --b. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> -- >>>>>> >>>>>> Sev Binello >>>>>> Brookhaven National Laboratory >>>>>> Upton, New York >>>>>> 631-344-5647 >>>>>> sev-IGkKxAqZmp0@public.gmane.org >>>>>> >>>>>> >>>>>> >>>>>> >>>> -------------------------------------------------------------- >>>> ----------- >>>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>>> challenge Build the coolest Linux based applications with >>>> >> Moblin SDK >> >>>> & win great prizes Grand prize is a trip for two to an Open Source >>>> event anywhere in the world >>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>>> _______________________________________________ >>>> NFS maillist - NFS@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/nfs >>>> _______________________________________________ >>>> Please note that nfs@lists.sourceforge.net is being discontinued. >>>> Please subscribe to linux-nfs@vger.kernel.org instead. >>>> http://vger.kernel.org/vger-lists.html#linux-nfs >>>> >>>> -- >>>> To unsubscribe from this list: send the line "unsubscribe >>>> >> linux-nfs" >> >>>> in the body of a message to majordomo@vger.kernel.org More >>>> >> majordomo >> >>>> info at http://vger.kernel.org/majordomo-info.html >>>> >>>> >>>> >> -- >> >> Sev Binello >> Brookhaven National Laboratory >> Upton, New York >> 631-344-5647 >> sev-IGkKxAqZmp0@public.gmane.org >> >> >> ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that nfs@lists.sourceforge.net is being discontinued. Please subscribe to linux-nfs@vger.kernel.org instead. http://vger.kernel.org/vger-lists.html#linux-nfs ^ permalink raw reply [flat|nested] 23+ messages in thread
[parent not found: <4918859C.6080608-IGkKxAqZmp0@public.gmane.org>]
* Re: [NFS] export dir thru 2 diff path names [not found] ` <4918859C.6080608-IGkKxAqZmp0@public.gmane.org> @ 2008-11-10 19:28 ` Murata, Dennis [not found] ` <620E93B2E5CC3B46BD811165E3335B8702F3759D-9/h0XwadXgnyjpQT3Si/rsM9+qvyE0V4QQ4Iyu8u01E@public.gmane.org> 0 siblings, 1 reply; 23+ messages in thread From: Murata, Dennis @ 2008-11-10 19:28 UTC (permalink / raw) To: Sev Binello; +Cc: J. Bruce Fields, nfs That really is the 64K question. During my initial testing, I exported the parent directory. Now I am explicitly exporting the installation directories, where I see the exportfs message. In the messages log file on the server the mount request from the client is always the actual directory. Wayne > -----Original Message----- > From: Sev Binello [mailto:sev-IGkKxAqZmp0@public.gmane.org] > Sent: Monday, November 10, 2008 1:04 PM > To: Murata, Dennis > Cc: J. Bruce Fields; nfs@lists.sourceforge.net > Subject: Re: [NFS] export dir thru 2 diff path names > > Hi - > Yeah, I see. > So it actually looks like you can do this. > I'm not 100% sure if safe --though it looks it -- so I'll > probably not use it for this application. > > Thanks > -Sev > > Murata, Dennis wrote: > > That is correct, exportfs only shows the actual directory. > The client > > seems to be able to mount the directory with either. > > > > Wayne > > > > > >> -----Original Message----- > >> From: Sev Binello [mailto:sev-IGkKxAqZmp0@public.gmane.org] > >> Sent: Monday, November 10, 2008 12:51 PM > >> To: Murata, Dennis > >> Cc: J. Bruce Fields; nfs@lists.sourceforge.net > >> Subject: Re: [NFS] export dir thru 2 diff path names > >> > >> Murata, Dennis wrote: > >> > >>> I just tested this on a SL4.7 (RHEL 4.7 variant) using a > >>> > >> RHEL 4.4 nfs > >> > >>> server. I did get the messages from exportfs about > >>> > >> duplicate export > >> > >>> entries. On the client I was able to mount both the > >>> > >> symlink and the > >> > >>> actual directory. They look like separate mounts. There are two > >>> entries in /proc/mounts and in /etc/mtab, one with the actual > >>> directory path, one with the symlink path. I am using > >>> > >> autofs to mount > >> > >>> the directories, not hardcoded. Are you using newer > distributions? > >>> > >>> > >> I tested on RHEL 4.6. > >> Interesting that you can still mount either one. > >> On the server an exportfs only shows the real path as exported. > >> > >> > >>> What problems will I cause by doing this? I am using the > >>> > >> symlink path > >> > >>> as the installation path for an application. The idea is a newer > >>> version can be installed into a different directory, then after > >>> testing the symlink will be changed to the new > installation. Other > >>> applications that reference the application will always use the > >>> symlink path, as well as any user scripts. > >>> > >>> Wayne > >>> > >>> > >>> > >>>> -----Original Message----- > >>>> From: linux-nfs-owner@vger.kernel.org > >>>> [mailto:linux-nfs-owner@vger.kernel.org] On Behalf Of Sev Binello > >>>> Sent: Monday, November 10, 2008 11:06 AM > >>>> To: J. Bruce Fields; nfs@lists.sourceforge.net > >>>> Subject: Re: [NFS] export dir thru 2 diff path names > >>>> > >>>> J. Bruce Fields wrote: > >>>> > >>>> > >>>>> On Mon, Nov 10, 2008 at 10:55:48AM -0500, Sev Binello wrote: > >>>>> > >>>>> > >>>>> > >>>>>> Well the simplest approach doesn't work. > >>>>>> i.e put symb link and actual path in the export file & try > >>>>>> > >>>>>> > >>>> exporting > >>>> > >>>> > >>>>>> it Exportfs dereferences the link and states that > >>>>>> > >>>>>> > >>>> duplicates are not allowed. > >>>> > >>>> > >>>>>> > >>>>>> > >>>>>> > >>>>> OK, makes sense. > >>>>> > >>>>> You could mount --bind the filesystem at the other location > >>>>> > >>>>> > >>>> instead of > >>>> > >>>> > >>>>> symlinking. > >>>>> > >>>>> The filehandles given to the client will be the same > >>>>> > >> across the two > >> > >>>>> exports. If you mount both from the same client, > >>>>> > >> behavior may vary > >> > >>>>> across different clients (for example, as to whether they > >>>>> > >>>>> > >>>> attempt to > >>>> > >>>> > >>>>> share caches between the two), but I think it'd work. > >>>>> > >>>>> (The question "why??!!??" does come to mind, though.) > >>>>> > >>>>> > >>>>> > >>>>> > >>>> Need to make a path change to how file systems are mounted and > >>>> exported on the servers This then required a wholesale change to > >>>> clients so they mount the correct path. > >>>> Not an issue for linux. > >>>> But since we don't administer windows pcs and they also > mount the > >>>> same file system, wanted to see if we could let them > stay the way > >>>> they were for now. > >>>> > >>>> We're just going to go ahead and have to coordinate this with > >>>> windows guys. > >>>> > >>>> -Sev > >>>> > >>>> > >>>>> --b. > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>> -Sev > >>>>>> > >>>>>> J. Bruce Fields wrote: > >>>>>> > >>>>>> > >>>>>> > >>>>>>> On Fri, Nov 07, 2008 at 12:44:25PM -0500, Sev Binello wrote: > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>>> Can anyone tell me if it's ok to export the same file system > >>>>>>>> through 2 different paths ( one is a link) ? > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>> I actually don't know. You could try it and tell us what > >>>>>>> > >>>>>>> > >>>> you find > >>>> > >>>> > >>>>>>> out.... > >>>>>>> > >>>>>>> If you're exporting something *containing* the symlink > >>>>>>> > >>>>>>> > >>>> and expecting > >>>> > >>>> > >>>>>>> the client to traverse into the filesystem, be aware that > >>>>>>> > >>>>>>> > >>>> symlinks > >>>> > >>>> > >>>>>>> over NFS are actually interpreted (and followed) on the > >>>>>>> > >>>>>>> > >>>> client--so > >>>> > >>>> > >>>>>>> they're interpreted as *client-side* paths, not server-side. > >>>>>>> > >>>>>>> If the path you're exporting is itself a symlink--it probably > >>>>>>> depends on how nfs-utils treats symlinks found in > >>>>>>> > >>>>>>> > >>>> /etc/exports. I'd > >>>> > >>>> > >>>>>>> have to try it or check the code. > >>>>>>> > >>>>>>> Another way to export the filesystem in two different > >>>>>>> > >>>>>>> > >>>> places would > >>>> > >>>> > >>>>>>> be with mount --bind. > >>>>>>> > >>>>>>> --b. > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>> -- > >>>>>> > >>>>>> Sev Binello > >>>>>> Brookhaven National Laboratory > >>>>>> Upton, New York > >>>>>> 631-344-5647 > >>>>>> sev-IGkKxAqZmp0@public.gmane.org > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>> -------------------------------------------------------------- > >>>> ----------- > >>>> This SF.Net email is sponsored by the Moblin Your Move > Developer's > >>>> challenge Build the coolest Linux based applications with > >>>> > >> Moblin SDK > >> > >>>> & win great prizes Grand prize is a trip for two to an > Open Source > >>>> event anywhere in the world > >>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ > >>>> _______________________________________________ > >>>> NFS maillist - NFS@lists.sourceforge.net > >>>> https://lists.sourceforge.net/lists/listinfo/nfs > >>>> _______________________________________________ > >>>> Please note that nfs@lists.sourceforge.net is being discontinued. > >>>> Please subscribe to linux-nfs@vger.kernel.org instead. > >>>> http://vger.kernel.org/vger-lists.html#linux-nfs > >>>> > >>>> -- > >>>> To unsubscribe from this list: send the line "unsubscribe > >>>> > >> linux-nfs" > >> > >>>> in the body of a message to majordomo@vger.kernel.org More > >>>> > >> majordomo > >> > >>>> info at http://vger.kernel.org/majordomo-info.html > >>>> > >>>> > >>>> > >> -- > >> > >> Sev Binello > >> Brookhaven National Laboratory > >> Upton, New York > >> 631-344-5647 > >> sev-IGkKxAqZmp0@public.gmane.org > >> > >> > >> > > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that nfs@lists.sourceforge.net is being discontinued. Please subscribe to linux-nfs@vger.kernel.org instead. http://vger.kernel.org/vger-lists.html#linux-nfs ^ permalink raw reply [flat|nested] 23+ messages in thread
[parent not found: <620E93B2E5CC3B46BD811165E3335B8702F3759D-9/h0XwadXgnyjpQT3Si/rsM9+qvyE0V4QQ4Iyu8u01E@public.gmane.org>]
* Re: [NFS] export dir thru 2 diff path names [not found] ` <620E93B2E5CC3B46BD811165E3335B8702F3759D-9/h0XwadXgnyjpQT3Si/rsM9+qvyE0V4QQ4Iyu8u01E@public.gmane.org> @ 2008-11-10 19:28 ` J. Bruce Fields 2008-11-10 19:36 ` Sev Binello 2008-11-10 20:20 ` Chuck Lever 0 siblings, 2 replies; 23+ messages in thread From: J. Bruce Fields @ 2008-11-10 19:28 UTC (permalink / raw) To: Murata, Dennis; +Cc: nfs, Sev Binello On Mon, Nov 10, 2008 at 11:28:04AM -0800, Murata, Dennis wrote: > That really is the 64K question. During my initial testing, I exported > the parent directory. Now I am explicitly exporting the installation > directories, where I see the exportfs message. In the messages log file > on the server the mount request from the client is always the actual > directory. I don't see how this would be "unsafe"--if it works, go for it. One potential trap: it's using the same client list and export options for both, so if you think you can make one of them read-only and one of them writeable, for example, you'll be disapointed. --b. > > Wayne > > > -----Original Message----- > > From: Sev Binello [mailto:sev-IGkKxAqZmp0@public.gmane.org] > > Sent: Monday, November 10, 2008 1:04 PM > > To: Murata, Dennis > > Cc: J. Bruce Fields; nfs@lists.sourceforge.net > > Subject: Re: [NFS] export dir thru 2 diff path names > > > > Hi - > > Yeah, I see. > > So it actually looks like you can do this. > > I'm not 100% sure if safe --though it looks it -- so I'll > > probably not use it for this application. > > > > Thanks > > -Sev > > > > Murata, Dennis wrote: > > > That is correct, exportfs only shows the actual directory. > > The client > > > seems to be able to mount the directory with either. > > > > > > Wayne > > > > > > > > >> -----Original Message----- > > >> From: Sev Binello [mailto:sev-IGkKxAqZmp0@public.gmane.org] > > >> Sent: Monday, November 10, 2008 12:51 PM > > >> To: Murata, Dennis > > >> Cc: J. Bruce Fields; nfs@lists.sourceforge.net > > >> Subject: Re: [NFS] export dir thru 2 diff path names > > >> > > >> Murata, Dennis wrote: > > >> > > >>> I just tested this on a SL4.7 (RHEL 4.7 variant) using a > > >>> > > >> RHEL 4.4 nfs > > >> > > >>> server. I did get the messages from exportfs about > > >>> > > >> duplicate export > > >> > > >>> entries. On the client I was able to mount both the > > >>> > > >> symlink and the > > >> > > >>> actual directory. They look like separate mounts. There are two > > >>> entries in /proc/mounts and in /etc/mtab, one with the actual > > >>> directory path, one with the symlink path. I am using > > >>> > > >> autofs to mount > > >> > > >>> the directories, not hardcoded. Are you using newer > > distributions? > > >>> > > >>> > > >> I tested on RHEL 4.6. > > >> Interesting that you can still mount either one. > > >> On the server an exportfs only shows the real path as exported. > > >> > > >> > > >>> What problems will I cause by doing this? I am using the > > >>> > > >> symlink path > > >> > > >>> as the installation path for an application. The idea is a newer > > >>> version can be installed into a different directory, then after > > >>> testing the symlink will be changed to the new > > installation. Other > > >>> applications that reference the application will always use the > > >>> symlink path, as well as any user scripts. > > >>> > > >>> Wayne > > >>> > > >>> > > >>> > > >>>> -----Original Message----- > > >>>> From: linux-nfs-owner@vger.kernel.org > > >>>> [mailto:linux-nfs-owner@vger.kernel.org] On Behalf Of Sev Binello > > >>>> Sent: Monday, November 10, 2008 11:06 AM > > >>>> To: J. Bruce Fields; nfs@lists.sourceforge.net > > >>>> Subject: Re: [NFS] export dir thru 2 diff path names > > >>>> > > >>>> J. Bruce Fields wrote: > > >>>> > > >>>> > > >>>>> On Mon, Nov 10, 2008 at 10:55:48AM -0500, Sev Binello wrote: > > >>>>> > > >>>>> > > >>>>> > > >>>>>> Well the simplest approach doesn't work. > > >>>>>> i.e put symb link and actual path in the export file & try > > >>>>>> > > >>>>>> > > >>>> exporting > > >>>> > > >>>> > > >>>>>> it Exportfs dereferences the link and states that > > >>>>>> > > >>>>>> > > >>>> duplicates are not allowed. > > >>>> > > >>>> > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>> OK, makes sense. > > >>>>> > > >>>>> You could mount --bind the filesystem at the other location > > >>>>> > > >>>>> > > >>>> instead of > > >>>> > > >>>> > > >>>>> symlinking. > > >>>>> > > >>>>> The filehandles given to the client will be the same > > >>>>> > > >> across the two > > >> > > >>>>> exports. If you mount both from the same client, > > >>>>> > > >> behavior may vary > > >> > > >>>>> across different clients (for example, as to whether they > > >>>>> > > >>>>> > > >>>> attempt to > > >>>> > > >>>> > > >>>>> share caches between the two), but I think it'd work. > > >>>>> > > >>>>> (The question "why??!!??" does come to mind, though.) > > >>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>> Need to make a path change to how file systems are mounted and > > >>>> exported on the servers This then required a wholesale change to > > >>>> clients so they mount the correct path. > > >>>> Not an issue for linux. > > >>>> But since we don't administer windows pcs and they also > > mount the > > >>>> same file system, wanted to see if we could let them > > stay the way > > >>>> they were for now. > > >>>> > > >>>> We're just going to go ahead and have to coordinate this with > > >>>> windows guys. > > >>>> > > >>>> -Sev > > >>>> > > >>>> > > >>>>> --b. > > >>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>>>> -Sev > > >>>>>> > > >>>>>> J. Bruce Fields wrote: > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>>> On Fri, Nov 07, 2008 at 12:44:25PM -0500, Sev Binello wrote: > > >>>>>>> > > >>>>>>> > > >>>>>>> > > >>>>>>> > > >>>>>>>> Can anyone tell me if it's ok to export the same file system > > >>>>>>>> through 2 different paths ( one is a link) ? > > >>>>>>>> > > >>>>>>>> > > >>>>>>>> > > >>>>>>>> > > >>>>>>> I actually don't know. You could try it and tell us what > > >>>>>>> > > >>>>>>> > > >>>> you find > > >>>> > > >>>> > > >>>>>>> out.... > > >>>>>>> > > >>>>>>> If you're exporting something *containing* the symlink > > >>>>>>> > > >>>>>>> > > >>>> and expecting > > >>>> > > >>>> > > >>>>>>> the client to traverse into the filesystem, be aware that > > >>>>>>> > > >>>>>>> > > >>>> symlinks > > >>>> > > >>>> > > >>>>>>> over NFS are actually interpreted (and followed) on the > > >>>>>>> > > >>>>>>> > > >>>> client--so > > >>>> > > >>>> > > >>>>>>> they're interpreted as *client-side* paths, not server-side. > > >>>>>>> > > >>>>>>> If the path you're exporting is itself a symlink--it probably > > >>>>>>> depends on how nfs-utils treats symlinks found in > > >>>>>>> > > >>>>>>> > > >>>> /etc/exports. I'd > > >>>> > > >>>> > > >>>>>>> have to try it or check the code. > > >>>>>>> > > >>>>>>> Another way to export the filesystem in two different > > >>>>>>> > > >>>>>>> > > >>>> places would > > >>>> > > >>>> > > >>>>>>> be with mount --bind. > > >>>>>>> > > >>>>>>> --b. > > >>>>>>> > > >>>>>>> > > >>>>>>> > > >>>>>>> > > >>>>>> -- > > >>>>>> > > >>>>>> Sev Binello > > >>>>>> Brookhaven National Laboratory > > >>>>>> Upton, New York > > >>>>>> 631-344-5647 > > >>>>>> sev-IGkKxAqZmp0@public.gmane.org > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>> > > >>>> -------------------------------------------------------------- > > >>>> ----------- > > >>>> This SF.Net email is sponsored by the Moblin Your Move > > Developer's > > >>>> challenge Build the coolest Linux based applications with > > >>>> > > >> Moblin SDK > > >> > > >>>> & win great prizes Grand prize is a trip for two to an > > Open Source > > >>>> event anywhere in the world > > >>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ > > >>>> _______________________________________________ > > >>>> NFS maillist - NFS@lists.sourceforge.net > > >>>> https://lists.sourceforge.net/lists/listinfo/nfs > > >>>> _______________________________________________ > > >>>> Please note that nfs@lists.sourceforge.net is being discontinued. > > >>>> Please subscribe to linux-nfs@vger.kernel.org instead. > > >>>> http://vger.kernel.org/vger-lists.html#linux-nfs > > >>>> > > >>>> -- > > >>>> To unsubscribe from this list: send the line "unsubscribe > > >>>> > > >> linux-nfs" > > >> > > >>>> in the body of a message to majordomo@vger.kernel.org More > > >>>> > > >> majordomo > > >> > > >>>> info at http://vger.kernel.org/majordomo-info.html > > >>>> > > >>>> > > >>>> > > >> -- > > >> > > >> Sev Binello > > >> Brookhaven National Laboratory > > >> Upton, New York > > >> 631-344-5647 > > >> sev-IGkKxAqZmp0@public.gmane.org > > >> > > >> > > >> > > > > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that nfs@lists.sourceforge.net is being discontinued. Please subscribe to linux-nfs@vger.kernel.org instead. http://vger.kernel.org/vger-lists.html#linux-nfs ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [NFS] export dir thru 2 diff path names 2008-11-10 19:28 ` J. Bruce Fields @ 2008-11-10 19:36 ` Sev Binello 2008-11-10 20:20 ` Chuck Lever 1 sibling, 0 replies; 23+ messages in thread From: Sev Binello @ 2008-11-10 19:36 UTC (permalink / raw) To: J. Bruce Fields; +Cc: Murata, Dennis, nfs Since on the server side there truly is only 1 export. And clients just access the same export through 2 different names, I expect it would be safe. -Sev ps: But I think I'll wait for a simpler application (less negative ramifications) to test it BTW haven't seen this documented anywhere. J. Bruce Fields wrote: > On Mon, Nov 10, 2008 at 11:28:04AM -0800, Murata, Dennis wrote: > >> That really is the 64K question. During my initial testing, I exported >> the parent directory. Now I am explicitly exporting the installation >> directories, where I see the exportfs message. In the messages log file >> on the server the mount request from the client is always the actual >> directory. >> > > I don't see how this would be "unsafe"--if it works, go for it. > > One potential trap: it's using the same client list and export options > for both, so if you think you can make one of them read-only and one of > them writeable, for example, you'll be disapointed. > > --b. > > >> Wayne >> >> >>> -----Original Message----- >>> From: Sev Binello [mailto:sev-IGkKxAqZmp0@public.gmane.org] >>> Sent: Monday, November 10, 2008 1:04 PM >>> To: Murata, Dennis >>> Cc: J. Bruce Fields; nfs@lists.sourceforge.net >>> Subject: Re: [NFS] export dir thru 2 diff path names >>> >>> Hi - >>> Yeah, I see. >>> So it actually looks like you can do this. >>> I'm not 100% sure if safe --though it looks it -- so I'll >>> probably not use it for this application. >>> >>> Thanks >>> -Sev >>> >>> Murata, Dennis wrote: >>> >>>> That is correct, exportfs only shows the actual directory. >>>> >>> The client >>> >>>> seems to be able to mount the directory with either. >>>> >>>> Wayne >>>> >>>> >>>> >>>>> -----Original Message----- >>>>> From: Sev Binello [mailto:sev-IGkKxAqZmp0@public.gmane.org] >>>>> Sent: Monday, November 10, 2008 12:51 PM >>>>> To: Murata, Dennis >>>>> Cc: J. Bruce Fields; nfs@lists.sourceforge.net >>>>> Subject: Re: [NFS] export dir thru 2 diff path names >>>>> >>>>> Murata, Dennis wrote: >>>>> >>>>> >>>>>> I just tested this on a SL4.7 (RHEL 4.7 variant) using a >>>>>> >>>>>> >>>>> RHEL 4.4 nfs >>>>> >>>>> >>>>>> server. I did get the messages from exportfs about >>>>>> >>>>>> >>>>> duplicate export >>>>> >>>>> >>>>>> entries. On the client I was able to mount both the >>>>>> >>>>>> >>>>> symlink and the >>>>> >>>>> >>>>>> actual directory. They look like separate mounts. There are two >>>>>> entries in /proc/mounts and in /etc/mtab, one with the actual >>>>>> directory path, one with the symlink path. I am using >>>>>> >>>>>> >>>>> autofs to mount >>>>> >>>>> >>>>>> the directories, not hardcoded. Are you using newer >>>>>> >>> distributions? >>> >>>>>> >>>>>> >>>>>> >>>>> I tested on RHEL 4.6. >>>>> Interesting that you can still mount either one. >>>>> On the server an exportfs only shows the real path as exported. >>>>> >>>>> >>>>> >>>>>> What problems will I cause by doing this? I am using the >>>>>> >>>>>> >>>>> symlink path >>>>> >>>>> >>>>>> as the installation path for an application. The idea is a newer >>>>>> version can be installed into a different directory, then after >>>>>> testing the symlink will be changed to the new >>>>>> >>> installation. Other >>> >>>>>> applications that reference the application will always use the >>>>>> symlink path, as well as any user scripts. >>>>>> >>>>>> Wayne >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> -----Original Message----- >>>>>>> From: linux-nfs-owner@vger.kernel.org >>>>>>> [mailto:linux-nfs-owner@vger.kernel.org] On Behalf Of Sev Binello >>>>>>> Sent: Monday, November 10, 2008 11:06 AM >>>>>>> To: J. Bruce Fields; nfs@lists.sourceforge.net >>>>>>> Subject: Re: [NFS] export dir thru 2 diff path names >>>>>>> >>>>>>> J. Bruce Fields wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>>> On Mon, Nov 10, 2008 at 10:55:48AM -0500, Sev Binello wrote: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> Well the simplest approach doesn't work. >>>>>>>>> i.e put symb link and actual path in the export file & try >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>> exporting >>>>>>> >>>>>>> >>>>>>> >>>>>>>>> it Exportfs dereferences the link and states that >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>> duplicates are not allowed. >>>>>>> >>>>>>> >>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> OK, makes sense. >>>>>>>> >>>>>>>> You could mount --bind the filesystem at the other location >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> instead of >>>>>>> >>>>>>> >>>>>>> >>>>>>>> symlinking. >>>>>>>> >>>>>>>> The filehandles given to the client will be the same >>>>>>>> >>>>>>>> >>>>> across the two >>>>> >>>>> >>>>>>>> exports. If you mount both from the same client, >>>>>>>> >>>>>>>> >>>>> behavior may vary >>>>> >>>>> >>>>>>>> across different clients (for example, as to whether they >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> attempt to >>>>>>> >>>>>>> >>>>>>> >>>>>>>> share caches between the two), but I think it'd work. >>>>>>>> >>>>>>>> (The question "why??!!??" does come to mind, though.) >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> Need to make a path change to how file systems are mounted and >>>>>>> exported on the servers This then required a wholesale change to >>>>>>> clients so they mount the correct path. >>>>>>> Not an issue for linux. >>>>>>> But since we don't administer windows pcs and they also >>>>>>> >>> mount the >>> >>>>>>> same file system, wanted to see if we could let them >>>>>>> >>> stay the way >>> >>>>>>> they were for now. >>>>>>> >>>>>>> We're just going to go ahead and have to coordinate this with >>>>>>> windows guys. >>>>>>> >>>>>>> -Sev >>>>>>> >>>>>>> >>>>>>> >>>>>>>> --b. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> -Sev >>>>>>>>> >>>>>>>>> J. Bruce Fields wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> On Fri, Nov 07, 2008 at 12:44:25PM -0500, Sev Binello wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> Can anyone tell me if it's ok to export the same file system >>>>>>>>>>> through 2 different paths ( one is a link) ? >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> I actually don't know. You could try it and tell us what >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>> you find >>>>>>> >>>>>>> >>>>>>> >>>>>>>>>> out.... >>>>>>>>>> >>>>>>>>>> If you're exporting something *containing* the symlink >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>> and expecting >>>>>>> >>>>>>> >>>>>>> >>>>>>>>>> the client to traverse into the filesystem, be aware that >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>> symlinks >>>>>>> >>>>>>> >>>>>>> >>>>>>>>>> over NFS are actually interpreted (and followed) on the >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>> client--so >>>>>>> >>>>>>> >>>>>>> >>>>>>>>>> they're interpreted as *client-side* paths, not server-side. >>>>>>>>>> >>>>>>>>>> If the path you're exporting is itself a symlink--it probably >>>>>>>>>> depends on how nfs-utils treats symlinks found in >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>> /etc/exports. I'd >>>>>>> >>>>>>> >>>>>>> >>>>>>>>>> have to try it or check the code. >>>>>>>>>> >>>>>>>>>> Another way to export the filesystem in two different >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>> places would >>>>>>> >>>>>>> >>>>>>> >>>>>>>>>> be with mount --bind. >>>>>>>>>> >>>>>>>>>> --b. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> -- >>>>>>>>> >>>>>>>>> Sev Binello >>>>>>>>> Brookhaven National Laboratory >>>>>>>>> Upton, New York >>>>>>>>> 631-344-5647 >>>>>>>>> sev-IGkKxAqZmp0@public.gmane.org >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>> -------------------------------------------------------------- >>>>>>> ----------- >>>>>>> This SF.Net email is sponsored by the Moblin Your Move >>>>>>> >>> Developer's >>> >>>>>>> challenge Build the coolest Linux based applications with >>>>>>> >>>>>>> >>>>> Moblin SDK >>>>> >>>>> >>>>>>> & win great prizes Grand prize is a trip for two to an >>>>>>> >>> Open Source >>> >>>>>>> event anywhere in the world >>>>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>>>>>> _______________________________________________ >>>>>>> NFS maillist - NFS@lists.sourceforge.net >>>>>>> https://lists.sourceforge.net/lists/listinfo/nfs >>>>>>> _______________________________________________ >>>>>>> Please note that nfs@lists.sourceforge.net is being discontinued. >>>>>>> Please subscribe to linux-nfs@vger.kernel.org instead. >>>>>>> http://vger.kernel.org/vger-lists.html#linux-nfs >>>>>>> >>>>>>> -- >>>>>>> To unsubscribe from this list: send the line "unsubscribe >>>>>>> >>>>>>> >>>>> linux-nfs" >>>>> >>>>> >>>>>>> in the body of a message to majordomo@vger.kernel.org More >>>>>>> >>>>>>> >>>>> majordomo >>>>> >>>>> >>>>>>> info at http://vger.kernel.org/majordomo-info.html >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>> -- >>>>> >>>>> Sev Binello >>>>> Brookhaven National Laboratory >>>>> Upton, New York >>>>> 631-344-5647 >>>>> sev-IGkKxAqZmp0@public.gmane.org >>>>> >>>>> >>>>> >>>>> >>> ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that nfs@lists.sourceforge.net is being discontinued. Please subscribe to linux-nfs@vger.kernel.org instead. http://vger.kernel.org/vger-lists.html#linux-nfs ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [NFS] export dir thru 2 diff path names 2008-11-10 19:28 ` J. Bruce Fields 2008-11-10 19:36 ` Sev Binello @ 2008-11-10 20:20 ` Chuck Lever 2008-11-10 20:44 ` J. Bruce Fields 1 sibling, 1 reply; 23+ messages in thread From: Chuck Lever @ 2008-11-10 20:20 UTC (permalink / raw) To: J. Bruce Fields; +Cc: Murata, Dennis, nfs, Sev Binello On Nov 10, 2008, at Nov 10, 2008, 2:28 PM, J. Bruce Fields wrote: > On Mon, Nov 10, 2008 at 11:28:04AM -0800, Murata, Dennis wrote: >> That really is the 64K question. During my initial testing, I >> exported >> the parent directory. Now I am explicitly exporting the installation >> directories, where I see the exportfs message. In the messages log >> file >> on the server the mount request from the client is always the actual >> directory. > > I don't see how this would be "unsafe"--if it works, go for it. > > One potential trap: it's using the same client list and export options > for both, so if you think you can make one of them read-only and one > of > them writeable, for example, you'll be disapointed. I wonder how this behaves on the client side. If the same client mounts both paths, will it recognize that these are the same and use a shared page cache for both? > --b. > >> >> Wayne >> >>> -----Original Message----- >>> From: Sev Binello [mailto:sev-IGkKxAqZmp0@public.gmane.org] >>> Sent: Monday, November 10, 2008 1:04 PM >>> To: Murata, Dennis >>> Cc: J. Bruce Fields; nfs@lists.sourceforge.net >>> Subject: Re: [NFS] export dir thru 2 diff path names >>> >>> Hi - >>> Yeah, I see. >>> So it actually looks like you can do this. >>> I'm not 100% sure if safe --though it looks it -- so I'll >>> probably not use it for this application. >>> >>> Thanks >>> -Sev >>> >>> Murata, Dennis wrote: >>>> That is correct, exportfs only shows the actual directory. >>> The client >>>> seems to be able to mount the directory with either. >>>> >>>> Wayne >>>> >>>> >>>>> -----Original Message----- >>>>> From: Sev Binello [mailto:sev-IGkKxAqZmp0@public.gmane.org] >>>>> Sent: Monday, November 10, 2008 12:51 PM >>>>> To: Murata, Dennis >>>>> Cc: J. Bruce Fields; nfs@lists.sourceforge.net >>>>> Subject: Re: [NFS] export dir thru 2 diff path names >>>>> >>>>> Murata, Dennis wrote: >>>>> >>>>>> I just tested this on a SL4.7 (RHEL 4.7 variant) using a >>>>>> >>>>> RHEL 4.4 nfs >>>>> >>>>>> server. I did get the messages from exportfs about >>>>>> >>>>> duplicate export >>>>> >>>>>> entries. On the client I was able to mount both the >>>>>> >>>>> symlink and the >>>>> >>>>>> actual directory. They look like separate mounts. There are two >>>>>> entries in /proc/mounts and in /etc/mtab, one with the actual >>>>>> directory path, one with the symlink path. I am using >>>>>> >>>>> autofs to mount >>>>> >>>>>> the directories, not hardcoded. Are you using newer >>> distributions? >>>>>> >>>>>> >>>>> I tested on RHEL 4.6. >>>>> Interesting that you can still mount either one. >>>>> On the server an exportfs only shows the real path as exported. >>>>> >>>>> >>>>>> What problems will I cause by doing this? I am using the >>>>>> >>>>> symlink path >>>>> >>>>>> as the installation path for an application. The idea is a newer >>>>>> version can be installed into a different directory, then after >>>>>> testing the symlink will be changed to the new >>> installation. Other >>>>>> applications that reference the application will always use the >>>>>> symlink path, as well as any user scripts. >>>>>> >>>>>> Wayne >>>>>> >>>>>> >>>>>> >>>>>>> -----Original Message----- >>>>>>> From: linux-nfs-owner@vger.kernel.org >>>>>>> [mailto:linux-nfs-owner@vger.kernel.org] On Behalf Of Sev >>>>>>> Binello >>>>>>> Sent: Monday, November 10, 2008 11:06 AM >>>>>>> To: J. Bruce Fields; nfs@lists.sourceforge.net >>>>>>> Subject: Re: [NFS] export dir thru 2 diff path names >>>>>>> >>>>>>> J. Bruce Fields wrote: >>>>>>> >>>>>>> >>>>>>>> On Mon, Nov 10, 2008 at 10:55:48AM -0500, Sev Binello wrote: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> Well the simplest approach doesn't work. >>>>>>>>> i.e put symb link and actual path in the export file & try >>>>>>>>> >>>>>>>>> >>>>>>> exporting >>>>>>> >>>>>>> >>>>>>>>> it Exportfs dereferences the link and states that >>>>>>>>> >>>>>>>>> >>>>>>> duplicates are not allowed. >>>>>>> >>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> OK, makes sense. >>>>>>>> >>>>>>>> You could mount --bind the filesystem at the other location >>>>>>>> >>>>>>>> >>>>>>> instead of >>>>>>> >>>>>>> >>>>>>>> symlinking. >>>>>>>> >>>>>>>> The filehandles given to the client will be the same >>>>>>>> >>>>> across the two >>>>> >>>>>>>> exports. If you mount both from the same client, >>>>>>>> >>>>> behavior may vary >>>>> >>>>>>>> across different clients (for example, as to whether they >>>>>>>> >>>>>>>> >>>>>>> attempt to >>>>>>> >>>>>>> >>>>>>>> share caches between the two), but I think it'd work. >>>>>>>> >>>>>>>> (The question "why??!!??" does come to mind, though.) >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> Need to make a path change to how file systems are mounted and >>>>>>> exported on the servers This then required a wholesale change to >>>>>>> clients so they mount the correct path. >>>>>>> Not an issue for linux. >>>>>>> But since we don't administer windows pcs and they also >>> mount the >>>>>>> same file system, wanted to see if we could let them >>> stay the way >>>>>>> they were for now. >>>>>>> >>>>>>> We're just going to go ahead and have to coordinate this with >>>>>>> windows guys. >>>>>>> >>>>>>> -Sev >>>>>>> >>>>>>> >>>>>>>> --b. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> -Sev >>>>>>>>> >>>>>>>>> J. Bruce Fields wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> On Fri, Nov 07, 2008 at 12:44:25PM -0500, Sev Binello wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> Can anyone tell me if it's ok to export the same file system >>>>>>>>>>> through 2 different paths ( one is a link) ? >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> I actually don't know. You could try it and tell us what >>>>>>>>>> >>>>>>>>>> >>>>>>> you find >>>>>>> >>>>>>> >>>>>>>>>> out.... >>>>>>>>>> >>>>>>>>>> If you're exporting something *containing* the symlink >>>>>>>>>> >>>>>>>>>> >>>>>>> and expecting >>>>>>> >>>>>>> >>>>>>>>>> the client to traverse into the filesystem, be aware that >>>>>>>>>> >>>>>>>>>> >>>>>>> symlinks >>>>>>> >>>>>>> >>>>>>>>>> over NFS are actually interpreted (and followed) on the >>>>>>>>>> >>>>>>>>>> >>>>>>> client--so >>>>>>> >>>>>>> >>>>>>>>>> they're interpreted as *client-side* paths, not server-side. >>>>>>>>>> >>>>>>>>>> If the path you're exporting is itself a symlink--it probably >>>>>>>>>> depends on how nfs-utils treats symlinks found in >>>>>>>>>> >>>>>>>>>> >>>>>>> /etc/exports. I'd >>>>>>> >>>>>>> >>>>>>>>>> have to try it or check the code. >>>>>>>>>> >>>>>>>>>> Another way to export the filesystem in two different >>>>>>>>>> >>>>>>>>>> >>>>>>> places would >>>>>>> >>>>>>> >>>>>>>>>> be with mount --bind. >>>>>>>>>> >>>>>>>>>> --b. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> -- >>>>>>>>> >>>>>>>>> Sev Binello >>>>>>>>> Brookhaven National Laboratory >>>>>>>>> Upton, New York >>>>>>>>> 631-344-5647 >>>>>>>>> sev-IGkKxAqZmp0@public.gmane.org >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>> -------------------------------------------------------------- >>>>>>> ----------- >>>>>>> This SF.Net email is sponsored by the Moblin Your Move >>> Developer's >>>>>>> challenge Build the coolest Linux based applications with >>>>>>> >>>>> Moblin SDK >>>>> >>>>>>> & win great prizes Grand prize is a trip for two to an >>> Open Source >>>>>>> event anywhere in the world >>>>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>>>>>> _______________________________________________ >>>>>>> NFS maillist - NFS@lists.sourceforge.net >>>>>>> https://lists.sourceforge.net/lists/listinfo/nfs >>>>>>> _______________________________________________ >>>>>>> Please note that nfs@lists.sourceforge.net is being >>>>>>> discontinued. >>>>>>> Please subscribe to linux-nfs@vger.kernel.org instead. >>>>>>> http://vger.kernel.org/vger-lists.html#linux-nfs >>>>>>> >>>>>>> -- >>>>>>> To unsubscribe from this list: send the line "unsubscribe >>>>>>> >>>>> linux-nfs" >>>>> >>>>>>> in the body of a message to majordomo@vger.kernel.org More >>>>>>> >>>>> majordomo >>>>> >>>>>>> info at http://vger.kernel.org/majordomo-info.html >>>>>>> >>>>>>> >>>>>>> >>>>> -- >>>>> >>>>> Sev Binello >>>>> Brookhaven National Laboratory >>>>> Upton, New York >>>>> 631-344-5647 >>>>> sev-IGkKxAqZmp0@public.gmane.org >>>>> >>>>> >>>>> >>> >>> > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win > great prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > NFS maillist - NFS@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nfs > _______________________________________________ > Please note that nfs@lists.sourceforge.net is being discontinued. > Please subscribe to linux-nfs@vger.kernel.org instead. > http://vger.kernel.org/vger-lists.html#linux-nfs > > -- > To unsubscribe from this list: send the line "unsubscribe linux-nfs" > in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Chuck Lever chuck[dot]lever[at]oracle[dot]com ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that nfs@lists.sourceforge.net is being discontinued. Please subscribe to linux-nfs@vger.kernel.org instead. http://vger.kernel.org/vger-lists.html#linux-nfs ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [NFS] export dir thru 2 diff path names 2008-11-10 20:20 ` Chuck Lever @ 2008-11-10 20:44 ` J. Bruce Fields 2008-11-12 18:04 ` Murata, Dennis 0 siblings, 1 reply; 23+ messages in thread From: J. Bruce Fields @ 2008-11-10 20:44 UTC (permalink / raw) To: Chuck Lever; +Cc: Murata, Dennis, nfs, Sev Binello On Mon, Nov 10, 2008 at 03:20:42PM -0500, Chuck Lever wrote: > On Nov 10, 2008, at Nov 10, 2008, 2:28 PM, J. Bruce Fields wrote: >> On Mon, Nov 10, 2008 at 11:28:04AM -0800, Murata, Dennis wrote: >>> That really is the 64K question. During my initial testing, I >>> exported >>> the parent directory. Now I am explicitly exporting the installation >>> directories, where I see the exportfs message. In the messages log >>> file >>> on the server the mount request from the client is always the actual >>> directory. >> >> I don't see how this would be "unsafe"--if it works, go for it. >> >> One potential trap: it's using the same client list and export options >> for both, so if you think you can make one of them read-only and one >> of >> them writeable, for example, you'll be disapointed. > > I wonder how this behaves on the client side. If the same client mounts > both paths, will it recognize that these are the same and use a shared > page cache for both? Yeah, who knows. I suspect it assumes they're different if the mount paths are different. But for most people's purposes it probably doesn't matter much. (For the purposes people have mentioned so far they don't even need to mount both paths from the same client at once.) --b. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that nfs@lists.sourceforge.net is being discontinued. Please subscribe to linux-nfs@vger.kernel.org instead. http://vger.kernel.org/vger-lists.html#linux-nfs ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [NFS] export dir thru 2 diff path names 2008-11-10 20:44 ` J. Bruce Fields @ 2008-11-12 18:04 ` Murata, Dennis [not found] ` <620E93B2E5CC3B46BD811165E3335B8702FD3423-9/h0XwadXgnyjpQT3Si/rsM9+qvyE0V4QQ4Iyu8u01E@public.gmane.org> 0 siblings, 1 reply; 23+ messages in thread From: Murata, Dennis @ 2008-11-12 18:04 UTC (permalink / raw) To: J. Bruce Fields, Chuck Lever; +Cc: nfs, Sev Binello One last question for the maintainers and the community. Is this viewed as an undocumented feature or a bug to be fixed? I would hate to recommend use of the exported link, only to have it disabled by an updated patch. Wayne > -----Original Message----- > From: J. Bruce Fields [mailto:bfields@fieldses.org] > Sent: Monday, November 10, 2008 2:45 PM > To: Chuck Lever > Cc: Murata, Dennis; nfs@lists.sourceforge.net; Sev Binello > Subject: Re: [NFS] export dir thru 2 diff path names > > On Mon, Nov 10, 2008 at 03:20:42PM -0500, Chuck Lever wrote: > > On Nov 10, 2008, at Nov 10, 2008, 2:28 PM, J. Bruce Fields wrote: > >> On Mon, Nov 10, 2008 at 11:28:04AM -0800, Murata, Dennis wrote: > >>> That really is the 64K question. During my initial testing, I > >>> exported the parent directory. Now I am explicitly exporting the > >>> installation directories, where I see the exportfs > message. In the > >>> messages log file on the server the mount request from > the client is > >>> always the actual directory. > >> > >> I don't see how this would be "unsafe"--if it works, go for it. > >> > >> One potential trap: it's using the same client list and export > >> options for both, so if you think you can make one of them > read-only > >> and one of them writeable, for example, you'll be disapointed. > > > > I wonder how this behaves on the client side. If the same client > > mounts both paths, will it recognize that these are the > same and use a > > shared page cache for both? > > Yeah, who knows. I suspect it assumes they're different if > the mount paths are different. > > But for most people's purposes it probably doesn't matter > much. (For the purposes people have mentioned so far they > don't even need to mount both paths from the same client at once.) > > --b. > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that nfs@lists.sourceforge.net is being discontinued. Please subscribe to linux-nfs@vger.kernel.org instead. http://vger.kernel.org/vger-lists.html#linux-nfs ^ permalink raw reply [flat|nested] 23+ messages in thread
[parent not found: <620E93B2E5CC3B46BD811165E3335B8702FD3423-9/h0XwadXgnyjpQT3Si/rsM9+qvyE0V4QQ4Iyu8u01E@public.gmane.org>]
* Re: [NFS] export dir thru 2 diff path names [not found] ` <620E93B2E5CC3B46BD811165E3335B8702FD3423-9/h0XwadXgnyjpQT3Si/rsM9+qvyE0V4QQ4Iyu8u01E@public.gmane.org> @ 2008-11-16 20:04 ` J. Bruce Fields 2008-11-17 16:54 ` Murata, Dennis 2008-12-03 21:46 ` J. Bruce Fields 1 sibling, 1 reply; 23+ messages in thread From: J. Bruce Fields @ 2008-11-16 20:04 UTC (permalink / raw) To: Murata, Dennis; +Cc: Chuck Lever, nfs, Sev Binello On Wed, Nov 12, 2008 at 10:04:30AM -0800, Murata, Dennis wrote: > One last question for the maintainers and the community. Is this viewed > as an undocumented feature or a bug to be fixed? By "this" you mean mountd's current practice of following symlinks in export points? If people are using it (and I can't imagine you're the only ones to try), then I think we should make it a point to keep it around. Patches to the documentation (probably the exports man page, kept in the nfs-utils code) welcomed. --b. > I would hate to > recommend use of the exported link, only to have it disabled by an > updated patch. > > Wayne > > > -----Original Message----- > > From: J. Bruce Fields [mailto:bfields@fieldses.org] > > Sent: Monday, November 10, 2008 2:45 PM > > To: Chuck Lever > > Cc: Murata, Dennis; nfs@lists.sourceforge.net; Sev Binello > > Subject: Re: [NFS] export dir thru 2 diff path names > > > > On Mon, Nov 10, 2008 at 03:20:42PM -0500, Chuck Lever wrote: > > > On Nov 10, 2008, at Nov 10, 2008, 2:28 PM, J. Bruce Fields wrote: > > >> On Mon, Nov 10, 2008 at 11:28:04AM -0800, Murata, Dennis wrote: > > >>> That really is the 64K question. During my initial testing, I > > >>> exported the parent directory. Now I am explicitly exporting the > > >>> installation directories, where I see the exportfs > > message. In the > > >>> messages log file on the server the mount request from > > the client is > > >>> always the actual directory. > > >> > > >> I don't see how this would be "unsafe"--if it works, go for it. > > >> > > >> One potential trap: it's using the same client list and export > > >> options for both, so if you think you can make one of them > > read-only > > >> and one of them writeable, for example, you'll be disapointed. > > > > > > I wonder how this behaves on the client side. If the same client > > > mounts both paths, will it recognize that these are the > > same and use a > > > shared page cache for both? > > > > Yeah, who knows. I suspect it assumes they're different if > > the mount paths are different. > > > > But for most people's purposes it probably doesn't matter > > much. (For the purposes people have mentioned so far they > > don't even need to mount both paths from the same client at once.) > > > > --b. > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > NFS maillist - NFS@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nfs > _______________________________________________ > Please note that nfs@lists.sourceforge.net is being discontinued. > Please subscribe to linux-nfs@vger.kernel.org instead. > http://vger.kernel.org/vger-lists.html#linux-nfs > > -- > To unsubscribe from this list: send the line "unsubscribe linux-nfs" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that nfs@lists.sourceforge.net is being discontinued. Please subscribe to linux-nfs@vger.kernel.org instead. http://vger.kernel.org/vger-lists.html#linux-nfs ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [NFS] export dir thru 2 diff path names 2008-11-16 20:04 ` J. Bruce Fields @ 2008-11-17 16:54 ` Murata, Dennis 0 siblings, 0 replies; 23+ messages in thread From: Murata, Dennis @ 2008-11-17 16:54 UTC (permalink / raw) To: J. Bruce Fields; +Cc: Chuck Lever, nfs, Sev Binello > -----Original Message----- > From: J. Bruce Fields [mailto:bfields@fieldses.org] > Sent: Sunday, November 16, 2008 2:04 PM > To: Murata, Dennis > Cc: Chuck Lever; nfs@lists.sourceforge.net; Sev Binello > Subject: Re: [NFS] export dir thru 2 diff path names > > On Wed, Nov 12, 2008 at 10:04:30AM -0800, Murata, Dennis wrote: > > One last question for the maintainers and the community. Is this > > viewed as an undocumented feature or a bug to be fixed? > > By "this" you mean mountd's current practice of following > symlinks in export points? If people are using it (and I > can't imagine you're the only ones to try), then I think we > should make it a point to keep it around. Patches to the > documentation (probably the exports man page, kept in the > nfs-utils code) welcomed. > > --b. The "following symlinks" is a part of what I am asking, but the other point is the idea of exporting a directory with two different path names. I didn't know if the message from exportfs, i.e. duplicated export entries, was designed as a warning or an error. As you pointed out, at any particular client workstation the directory would probably be mounted by only one of the names, but a different workstation may use the other name, so the directory would have to be exported by both names from the server. I am still working out the details, but in my situation it may be possible that the directory will only be exported by one of the names depending on the stage of the process it is in. Wayne > > > I would hate to > > recommend use of the exported link, only to have it disabled by an > > updated patch. > > > > Wayne > > > > > -----Original Message----- > > > From: J. Bruce Fields [mailto:bfields@fieldses.org] > > > Sent: Monday, November 10, 2008 2:45 PM > > > To: Chuck Lever > > > Cc: Murata, Dennis; nfs@lists.sourceforge.net; Sev Binello > > > Subject: Re: [NFS] export dir thru 2 diff path names > > > > > > On Mon, Nov 10, 2008 at 03:20:42PM -0500, Chuck Lever wrote: > > > > On Nov 10, 2008, at Nov 10, 2008, 2:28 PM, J. Bruce > Fields wrote: > > > >> On Mon, Nov 10, 2008 at 11:28:04AM -0800, Murata, Dennis wrote: > > > >>> That really is the 64K question. During my initial > testing, I > > > >>> exported the parent directory. Now I am explicitly exporting > > > >>> the installation directories, where I see the exportfs > > > message. In the > > > >>> messages log file on the server the mount request from > > > the client is > > > >>> always the actual directory. > > > >> > > > >> I don't see how this would be "unsafe"--if it works, go for it. > > > >> > > > >> One potential trap: it's using the same client list and export > > > >> options for both, so if you think you can make one of them > > > read-only > > > >> and one of them writeable, for example, you'll be disapointed. > > > > > > > > I wonder how this behaves on the client side. If the > same client > > > > mounts both paths, will it recognize that these are the > > > same and use a > > > > shared page cache for both? > > > > > > Yeah, who knows. I suspect it assumes they're different if the > > > mount paths are different. > > > > > > But for most people's purposes it probably doesn't matter much. > > > (For the purposes people have mentioned so far they don't > even need > > > to mount both paths from the same client at once.) > > > > > > --b. > > > > > > > > ---------------------------------------------------------------------- > > --- This SF.Net email is sponsored by the Moblin Your Move > Developer's > > challenge Build the coolest Linux based applications with > Moblin SDK & > > win great prizes Grand prize is a trip for two to an Open > Source event > > anywhere in the world > > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > > _______________________________________________ > > NFS maillist - NFS@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/nfs > > _______________________________________________ > > Please note that nfs@lists.sourceforge.net is being discontinued. > > Please subscribe to linux-nfs@vger.kernel.org instead. > > http://vger.kernel.org/vger-lists.html#linux-nfs > > > > -- > > To unsubscribe from this list: send the line "unsubscribe > linux-nfs" > > in the body of a message to majordomo@vger.kernel.org More > majordomo > > info at http://vger.kernel.org/majordomo-info.html > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that nfs@lists.sourceforge.net is being discontinued. Please subscribe to linux-nfs@vger.kernel.org instead. http://vger.kernel.org/vger-lists.html#linux-nfs ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [NFS] export dir thru 2 diff path names [not found] ` <620E93B2E5CC3B46BD811165E3335B8702FD3423-9/h0XwadXgnyjpQT3Si/rsM9+qvyE0V4QQ4Iyu8u01E@public.gmane.org> 2008-11-16 20:04 ` J. Bruce Fields @ 2008-12-03 21:46 ` J. Bruce Fields 1 sibling, 0 replies; 23+ messages in thread From: J. Bruce Fields @ 2008-12-03 21:46 UTC (permalink / raw) To: Murata, Dennis; +Cc: Chuck Lever, nfs, Sev Binello On Wed, Nov 12, 2008 at 10:04:30AM -0800, Murata, Dennis wrote: > One last question for the maintainers and the community. Is this viewed > as an undocumented feature or a bug to be fixed? I would hate to > recommend use of the exported link, only to have it disabled by an > updated patch. Hopefully if it turns out there's some good reason why we'd need to disable it, then we can provide some sort of backwards-compatibility flag (or at least a warning). --b. > > Wayne > > > -----Original Message----- > > From: J. Bruce Fields [mailto:bfields@fieldses.org] > > Sent: Monday, November 10, 2008 2:45 PM > > To: Chuck Lever > > Cc: Murata, Dennis; nfs@lists.sourceforge.net; Sev Binello > > Subject: Re: [NFS] export dir thru 2 diff path names > > > > On Mon, Nov 10, 2008 at 03:20:42PM -0500, Chuck Lever wrote: > > > On Nov 10, 2008, at Nov 10, 2008, 2:28 PM, J. Bruce Fields wrote: > > >> On Mon, Nov 10, 2008 at 11:28:04AM -0800, Murata, Dennis wrote: > > >>> That really is the 64K question. During my initial testing, I > > >>> exported the parent directory. Now I am explicitly exporting the > > >>> installation directories, where I see the exportfs > > message. In the > > >>> messages log file on the server the mount request from > > the client is > > >>> always the actual directory. > > >> > > >> I don't see how this would be "unsafe"--if it works, go for it. > > >> > > >> One potential trap: it's using the same client list and export > > >> options for both, so if you think you can make one of them > > read-only > > >> and one of them writeable, for example, you'll be disapointed. > > > > > > I wonder how this behaves on the client side. If the same client > > > mounts both paths, will it recognize that these are the > > same and use a > > > shared page cache for both? > > > > Yeah, who knows. I suspect it assumes they're different if > > the mount paths are different. > > > > But for most people's purposes it probably doesn't matter > > much. (For the purposes people have mentioned so far they > > don't even need to mount both paths from the same client at once.) > > > > --b. > > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that nfs@lists.sourceforge.net is being discontinued. Please subscribe to linux-nfs@vger.kernel.org instead. http://vger.kernel.org/vger-lists.html#linux-nfs ^ permalink raw reply [flat|nested] 23+ messages in thread
end of thread, other threads:[~2008-12-03 21:47 UTC | newest]
Thread overview: 23+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-01-14 16:41 [NFS] Redhat WS4 mount default changed to tcp ? Sev Binello
[not found] ` <478B90A1.5000900-IGkKxAqZmp0@public.gmane.org>
2008-01-14 17:06 ` Trond Myklebust
[not found] ` <1200330387.7470.11.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-01-14 17:22 ` Sev Binello
[not found] ` <478B9A64.5030903-IGkKxAqZmp0@public.gmane.org>
2008-01-14 17:39 ` Trond Myklebust
2008-11-07 17:44 ` [NFS] export dir thru 2 diff path names Sev Binello
[not found] ` <49147E79.6000508-IGkKxAqZmp0@public.gmane.org>
2008-11-09 15:58 ` J. Bruce Fields
2008-11-10 15:55 ` Sev Binello
[not found] ` <49185984.8010500-IGkKxAqZmp0@public.gmane.org>
2008-11-10 16:49 ` J. Bruce Fields
2008-11-10 17:05 ` Sev Binello
[not found] ` <491869F0.1000505-IGkKxAqZmp0@public.gmane.org>
2008-11-10 18:08 ` J. Bruce Fields
2008-11-10 18:11 ` Murata, Dennis
[not found] ` <620E93B2E5CC3B46BD811165E3335B8702F374A0-9/h0XwadXgnyjpQT3Si/rsM9+qvyE0V4QQ4Iyu8u01E@public.gmane.org>
2008-11-10 18:51 ` Sev Binello
[not found] ` <491882AB.6070908-IGkKxAqZmp0@public.gmane.org>
2008-11-10 18:58 ` Murata, Dennis
[not found] ` <620E93B2E5CC3B46BD811165E3335B8702F37542-9/h0XwadXgnyjpQT3Si/rsM9+qvyE0V4QQ4Iyu8u01E@public.gmane.org>
2008-11-10 19:03 ` Sev Binello
[not found] ` <4918859C.6080608-IGkKxAqZmp0@public.gmane.org>
2008-11-10 19:28 ` Murata, Dennis
[not found] ` <620E93B2E5CC3B46BD811165E3335B8702F3759D-9/h0XwadXgnyjpQT3Si/rsM9+qvyE0V4QQ4Iyu8u01E@public.gmane.org>
2008-11-10 19:28 ` J. Bruce Fields
2008-11-10 19:36 ` Sev Binello
2008-11-10 20:20 ` Chuck Lever
2008-11-10 20:44 ` J. Bruce Fields
2008-11-12 18:04 ` Murata, Dennis
[not found] ` <620E93B2E5CC3B46BD811165E3335B8702FD3423-9/h0XwadXgnyjpQT3Si/rsM9+qvyE0V4QQ4Iyu8u01E@public.gmane.org>
2008-11-16 20:04 ` J. Bruce Fields
2008-11-17 16:54 ` Murata, Dennis
2008-12-03 21:46 ` J. Bruce Fields
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox