On Fri, 2009-05-08 at 08:10 +0200, Roger Marcus wrote:
> Hi,
>
> I am having a problem with NFS and I thought that you could help me or
> you could steer me to
> someone who might be able to.
>
> The problem is this:
>
> An NFS Server mounts an image on a local directory, containing a XEN
> virtual machine configuration file and a XEN image.
>
> An NFS Client computer sees the directory that was mounted remotely
> and starts the XEN Virtual machine on the mounted directory.
> The NFS Client computer then stops the XEN Virtual machine. So far, so
> good. The machine ran. It stopped. The NFS Client
> leaves the directory. No process is accessing that directory from the
> client side.
It is still exported, so the NFS server still has a reference to it.
> Problem: The NFS Server cannot umount the local directory.
> fuser returns no usage of the directory.
> lsof returns no usage of the directory.
correction: lsof and fuser don't show any _user processes_ that
reference the directory. NFSd runs in the kernel...
> umount -f won't force umount the directory.
>
> What does work is exportfs -ua.
or 'exportfs -u client:/directory'. See 'man exportfs'
> This is not a good way to go, since it is planned that many clients
> will be using the server; indeed many
> clients will be using multiple subdirectories on the server.
>
> 1. Is this a XEN bug or an NFS bug?
> 2. Is there some other command like exportfs in which you can just
> disable the one local directory but maintain an
> active mount on the parent directory?
See above.
Note that if you want to unexport all export entries for a particular
directory '/mydir', then something like this simple script will do it:
exportfs -u $(exportfs | awk '/^\/mydir/ { print $2 ":" $1; }')
Trond
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
