Ownership problem with NFS exported /home
David M. Bucknell
david at rose-marie.ac.th
Tue Sep 21 00:53:07 UTC 2004
Hi,
We do this:
manual mount:
mount -o rw,bg,intr,soft servername:/home /home
or we put this in fstab
servername:/home /home nfs rw,bg,intr,soft 0 0
This is quick and perhaps dirty but it gives every user his/her home upon login
from anywhere on campus.
David
Quoting Robert Locke <rlocke at ralii.com>:
> On Mon, 2004-09-20 at 19:10, CB wrote:
> > On Tue, 2004-09-21 at 00:49, David L Norris wrote:
> > > On Mon, 2004-09-20 at 21:02 +1000, CB wrote:
> > > > /home-ext/<username>
> > > >
>
192.168.0.1/24(rw,wdelay,insecure,root_squash,no_subtree_check,fsid=0,anonuid=65563,anongid=65535)
> > >
> > > > Anyone know what I am doing wrong, or can suggest how to troubleshoot
> > > > further?
> > >
> > > What's with all the options? Have you tried exporting the home
> > > directory using simple options? Just divide and conquer the options
> > > until you find the one that is causing your problem.
> > >
> > > This should always work:
> > > /home 192.168.0.0/255.255.255.0(rw,root_squash)
> >
> > For some reason on my (FC2) system, the fsid option is necessary, but I
> > can get away without the other options, at least for testing purposes.
> > So that leaves me with:
> >
> > /home 192.168.0.0/255.255.255.0(rw,root_squash,fsid=0)
> >
> > (Without the fsid, I can't connect the client).
> >
>
> I am not sure why the fsid option would be affecting you that way....
> Your client really should be able to connect whether you use fsid or
> not... Do you have other things in the exports file? That seems to be
> what fsid is more for to differentiate between exports and to address
> what I thought were some bugs where the fsid changes on us creating
> inode mismatches.... Try to change your exports to be only this item
> and see if it impacts....
>
> Of course, perhaps we are looking at this from the wrong side. What are
> you using to mount from the client (options, etc)???
>
> > But whichever options I do or don't use, I'm still finding that the UID
> > and GID of all files and dirs shown by ls -n in the user's home
> > directory once connected are 0 and 1 respectively, whereas on the server
> > they are 500 and 500. The upshot is that the user on the remote machine
> > only has read access to most of the home directory.
> >
> > Why would the UID and GID be different on the NFS and client machines?
> >
>
> Only if we are doing some sort of "mapping...", but that is usually
> forced onto "anonymous" connections - hence your earlier anonuid and
> anongid uses....
>
> I really think your requirement of the fsid option is indicative of some
> other fundamental problem. Have you changed anything in /etc/sysconfig
> related to nfs or added anything to /etc/sysctl.conf?
>
> --Rob
>
>
> --
> fedora-list mailing list
> fedora-list at redhat.com
> To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
>
Assistant Academic Director and
Technology Department Head
Rose Marie Academy
http://www.rose-marie.ac.th
http://www.fsf.org/philosophy/no-word-attachments.html
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
More information about the fedora-list
mailing list