From: Neil Brown <neilb@suse.de>
To: rasca-9B074fXSGsOr88ip1nKoZ2D2FQJk+8+b@public.gmane.org
Cc: linux-nfs@vger.kernel.org
Subject: Re: Problem using exportfs in an active-active nfs cluster
Date: Wed, 9 Jun 2010 18:04:39 +1000 [thread overview]
Message-ID: <20100609180439.40e856ac@notabene.brown> (raw)
In-Reply-To: <4C0F4634.8090102-9B074fXSGsOr88ip1nKoZ2D2FQJk+8+b@public.gmane.org>
On Wed, 09 Jun 2010 09:43:48 +0200
RaSca <rasca-9B074fXSGsOr88ip1nKoZ2D2FQJk+8+b@public.gmane.org> wrote:
> Il giorno Mar 08 Giu 2010 23:54:25 CET, Neil Brown ha scritto:
> [...]
> > Try
> > exportfs -f
>
> Already tried, it didn't work. The file system is still locked by nfsd.
>
Seems unlikely ... "exportfs -f" flushes all the export caches in the kernel
thus letting go of any filesystems.
I guess an active NFS request could still hold the fs active, but that should
complete fairly quickly.
file locking might be an issue. Might a client have a lock on some file in
the filesystem? Failover of locks is rather more complicated that simple
file-access fail-over. I don't recall what the status of this is currently.
When the umount files, check the content of
/proc/net/rpc/nfsd.export/content
and
/proc/locks
to check what is actually using the filesystem.
NeilBrown
next prev parent reply other threads:[~2010-06-09 8:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 16:24 Problem using exportfs in an active-active nfs cluster RaSca
[not found] ` <4C0E6ED0.60200-9B074fXSGsOr88ip1nKoZ2D2FQJk+8+b@public.gmane.org>
2010-06-08 21:54 ` Neil Brown
[not found] ` <20100609075425.7ec4ccd9-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2010-06-09 7:43 ` RaSca
[not found] ` <4C0F4634.8090102-9B074fXSGsOr88ip1nKoZ2D2FQJk+8+b@public.gmane.org>
2010-06-09 8:01 ` RaSca
2010-06-09 8:01 ` RaSca
2010-06-09 8:04 ` Neil Brown [this message]
2010-06-09 10:28 ` RaSca
2010-06-10 4:09 ` Neil Brown
2010-06-11 8:49 ` RaSca
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=20100609180439.40e856ac@notabene.brown \
--to=neilb@suse.de \
--cc=linux-nfs@vger.kernel.org \
--cc=rasca-9B074fXSGsOr88ip1nKoZ2D2FQJk+8+b@public.gmane.org \
/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