public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Roger Marcus <roger.marcus@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Problem with NFS and XEN
Date: Fri, 08 May 2009 08:24:01 -0400	[thread overview]
Message-ID: <1241785441.19651.28.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <c4838b6b0905072310g5658ed91i486797b76c8d95d3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

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


  parent reply	other threads:[~2009-05-08 12:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-08  6:10 Problem with NFS and XEN Roger Marcus
     [not found] ` <4A03DBFB.8010407@symantec.com>
2009-05-08  8:11   ` Roger Marcus
     [not found] ` <c4838b6b0905072310g5658ed91i486797b76c8d95d3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-05-08 12:24   ` Trond Myklebust [this message]
     [not found]     ` <1241785441.19651.28.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-05-08 13:11       ` Roger Marcus
     [not found]         ` <c4838b6b0905080611n3ef3f2efr3e843836b1e3dd-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-05-08 13:43           ` Trond Myklebust
     [not found]             ` <1241790224.19651.40.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-05-08 14:32               ` Roger Marcus
     [not found]                 ` <c4838b6b0905080732v7f693436md49bc6dcdca5d6d9-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-05-08 17:18                   ` J. Bruce Fields

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=1241785441.19651.28.camel@heimdal.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=linux-nfs@vger.kernel.org \
    --cc=roger.marcus@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox