Linux NFS development
 help / color / mirror / Atom feed
From: Sev Binello <sev-IGkKxAqZmp0@public.gmane.org>
To: "Murata, Dennis" <DENNIS.MURATA-jTGLxe6cr0Q@public.gmane.org>
Cc: "J. Bruce Fields" <bfields@fieldses.org>, nfs@lists.sourceforge.net
Subject: Re: [NFS] export dir thru 2 diff path names
Date: Mon, 10 Nov 2008 14:03:56 -0500	[thread overview]
Message-ID: <4918859C.6080608@bnl.gov> (raw)
In-Reply-To: <620E93B2E5CC3B46BD811165E3335B8702F37542-9/h0XwadXgnyjpQT3Si/rsM9+qvyE0V4QQ4Iyu8u01E@public.gmane.org>

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


  parent reply	other threads:[~2008-11-10 19:04 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
     [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

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4918859C.6080608@bnl.gov \
    --to=sev-igkkxaqzmp0@public.gmane.org \
    --cc=DENNIS.MURATA-jTGLxe6cr0Q@public.gmane.org \
    --cc=bfields@fieldses.org \
    --cc=nfs@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox