Re: [tlug] NFS export issue

[chris mague <chris@example.com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

To find out which processes are mounting /home you can use fstat or fuser
(depending upon the OS) on the client.  Kill these proceeses to unmount
the directory.

Is the user ID or jmglov 141 (and how are you keeping track of users?).

Instead of hard mounting you may wish to look into using amd or something
to control mounts of the directories.  This will make things easier if you
are looking to expand.  amd also runs on Solaris/BSD/Linux and there are
also amutils can be used to convert the Solaris maps to amd style.


- -c


- --------------------------
Chris Mague

On Sat, 16 Mar 2002, Josh Glover wrote:

>
> drwxrwxr-x    2 141      bin           512 Mar 16 10:35 jmglov
> drwxrwxr-x   40 john     bin          3072 Mar 13 15:36 john
> drwxrwxr-x    5 137      bin           512 Feb 21 08:38 judith
> drwxrwxr-x    7 kellyw   bin           512 Dec 13 09:21 kellyw
>
> Two of these users, john and kellyw, can happily use their homespace.
> The other two, jmglov and judith, cannot, as they do not own their
> homespace. The question is, why not? and where does the 141 come from?
> On the server, /home looks like:
>
> drwxrwxr-x   2 jmglov   users        512 Mar 16 10:35 jmglov
> drwxrwxr-x  40 john     users       3072 Mar 16 11:10 john
> drwxrwxr-x   5 judith   users        512 Feb 21 08:38 judith
> drwxrwxr-x   7 kellyw   users        512 Mar 16 11:11 kellyw
>
> As one might expect, jmglov's homespace works fine on the server. I have
> tried restarting the NFS server, but that did nothing.
>
> Back on the client, mount reports that /home is being mounted rw:
>
> jabba:/home on /home type nfs (rw,hard,intr,addr=XXX.XXX.XXX.XXX)
>
> (IP address censored to protect the guilty)
>
> I cannot umount /home, as umount always reports that /home is busy, even
> when I stop the NFS server. Strange. I cannot force it, but I can umount
> -r and have it mounted readonly. Which buys me nothing.
>
> So I am out of ideas, for now. What I have not done is restarted the
> client. I would rather not, as it is a high availability machine. And I
> should not have to.
>
> Any suggestions?
>
>
> --
> Josh Glover <jmglov@example.com>
>
> Computer Science Undergrad
> "No segfault, no problem!"
>
>
-----BEGIN PGP SIGNATURE-----

iD8DBQE8lFgPgUQV0DCQirkRAinEAKCOHG2M0ds3bnS1ujcohtA+oOdqvACfZ+cM
t5S7n7zwtjME6iQ8ZBKPpoE=
=GlNt
-----END PGP SIGNATURE-----