From: David Cureton <david.cureton@catapult.com>
To: Murray Trainer <mtrainer@central-data.net>
Cc: NFS Mailing List <nfs@lists.sourceforge.net>
Subject: Re: Accessing other shares from NFS mounted home directories
Date: Tue, 10 May 2005 09:39:40 +1000 [thread overview]
Message-ID: <427FF4BC.2090705@catapult.com> (raw)
In-Reply-To: <1115647866.21417.51.camel@vserver.central-data.net>
Hi Murray,
If I understand you, what you are trying to do is mount NFS
filesystems on mount points that are itself an nfs filesystem.
We are currently do just this and it appears to work OK. We are having
one slight isolated problem with a symbolic link going missing however
this may or may not be due to mounting the mountpoints via NFS.
Basically here I export the directory:
/server
which contains the directorys (which I use as mount points for the
actual disk patitions of the server and as NFS mountpoint on the client)
/server/volumes/vol1
/server/volumes/vol2
/server/volumes/vol3
Then on the clients I go about mounting the NFS mounts onto these volX
mount points.
Therefore out fstab on a client machine looks like:
##client specific stuff##
...
melbourne-fs3:/server /server nfs defaults 0 2
melbourne-fs3:/server/volumes/vol2 /server/volumes/vol2 nfs
defaults 0 2
melbourne-fs3:/server/volumes/vol1 /server/volumes/vol1 nfs
defaults 0 2
melbourne-fs3:/server/volumes/vol0 /server/volumes/vol0 nfs
defaults 0 2
The fstab looks a little confusing with all the '/server/volumes/' but
just remember that the
'melbourne-fs3:/server/volumes/volx' are where physcal disk partitions
have been mounted on the
server and the '/server/volumes/volx' mount points are mounting those
same physical patitions on
the Linux client machines via NFS.
We use SuSE 9.2 Professional for Clients and Server.
Hope this is of value to you,
Regards,
David
Murray Trainer wrote:
>Hi All,
>
>We mount /home on our front end Linux machines via NFS from a backend
>Linux NFS file server. This is nice and simple and reliable so far. We
>want our user's to be able to access other shares but make them appear
>under their home directory, eg mount remote_share under
>/home/username/Shares/remote_share. We could use automount or pam_mount
>to do the mounting when the user logs in. But the problem is
>that, unless there is some trick or new feature I am unaware of, NFS
>doesn't appear to be able to mount remote filesystems under these NFS
>home directories on the front-end Linux NFS client machine.
>
>Mounting the remote filesystems elsewhere on the server and using
>symbolic links to point to make them appear to be under the user's home
>directory appears to be the only solution. If anyone knows of a better
>way to achieve this I would greatly appreciate hearing about it. If we
>go the symbolic links way, automating the process of creating the mounts
>and the symbolic links appears to be messy. It was also suggested to me
>that I use the mount with the --bind option but I can't see how this
>would allow me to achieve mounts under the home directory. Automount
>may be another option but I not that familiar with it.
>
>Does anyone have any suggestions on how best to implement a solution for
>the above situation?
>
>Thanks
>
>Murray
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: NEC IT Guy Games.
>Get your fingers limbered up and give it your best shot. 4 great events, 4
>opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
>win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
>_______________________________________________
>NFS maillist - NFS@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/nfs
>
>
>
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2005-05-09 23:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 14:11 Accessing other shares from NFS mounted home directories Murray Trainer
2005-05-09 23:39 ` David Cureton [this message]
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=427FF4BC.2090705@catapult.com \
--to=david.cureton@catapult.com \
--cc=mtrainer@central-data.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.