quota/indirection problem

quota/indirection problem

[Matt Bernstein]

Hi,

This is a little difficult to describe, but is quite a nasty problem.

Our home directories are defined as being
	/homes/$LOGNAME
which (via an autofs bind mount) abstracts to
	:/home/server/volume [1]
which in turn (another autofs bind mount) abstracts to
	:/server/SERVERNAME/PATH
which is an autofs NFS mount.


Now, at first this all works swimmingly and when I log in df tells me what 
I wanted:

cream:/export61       48078504  42604528   3031696  94% /server/cream/export61
/server/cream/export61/users
                      48078504  42604528   3031696  94% /home/cream/home61
/home/cream/home61/mb
                      48078504  42604528   3031696  94% /homes/mb

..and my quota works perfectly:

Disk quotas for user mb (uid 5154):
     Filesystem  blocks    quota   limit   grace   files   quota   limit   grace
cream:/export61  753432  3000000 7000000           16290       0       0

However, after the timeout kicks in only the "/homes/mb" mount is visible 
to df--I guess Deep VFS Magick keeps everything internally in order, and 
my home directory still works fine. BUT..

Disk quotas for user mb (uid 5154): none

SO.. I would really like the NFS mount to persist so that the "quota" 
command produces the output you'd expect.

Can anyone help? Please.. before our students come back and ruin everything..

Our machines use autofs 3. I'm happy to try out bleeding-edge software 
on client machines if anyone thinks it might help..

Matt


[1] The idea is that "/home/server/path" can be different for different
networks, ie our staff machines can have an auto.master like this:

/homes          ldap:ou=auto.homes
/homes.itl      ldap:ou=auto.homes.itl

..and on the "itl" network, like this:

/homes          ldap:ou=auto.homes.itl

Both master maps include:

/server/cream   ldap:ou=auto.server.cream
/server/custard ldap:ou=auto.server.custard
/home/cream     ldap:ou=auto.home.cream
/home/custard   ldap:ou=auto.home.custard

Re: quota/indirection problem

[H. Peter Anvin]

Matt Bernstein wrote:
> 
> However, after the timeout kicks in only the "/homes/mb" mount is visible 
> to df--I guess Deep VFS Magick keeps everything internally in order, and 
> my home directory still works fine. BUT..
> 
> Disk quotas for user mb (uid 5154): none
> 
> SO.. I would really like the NFS mount to persist so that the "quota" 
> command produces the output you'd expect.
> 
> Can anyone help? Please.. before our students come back and ruin everything..
> 

Set timeout to zero, so it never times out.

	-hpa