Redhat WS4 mount default changed to tcp ?
Subsystems (2)
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
Signature · 19 lines
Sev Binello Brookhaven National Laboratory Upton, New York 631-344-5647 [email protected] ------------------------------------------------------------------------- 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 - [email protected] https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead. http://vger.kernel.org/vger-lists.html#linux-nfs
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 2 lines · Sev Binello
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').
Quoted 2 lines
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
A message that is not in the archive (sent off-list or not yet received): 1200330387.7470.11.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org
Quoted 11 lines · Trond Myklebust
Quoted 3 lines · Sev Binello
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 ?
Quoted 11 lines
Quoted 3 lines
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
Signature · 19 lines
Sev Binello Brookhaven National Laboratory Upton, New York 631-344-5647 [email protected] ------------------------------------------------------------------------- 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 - [email protected] https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead. http://vger.kernel.org/vger-lists.html#linux-nfs
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 7 lines · Sev Binello
Quoted 6 lines · Trond Myklebust
Quoted 3 lines · Sev Binello
Does anyone know the reason Redhat changed the default mount protocol to tcp ?
Quoted 6 lines
Quoted 5 lines
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
[NFS] export dir thru 2 diff path names
In reply to a message not in the archiveCan anyone tell me if it's ok to export the same file system through 2 different paths ( one is a link) ?
Thanks
-Sev
Signature · 19 lines
Sev Binello Brookhaven National Laboratory Upton, New York 631-344-5647 [email protected] ------------------------------------------------------------------------- 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 - [email protected] https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead. http://vger.kernel.org/vger-lists.html#linux-nfs
A message that is not in the archive (sent off-list or not yet received): [email protected]
Re: [NFS] export dir thru 2 diff path names
Quoted 2 lines · Sev Binello
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
Re: [NFS] export dir thru 2 diff path names
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
Quoted 23 lines · J. Bruce Fields
Quoted 3 lines · Sev Binello
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.
Signature · 19 lines
Sev Binello Brookhaven National Laboratory Upton, New York 631-344-5647 [email protected] ------------------------------------------------------------------------- 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 - [email protected] https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead. http://vger.kernel.org/vger-lists.html#linux-nfs
A message that is not in the archive (sent off-list or not yet received): [email protected]
Re: [NFS] export dir thru 2 diff path names
Quoted 3 lines · Sev Binello
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.
Quoted 22 lines
-Sev
Quoted 18 lines · J. Bruce Fields
Quoted 3 lines · Sev Binello
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.
Quoted 15 lines
Quoted 5 lines
Another way to export the filesystem in two different places would be with mount --bind.
--b.
Signature · 5 lines
Sev Binello Brookhaven National Laboratory Upton, New York 631-344-5647 [email protected]
-------------------------------------------------------------------------
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
Re: [NFS] export dir thru 2 diff path names
Quoted 12 lines · J. Bruce Fields
Quoted 4 lines · Sev Binello
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.
Quoted 8 lines
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
Quoted 41 lines
--b.
Quoted 38 lines
-Sev
Quoted 25 lines · J. Bruce Fields
Quoted 4 lines · Sev Binello
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.
Signature · 5 lines
Sev Binello Brookhaven National Laboratory Upton, New York 631-344-5647 [email protected]
-------------------------------------------------------------------------
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
A message that is not in the archive (sent off-list or not yet received): [email protected]
Re: [NFS] export dir thru 2 diff path names
Quoted 14 lines · Sev Binello
Quoted 5 lines · J. Bruce Fields
OK, makes sense.
You could mount --bind the filesystem at the other location instead of symlinking.
Quoted 8 lines
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.)
Quoted 8 lines
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.
Quoted 60 lines
We're just going to go ahead and have to coordinate this with windows guys.
-Sev
Quoted 41 lines
--b.
Quoted 38 lines
-Sev
Quoted 25 lines · J. Bruce Fields
Quoted 4 lines · Sev Binello
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.
Signature · 5 lines
Sev Binello Brookhaven National Laboratory Upton, New York 631-344-5647 [email protected]-------------------------------------------------------------------------
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
Quoted 4 lines
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected]
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
Re: [NFS] export dir thru 2 diff path names
In reply to a message not in the archiveI 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
Quoted 108 lines
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Sev Binello
Sent: Monday, November 10, 2008 11:06 AM
To: J. Bruce Fields; [email protected]
Subject: Re: [NFS] export dir thru 2 diff path namesQuoted 4 lines · J. Bruce Fields
Quoted 2 lines · Sev Binello
Well the simplest approach doesn't work.
i.e put symb link and actual path in the export file & tryexporting
Quoted 1 line
Quoted 1 line
it Exportfs dereferences the link and states that
duplicates are not allowed.
Quoted 5 lines
Quoted 1 line
OK, makes sense.
You could mount --bind the filesystem at the other location
instead of
Quoted 5 lines
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
Quoted 5 lines
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
Quoted 15 lines
--b.
Quoted 12 lines
-Sev
Quoted 8 lines · J. Bruce Fields
Quoted 4 lines · Sev Binello
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
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
out....
If you're exporting something *containing* the symlink
and expecting
Quoted 1 line
Quoted 1 line
Quoted 1 line
the client to traverse into the filesystem, be aware that
symlinks
Quoted 1 line
Quoted 1 line
Quoted 1 line
over NFS are actually interpreted (and followed) on the
client--so
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
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'dQuoted 3 lines
Quoted 3 lines
Quoted 3 lines
have to try it or check the code.
Another way to export the filesystem in two different
places would
Quoted 7 lines
Quoted 7 lines
Quoted 5 lines
be with mount --bind.
--b.
--
Quoted 7 lines
Quoted 7 lines
Sev Binello
Brookhaven National Laboratory
Upton, New York
631-344-5647
[email protected]--------------------------------------------------------------
-----------
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
Quoted 6 lines
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected] 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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
A message that is not in the archive (sent off-list or not yet received): 620E93B2E5CC3B46BD811165E3335B8702F374A0-9/h0XwadXgnyjpQT3Si/[email protected]
Re: [NFS] export dir thru 2 diff path names
Quoted 8 lines · Dennis
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/mountsand 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.
Quoted 153 lines
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
Quoted 143 lines
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Sev Binello
Sent: Monday, November 10, 2008 11:06 AM
To: J. Bruce Fields; [email protected]
Subject: Re: [NFS] export dir thru 2 diff path namesQuoted 6 lines · J. Bruce Fields
Quoted 3 lines · Sev Binello
Well the simplest approach doesn't work.
i.e put symb link and actual path in the export file & tryexporting
Quoted 2 lines
Quoted 2 lines
it Exportfs dereferences the link and states that
duplicates are not allowed.
Quoted 6 lines
Quoted 2 lines
OK, makes sense.
You could mount --bind the filesystem at the other location
instead of
Quoted 6 lines
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
Quoted 6 lines
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
Quoted 20 lines
--b.
Quoted 16 lines
-Sev
Quoted 11 lines · J. Bruce Fields
Quoted 5 lines · Sev Binello
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
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
out....
If you're exporting something *containing* the symlink
and expecting
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
the client to traverse into the filesystem, be aware that
symlinks
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
over NFS are actually interpreted (and followed) on the
client--so
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
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'dQuoted 4 lines
Quoted 4 lines
Quoted 4 lines
have to try it or check the code.
Another way to export the filesystem in two different
places would
Quoted 8 lines
Quoted 8 lines
Quoted 6 lines
be with mount --bind.
--b.
--
Quoted 8 lines
Quoted 8 lines
Sev Binello
Brookhaven National Laboratory
Upton, New York
631-344-5647
[email protected]--------------------------------------------------------------
-----------
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] 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 [email protected] More majordomo info at
http://vger.kernel.org/majordomo-info.html
Signature · 19 lines
Sev Binello Brookhaven National Laboratory Upton, New York 631-344-5647 [email protected] ------------------------------------------------------------------------- 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 - [email protected] https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead. http://vger.kernel.org/vger-lists.html#linux-nfs
A message that is not in the archive (sent off-list or not yet received): [email protected]
Re: [NFS] export dir thru 2 diff path names
That is correct, exportfs only shows the actual directory. The client seems to be able to mount the directory with either.
Wayne
Quoted 174 lines
-----Original Message-----
From: Sev Binello [mailto:[email protected]]
Sent: Monday, November 10, 2008 12:51 PM
To: Murata, Dennis
Cc: J. Bruce Fields; [email protected]
Subject: Re: [NFS] export dir thru 2 diff path namesQuoted 1 line · Dennis
I just tested this on a SL4.7 (RHEL 4.7 variant) using a
RHEL 4.4 nfs
Quoted 1 line
server. I did get the messages from exportfs about
duplicate export
Quoted 1 line
entries. On the client I was able to mount both the
symlink and the
Quoted 3 lines
actual directory. They look like separate mounts. There are two entries in
/proc/mountsand in/etc/mtab, one with the actual directory path, one with the symlink path. I am usingautofs to mount
Quoted 2 lines
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.Quoted 1 line
What problems will I cause by doing this? I am using the
symlink path
Quoted 6 lines
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.
Quoted 35 lines
Wayne
Quoted 32 lines
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Sev Binello
Sent: Monday, November 10, 2008 11:06 AM
To: J. Bruce Fields; [email protected]
Subject: Re: [NFS] export dir thru 2 diff path namesQuoted 6 lines · J. Bruce Fields
Quoted 3 lines · Sev Binello
Well the simplest approach doesn't work.
i.e put symb link and actual path in the export file & tryexporting
Quoted 2 lines
Quoted 2 lines
it Exportfs dereferences the link and states that
duplicates are not allowed.
Quoted 6 lines
Quoted 2 lines
OK, makes sense.
You could mount --bind the filesystem at the other location
instead of
Quoted 3 lines
symlinking.
The filehandles given to the client will be the same
across the two
Quoted 1 line
Quoted 1 line
Quoted 1 line
exports. If you mount both from the same client,
behavior may vary
Quoted 88 lines
Quoted 88 lines
Quoted 2 lines
across different clients (for example, as to whether they
attempt to
Quoted 6 lines
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
Quoted 20 lines
--b.
Quoted 16 lines
-Sev
Quoted 11 lines · J. Bruce Fields
Quoted 5 lines · Sev Binello
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
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
out....
If you're exporting something *containing* the symlink
and expecting
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
the client to traverse into the filesystem, be aware that
symlinks
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
over NFS are actually interpreted (and followed) on the
client--so
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
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'dQuoted 4 lines
Quoted 4 lines
Quoted 4 lines
have to try it or check the code.
Another way to export the filesystem in two different
places would
Quoted 16 lines
Quoted 16 lines
Quoted 6 lines
be with mount --bind.
--b.
--
Sev Binello
Brookhaven National Laboratory
Upton, New York
631-344-5647
[email protected]Quoted 4 lines
Quoted 4 lines
--------------------------------------------------------------
-----------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications withMoblin SDK
Quoted 11 lines
Quoted 11 lines
& 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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
Quoted 19 lines
Quoted 2 lines
Quoted 2 lines
--
To unsubscribe from this list: send the line "unsubscribelinux-nfs"
Quoted 1 line
Quoted 1 line
in the body of a message to [email protected] More
majordomo
Quoted 3 lines
Quoted 3 lines
Signature · 5 lines
Sev Binello Brookhaven National Laboratory Upton, New York 631-344-5647 [email protected]
-------------------------------------------------------------------------
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
A message that is not in the archive (sent off-list or not yet received): 620E93B2E5CC3B46BD811165E3335B8702F37542-9/h0XwadXgnyjpQT3Si/[email protected]
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
Quoted 254 lines · Dennis
That is correct, exportfs only shows the actual directory. The client seems to be able to mount the directory with either.
Wayne
Quoted 248 lines
-----Original Message-----
From: Sev Binello [mailto:[email protected]]
Sent: Monday, November 10, 2008 12:51 PM
To: Murata, Dennis
Cc: J. Bruce Fields; [email protected]
Subject: Re: [NFS] export dir thru 2 diff path namesQuoted 2 lines · Dennis
I just tested this on a SL4.7 (RHEL 4.7 variant) using a
RHEL 4.4 nfs
Quoted 2 lines
server. I did get the messages from exportfs about
duplicate export
Quoted 2 lines
entries. On the client I was able to mount both the
symlink and the
Quoted 4 lines
actual directory. They look like separate mounts. There are two entries in
/proc/mountsand in/etc/mtab, one with the actual directory path, one with the symlink path. I am usingautofs to mount
Quoted 3 lines
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.Quoted 2 lines
What problems will I cause by doing this? I am using the
symlink path
Quoted 6 lines
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.
Quoted 46 lines
Wayne
Quoted 42 lines
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Sev Binello
Sent: Monday, November 10, 2008 11:06 AM
To: J. Bruce Fields; [email protected]
Subject: Re: [NFS] export dir thru 2 diff path namesQuoted 8 lines · J. Bruce Fields
Quoted 4 lines · Sev Binello
Well the simplest approach doesn't work.
i.e put symb link and actual path in the export file & tryexporting
Quoted 3 lines
Quoted 3 lines
it Exportfs dereferences the link and states that
duplicates are not allowed.
Quoted 8 lines
Quoted 3 lines
OK, makes sense.
You could mount --bind the filesystem at the other location
instead of
Quoted 4 lines
symlinking.
The filehandles given to the client will be the same
across the two
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
exports. If you mount both from the same client,
behavior may vary
Quoted 110 lines
Quoted 110 lines
Quoted 3 lines
across different clients (for example, as to whether they
attempt to
Quoted 7 lines
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
Quoted 25 lines
--b.
Quoted 20 lines
-Sev
Quoted 14 lines · J. Bruce Fields
Quoted 6 lines · Sev Binello
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
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
out....
If you're exporting something *containing* the symlink
and expecting
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
the client to traverse into the filesystem, be aware that
symlinks
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
over NFS are actually interpreted (and followed) on the
client--so
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
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'dQuoted 5 lines
Quoted 5 lines
Quoted 5 lines
have to try it or check the code.
Another way to export the filesystem in two different
places would
Quoted 18 lines
Quoted 18 lines
Quoted 7 lines
be with mount --bind.
--b.
--
Sev Binello
Brookhaven National Laboratory
Upton, New York
631-344-5647
[email protected]Quoted 5 lines
Quoted 5 lines
--------------------------------------------------------------
-----------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications withMoblin SDK
Quoted 11 lines
Quoted 11 lines
& 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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfsQuoted 3 lines
Quoted 3 lines
--
To unsubscribe from this list: send the line "unsubscribelinux-nfs"
Quoted 2 lines
Quoted 2 lines
in the body of a message to [email protected] More
majordomo
Quoted 4 lines
Quoted 4 lines
Signature · 5 lines
Sev Binello Brookhaven National Laboratory Upton, New York 631-344-5647 [email protected]
-------------------------------------------------------------------------
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
A message that is not in the archive (sent off-list or not yet received): [email protected]
Re: [NFS] export dir thru 2 diff path names
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
Quoted 238 lines
-----Original Message-----
From: Sev Binello [mailto:[email protected]]
Sent: Monday, November 10, 2008 1:04 PM
To: Murata, Dennis
Cc: J. Bruce Fields; [email protected]
Subject: Re: [NFS] export dir thru 2 diff path namesHi -
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
-SevQuoted 1 line · Dennis
That is correct, exportfs only shows the actual directory.
The client
Quoted 33 lines
seems to be able to mount the directory with either.
Wayne
Quoted 28 lines
-----Original Message-----
From: Sev Binello [mailto:[email protected]]
Sent: Monday, November 10, 2008 12:51 PM
To: Murata, Dennis
Cc: J. Bruce Fields; [email protected]
Subject: Re: [NFS] export dir thru 2 diff path namesQuoted 2 lines · Dennis
I just tested this on a SL4.7 (RHEL 4.7 variant) using a
RHEL 4.4 nfs
Quoted 2 lines
server. I did get the messages from exportfs about
duplicate export
Quoted 2 lines
entries. On the client I was able to mount both the
symlink and the
Quoted 4 lines
actual directory. They look like separate mounts. There are two entries in
/proc/mountsand in/etc/mtab, one with the actual directory path, one with the symlink path. I am usingautofs to mount
Quoted 1 line
the directories, not hardcoded. Are you using newer
distributions?
Quoted 7 lines
Quoted 7 lines
Quoted 2 lines
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.Quoted 7 lines
Quoted 7 lines
Quoted 2 lines
What problems will I cause by doing this? I am using the
symlink path
Quoted 3 lines
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
Quoted 68 lines
Quoted 68 lines
Quoted 49 lines
applications that reference the application will always use the symlink path, as well as any user scripts.
Wayne
Quoted 42 lines
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Sev Binello
Sent: Monday, November 10, 2008 11:06 AM
To: J. Bruce Fields; [email protected]
Subject: Re: [NFS] export dir thru 2 diff path namesQuoted 8 lines · J. Bruce Fields
Quoted 4 lines · Sev Binello
Well the simplest approach doesn't work.
i.e put symb link and actual path in the export file & tryexporting
Quoted 3 lines
Quoted 3 lines
it Exportfs dereferences the link and states that
duplicates are not allowed.
Quoted 8 lines
Quoted 3 lines
OK, makes sense.
You could mount --bind the filesystem at the other location
instead of
Quoted 4 lines
symlinking.
The filehandles given to the client will be the same
across the two
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
exports. If you mount both from the same client,
behavior may vary
Quoted 13 lines
Quoted 13 lines
Quoted 3 lines
across different clients (for example, as to whether they
attempt to
Quoted 7 lines
share caches between the two), but I think it'd work.
(The question "why??!!??" does come to mind, though.)
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
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 alsomount the
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
same file system, wanted to see if we could let them
stay the way
Quoted 91 lines
Quoted 91 lines
Quoted 91 lines
Quoted 91 lines
they were for now.
We're just going to go ahead and have to coordinate this with windows guys.
-Sev
Quoted 25 lines
--b.
Quoted 20 lines
-Sev
Quoted 14 lines · J. Bruce Fields
Quoted 6 lines · Sev Binello
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
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
out....
If you're exporting something *containing* the symlink
and expecting
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
the client to traverse into the filesystem, be aware that
symlinks
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
over NFS are actually interpreted (and followed) on the
client--so
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
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'dQuoted 5 lines
Quoted 5 lines
Quoted 5 lines
have to try it or check the code.
Another way to export the filesystem in two different
places would
Quoted 18 lines
Quoted 18 lines
Quoted 7 lines
be with mount --bind.
--b.
--
Sev Binello
Brookhaven National Laboratory
Upton, New York
631-344-5647
[email protected]Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
--------------------------------------------------------------
-----------
This SF.Net email is sponsored by the Moblin Your Move
Quoted 42 lines
Developer's
Quoted 5 lines
Quoted 5 lines
Quoted 2 lines
Quoted 2 lines
challenge Build the coolest Linux based applications with
Moblin SDK
Quoted 1 line
Quoted 1 line
& win great prizes Grand prize is a trip for two to an
Open Source
Quoted 33 lines
Quoted 33 lines
Quoted 10 lines
Quoted 10 lines
event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfsQuoted 3 lines
Quoted 3 lines
--
To unsubscribe from this list: send the line "unsubscribelinux-nfs"
Quoted 2 lines
Quoted 2 lines
in the body of a message to [email protected] More
majordomo
Quoted 4 lines
Quoted 4 lines
--
Sev Binello
Brookhaven National Laboratory
Upton, New York
631-344-5647
[email protected]
-------------------------------------------------------------------------
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
A message that is not in the archive (sent off-list or not yet received): 620E93B2E5CC3B46BD811165E3335B8702F3759D-9/h0XwadXgnyjpQT3Si/[email protected]
Re: [NFS] export dir thru 2 diff path names
Quoted 5 lines · Dennis
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.
Quoted 283 lines
Wayne
Quoted 280 lines
-----Original Message-----
From: Sev Binello [mailto:[email protected]]
Sent: Monday, November 10, 2008 1:04 PM
To: Murata, Dennis
Cc: J. Bruce Fields; [email protected]
Subject: Re: [NFS] export dir thru 2 diff path namesHi -
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
-SevQuoted 1 line · Dennis
That is correct, exportfs only shows the actual directory.
The client
Quoted 33 lines
seems to be able to mount the directory with either.
Wayne
Quoted 28 lines
-----Original Message-----
From: Sev Binello [mailto:[email protected]]
Sent: Monday, November 10, 2008 12:51 PM
To: Murata, Dennis
Cc: J. Bruce Fields; [email protected]
Subject: Re: [NFS] export dir thru 2 diff path namesQuoted 2 lines · Dennis
I just tested this on a SL4.7 (RHEL 4.7 variant) using a
RHEL 4.4 nfs
Quoted 2 lines
server. I did get the messages from exportfs about
duplicate export
Quoted 2 lines
entries. On the client I was able to mount both the
symlink and the
Quoted 4 lines
actual directory. They look like separate mounts. There are two entries in
/proc/mountsand in/etc/mtab, one with the actual directory path, one with the symlink path. I am usingautofs to mount
Quoted 1 line
the directories, not hardcoded. Are you using newer
distributions?
Quoted 7 lines
Quoted 7 lines
Quoted 2 lines
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.Quoted 7 lines
Quoted 7 lines
Quoted 2 lines
What problems will I cause by doing this? I am using the
symlink path
Quoted 3 lines
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
Quoted 68 lines
Quoted 68 lines
Quoted 49 lines
applications that reference the application will always use the symlink path, as well as any user scripts.
Wayne
Quoted 42 lines
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Sev Binello
Sent: Monday, November 10, 2008 11:06 AM
To: J. Bruce Fields; [email protected]
Subject: Re: [NFS] export dir thru 2 diff path namesQuoted 8 lines · J. Bruce Fields
Quoted 4 lines · Sev Binello
Well the simplest approach doesn't work.
i.e put symb link and actual path in the export file & tryexporting
Quoted 3 lines
Quoted 3 lines
it Exportfs dereferences the link and states that
duplicates are not allowed.
Quoted 8 lines
Quoted 3 lines
OK, makes sense.
You could mount --bind the filesystem at the other location
instead of
Quoted 4 lines
symlinking.
The filehandles given to the client will be the same
across the two
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
exports. If you mount both from the same client,
behavior may vary
Quoted 13 lines
Quoted 13 lines
Quoted 3 lines
across different clients (for example, as to whether they
attempt to
Quoted 7 lines
share caches between the two), but I think it'd work.
(The question "why??!!??" does come to mind, though.)
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
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 alsomount the
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
same file system, wanted to see if we could let them
stay the way
Quoted 91 lines
Quoted 91 lines
Quoted 91 lines
Quoted 91 lines
they were for now.
We're just going to go ahead and have to coordinate this with windows guys.
-Sev
Quoted 25 lines
--b.
Quoted 20 lines
-Sev
Quoted 14 lines · J. Bruce Fields
Quoted 6 lines · Sev Binello
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
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
out....
If you're exporting something *containing* the symlink
and expecting
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
the client to traverse into the filesystem, be aware that
symlinks
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
over NFS are actually interpreted (and followed) on the
client--so
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
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'dQuoted 5 lines
Quoted 5 lines
Quoted 5 lines
have to try it or check the code.
Another way to export the filesystem in two different
places would
Quoted 18 lines
Quoted 18 lines
Quoted 7 lines
be with mount --bind.
--b.
--
Sev Binello
Brookhaven National Laboratory
Upton, New York
631-344-5647
[email protected]Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
--------------------------------------------------------------
-----------
This SF.Net email is sponsored by the Moblin Your MoveDeveloper's
Quoted 5 lines
Quoted 5 lines
Quoted 2 lines
Quoted 2 lines
challenge Build the coolest Linux based applications with
Moblin SDK
Quoted 1 line
Quoted 1 line
& win great prizes Grand prize is a trip for two to an
Open Source
Quoted 33 lines
Quoted 33 lines
Quoted 10 lines
Quoted 10 lines
event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfsQuoted 3 lines
Quoted 3 lines
--
To unsubscribe from this list: send the line "unsubscribelinux-nfs"
Quoted 2 lines
Quoted 2 lines
in the body of a message to [email protected] More
majordomo
Quoted 4 lines
Quoted 4 lines
--
Sev Binello
Brookhaven National Laboratory
Upton, New York
631-344-5647
[email protected]
-------------------------------------------------------------------------
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
Re: [NFS] export dir thru 2 diff path names
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.
Quoted 9 lines · J. Bruce Fields
Quoted 6 lines · Dennis
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.
Quoted 364 lines
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.
Quoted 355 lines
Wayne
Quoted 352 lines
-----Original Message-----
From: Sev Binello [mailto:[email protected]]
Sent: Monday, November 10, 2008 1:04 PM
To: Murata, Dennis
Cc: J. Bruce Fields; [email protected]
Subject: Re: [NFS] export dir thru 2 diff path namesHi -
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
-SevQuoted 2 lines · Dennis
That is correct, exportfs only shows the actual directory.
The client
Quoted 44 lines
seems to be able to mount the directory with either.
Wayne
Quoted 38 lines
-----Original Message-----
From: Sev Binello [mailto:[email protected]]
Sent: Monday, November 10, 2008 12:51 PM
To: Murata, Dennis
Cc: J. Bruce Fields; [email protected]
Subject: Re: [NFS] export dir thru 2 diff path namesQuoted 3 lines · Dennis
I just tested this on a SL4.7 (RHEL 4.7 variant) using a
RHEL 4.4 nfs
Quoted 3 lines
server. I did get the messages from exportfs about
duplicate export
Quoted 3 lines
entries. On the client I was able to mount both the
symlink and the
Quoted 5 lines
actual directory. They look like separate mounts. There are two entries in
/proc/mountsand in/etc/mtab, one with the actual directory path, one with the symlink path. I am usingautofs to mount
Quoted 2 lines
the directories, not hardcoded. Are you using newer
distributions?
Quoted 12 lines
Quoted 12 lines
Quoted 3 lines
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.Quoted 3 lines
What problems will I cause by doing this? I am using the
Quoted 7 lines
Quoted 7 lines
symlink path
Quoted 4 lines
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
Quoted 85 lines
Quoted 85 lines
Quoted 60 lines
applications that reference the application will always use the symlink path, as well as any user scripts.
Wayne
Quoted 52 lines
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Sev Binello
Sent: Monday, November 10, 2008 11:06 AM
To: J. Bruce Fields; [email protected]
Subject: Re: [NFS] export dir thru 2 diff path namesQuoted 10 lines · J. Bruce Fields
Quoted 5 lines · Sev Binello
Well the simplest approach doesn't work.
i.e put symb link and actual path in the export file & tryexporting
Quoted 4 lines
Quoted 4 lines
it Exportfs dereferences the link and states that
duplicates are not allowed.
Quoted 10 lines
Quoted 4 lines
OK, makes sense.
You could mount --bind the filesystem at the other location
instead of
Quoted 5 lines
symlinking.
The filehandles given to the client will be the same
across the two
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
exports. If you mount both from the same client,
behavior may vary
Quoted 16 lines
Quoted 16 lines
Quoted 4 lines
across different clients (for example, as to whether they
attempt to
Quoted 8 lines
share caches between the two), but I think it'd work.
(The question "why??!!??" does come to mind, though.)
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
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 alsomount the
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
same file system, wanted to see if we could let them
stay the way
Quoted 110 lines
Quoted 110 lines
Quoted 110 lines
Quoted 110 lines
they were for now.
We're just going to go ahead and have to coordinate this with windows guys.
-Sev
Quoted 30 lines
--b.
Quoted 24 lines
-Sev
Quoted 17 lines · J. Bruce Fields
Quoted 7 lines · Sev Binello
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
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
out....
If you're exporting something *containing* the symlink
and expecting
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
the client to traverse into the filesystem, be aware that
symlinks
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
over NFS are actually interpreted (and followed) on the
client--so
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
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'dQuoted 6 lines
Quoted 6 lines
Quoted 6 lines
have to try it or check the code.
Another way to export the filesystem in two different
places would
Quoted 20 lines
Quoted 20 lines
Quoted 8 lines
be with mount --bind.
--b.
--
Sev Binello
Brookhaven National Laboratory
Upton, New York
631-344-5647
[email protected]Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
--------------------------------------------------------------
-----------
This SF.Net email is sponsored by the Moblin Your MoveDeveloper's
Quoted 8 lines
Quoted 8 lines
Quoted 3 lines
Quoted 3 lines
challenge Build the coolest Linux based applications with
Moblin SDK
Quoted 2 lines
Quoted 2 lines
& win great prizes Grand prize is a trip for two to an
Open Source
Quoted 39 lines
Quoted 39 lines
Quoted 10 lines
Quoted 10 lines
event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfsQuoted 4 lines
Quoted 4 lines
--
To unsubscribe from this list: send the line "unsubscribelinux-nfs"
Quoted 3 lines
Quoted 3 lines
in the body of a message to [email protected] More
majordomo
Quoted 5 lines
Quoted 5 lines
--
Sev Binello
Brookhaven National Laboratory
Upton, New York
631-344-5647
[email protected]
-------------------------------------------------------------------------
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
Re: [NFS] export dir thru 2 diff path names
In reply to J. Bruce FieldsQuoted 9 lines · J. Bruce Fields
Quoted 7 lines · Dennis
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.
Quoted 6 lines
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?
Quoted 309 lines
--b.
Quoted 285 lines
Wayne
Quoted 282 lines
-----Original Message-----
From: Sev Binello [mailto:[email protected]]
Sent: Monday, November 10, 2008 1:04 PM
To: Murata, Dennis
Cc: J. Bruce Fields; [email protected]
Subject: Re: [NFS] export dir thru 2 diff path namesHi -
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
-SevQuoted 1 line · Dennis
That is correct, exportfs only shows the actual directory.
The client
Quoted 33 lines
seems to be able to mount the directory with either.
Wayne
Quoted 28 lines
-----Original Message-----
From: Sev Binello [mailto:[email protected]]
Sent: Monday, November 10, 2008 12:51 PM
To: Murata, Dennis
Cc: J. Bruce Fields; [email protected]
Subject: Re: [NFS] export dir thru 2 diff path namesQuoted 2 lines · Dennis
I just tested this on a SL4.7 (RHEL 4.7 variant) using a
RHEL 4.4 nfs
Quoted 2 lines
server. I did get the messages from exportfs about
duplicate export
Quoted 2 lines
entries. On the client I was able to mount both the
symlink and the
Quoted 4 lines
actual directory. They look like separate mounts. There are two entries in
/proc/mountsand in/etc/mtab, one with the actual directory path, one with the symlink path. I am usingautofs to mount
Quoted 1 line
the directories, not hardcoded. Are you using newer
distributions?
Quoted 7 lines
Quoted 7 lines
Quoted 2 lines
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.Quoted 7 lines
Quoted 7 lines
Quoted 2 lines
What problems will I cause by doing this? I am using the
symlink path
Quoted 3 lines
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
Quoted 69 lines
Quoted 69 lines
Quoted 50 lines
applications that reference the application will always use the symlink path, as well as any user scripts.
Wayne
Quoted 43 lines
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Sev Binello
Sent: Monday, November 10, 2008 11:06 AM
To: J. Bruce Fields; [email protected]
Subject: Re: [NFS] export dir thru 2 diff path namesQuoted 8 lines · J. Bruce Fields
Quoted 4 lines · Sev Binello
Well the simplest approach doesn't work.
i.e put symb link and actual path in the export file & tryexporting
Quoted 3 lines
Quoted 3 lines
it Exportfs dereferences the link and states that
duplicates are not allowed.
Quoted 8 lines
Quoted 3 lines
OK, makes sense.
You could mount --bind the filesystem at the other location
instead of
Quoted 4 lines
symlinking.
The filehandles given to the client will be the same
across the two
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
exports. If you mount both from the same client,
behavior may vary
Quoted 13 lines
Quoted 13 lines
Quoted 3 lines
across different clients (for example, as to whether they
attempt to
Quoted 7 lines
share caches between the two), but I think it'd work.
(The question "why??!!??" does come to mind, though.)
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
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 alsomount the
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
same file system, wanted to see if we could let them
stay the way
Quoted 91 lines
Quoted 91 lines
Quoted 91 lines
Quoted 91 lines
they were for now.
We're just going to go ahead and have to coordinate this with windows guys.
-Sev
Quoted 25 lines
--b.
Quoted 20 lines
-Sev
Quoted 14 lines · J. Bruce Fields
Quoted 6 lines · Sev Binello
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
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
out....
If you're exporting something *containing* the symlink
and expecting
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
the client to traverse into the filesystem, be aware that
symlinks
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
over NFS are actually interpreted (and followed) on the
client--so
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
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'dQuoted 5 lines
Quoted 5 lines
Quoted 5 lines
have to try it or check the code.
Another way to export the filesystem in two different
places would
Quoted 18 lines
Quoted 18 lines
Quoted 7 lines
be with mount --bind.
--b.
--
Sev Binello
Brookhaven National Laboratory
Upton, New York
631-344-5647
[email protected]Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
--------------------------------------------------------------
-----------
This SF.Net email is sponsored by the Moblin Your MoveDeveloper's
Quoted 5 lines
Quoted 5 lines
Quoted 2 lines
Quoted 2 lines
challenge Build the coolest Linux based applications with
Moblin SDK
Quoted 1 line
Quoted 1 line
& win great prizes Grand prize is a trip for two to an
Open Source
Quoted 34 lines
Quoted 34 lines
Quoted 11 lines
Quoted 11 lines
event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued.
Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfsQuoted 3 lines
Quoted 3 lines
--
To unsubscribe from this list: send the line "unsubscribelinux-nfs"
Quoted 2 lines
Quoted 2 lines
in the body of a message to [email protected] More
majordomo
Quoted 4 lines
Quoted 4 lines
--
Sev Binello
Brookhaven National Laboratory
Upton, New York
631-344-5647
[email protected]-------------------------------------------------------------------------
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] 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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 19 lines
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 - [email protected] https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead. http://vger.kernel.org/vger-lists.html#linux-nfs
Re: [NFS] export dir thru 2 diff path names
Quoted 12 lines · Chuck Lever
Quoted 11 lines · J. Bruce Fields
Quoted 7 lines · Dennis
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.
Quoted 8 lines
Quoted 4 lines
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
Re: [NFS] export dir thru 2 diff path names
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
Quoted 30 lines
-----Original Message-----
From: J. Bruce Fields [mailto:[email protected]]
Sent: Monday, November 10, 2008 2:45 PM
To: Chuck Lever
Cc: Murata, Dennis; [email protected]; Sev Binello
Subject: Re: [NFS] export dir thru 2 diff path namesQuoted 5 lines · Chuck Lever
Quoted 4 lines · J. Bruce Fields
Quoted 3 lines · Dennis
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
Quoted 1 line
Quoted 1 line
Quoted 1 line
messages log file on the server the mount request from
the client is
Quoted 6 lines
Quoted 6 lines
Quoted 1 line
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
Quoted 4 lines
Quoted 1 line
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
Quoted 1 line
shared page cache for both?
Quoted 9 lines
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
A message that is not in the archive (sent off-list or not yet received): 620E93B2E5CC3B46BD811165E3335B8702FD3423-9/h0XwadXgnyjpQT3Si/[email protected]
Re: [NFS] export dir thru 2 diff path names
Quoted 2 lines · Dennis
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.
Quoted 59 lines
I would hate to
recommend use of the exported link, only to have it disabled by an updated patch.Wayne
Quoted 30 lines
-----Original Message-----
From: J. Bruce Fields [mailto:[email protected]]
Sent: Monday, November 10, 2008 2:45 PM
To: Chuck Lever
Cc: Murata, Dennis; [email protected]; Sev Binello
Subject: Re: [NFS] export dir thru 2 diff path namesQuoted 5 lines · Chuck Lever
Quoted 4 lines · J. Bruce Fields
Quoted 3 lines · Dennis
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
Quoted 1 line
Quoted 1 line
Quoted 1 line
messages log file on the server the mount request from
the client is
Quoted 6 lines
Quoted 6 lines
Quoted 1 line
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
Quoted 4 lines
Quoted 1 line
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
Quoted 1 line
shared page cache for both?
Quoted 9 lines
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
Quoted 4 lines
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected]
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
Re: [NFS] export dir thru 2 diff path names
Quoted 12 lines
-----Original Message-----
From: J. Bruce Fields [mailto:[email protected]]
Sent: Sunday, November 16, 2008 2:04 PM
To: Murata, Dennis
Cc: Chuck Lever; [email protected]; Sev Binello
Subject: Re: [NFS] export dir thru 2 diff path namesQuoted 2 lines · Dennis
One last question for the maintainers and the community. Is this viewed as an undocumented feature or a bug to be fixed?
Quoted 8 lines
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
Quoted 69 lines
Quoted 16 lines
I would hate to
recommend use of the exported link, only to have it disabled by an updated patch.Wayne
Quoted 9 lines
-----Original Message-----
From: J. Bruce Fields [mailto:[email protected]]
Sent: Monday, November 10, 2008 2:45 PM
To: Chuck Lever
Cc: Murata, Dennis; [email protected]; Sev Binello
Subject: Re: [NFS] export dir thru 2 diff path namesQuoted 1 line · Chuck Lever
On Nov 10, 2008, at Nov 10, 2008, 2:28 PM, J. Bruce
Quoted 2 lines · Fields
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines · Dennis
Quoted 1 line
That really is the 64K question. During my initial
testing, I
Quoted 7 lines
Quoted 7 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
exported the parent directory. Now I am explicitly exporting the installation directories, where I see the exportfs
message. In the
Quoted 1 line
Quoted 1 line
Quoted 1 line
messages log file on the server the mount request from
the client is
Quoted 2 lines
Quoted 2 lines
Quoted 1 line
always the actual directory.
Quoted 8 lines
Quoted 8 lines
Quoted 4 lines
Quoted 4 lines
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
Quoted 3 lines
Quoted 1 line
and one of them writeable, for example, you'll be disapointed.
I wonder how this behaves on the client side. If the
same client
Quoted 9 lines
Quoted 9 lines
Quoted 1 line
mounts both paths, will it recognize that these are the
same and use a
Quoted 1 line
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
Quoted 6 lines
Quoted 4 lines
to mount both paths from the same client at once.)
--b.
----------------------------------------------------------------------
Quoted 1 line
--- This SF.Net email is sponsored by the Moblin Your Move
Developer's
Quoted 1 line
challenge Build the coolest Linux based applications with
Moblin SDK &
Quoted 1 line
win great prizes Grand prize is a trip for two to an Open
Source event
Quoted 10 lines
anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
Quoted 7 lines
Quoted 2 lines
--
To unsubscribe from this list: send the line "unsubscribelinux-nfs"
Quoted 1 line
in the body of a message to [email protected] More
majordomo
Quoted 1 line
-------------------------------------------------------------------------
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
Re: [NFS] export dir thru 2 diff path names
In reply to a message not in the archiveQuoted 4 lines · Dennis
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.
Quoted 42 lines
Wayne
Quoted 39 lines
-----Original Message-----
From: J. Bruce Fields [mailto:[email protected]]
Sent: Monday, November 10, 2008 2:45 PM
To: Chuck Lever
Cc: Murata, Dennis; [email protected]; Sev Binello
Subject: Re: [NFS] export dir thru 2 diff path namesQuoted 5 lines · Chuck Lever
Quoted 4 lines · J. Bruce Fields
Quoted 3 lines · Dennis
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
Quoted 1 line
Quoted 1 line
Quoted 1 line
messages log file on the server the mount request from
the client is
Quoted 6 lines
Quoted 6 lines
Quoted 1 line
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
Quoted 4 lines
Quoted 1 line
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
Quoted 1 line
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs