public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: RaSca <rasca-9B074fXSGsOr88ip1nKoZ2D2FQJk+8+b@public.gmane.org>
To: Neil Brown <neilb@suse.de>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Problem using exportfs in an active-active nfs cluster
Date: Wed, 09 Jun 2010 10:01:45 +0200	[thread overview]
Message-ID: <4C0F4A69.20005@miamammausalinux.org> (raw)
In-Reply-To: <4C0F4634.8090102-9B074fXSGsOr88ip1nKoZ2D2FQJk+8+b@public.gmane.org>

Il giorno Mer 09 Giu 2010 09:43:48 CET, RaSca ha scritto:
> 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 nfs=
d.

To be more specific: In my try first I do an exportfs -u of the export =
i=20
need to move and then i do an exportfs -f.
Client side the copy wait for a while and then gives some "Permission=20
denied" and exit.
Server side the problem, as already said is this one:

Jun  9 11:54:16 ubuntu-nodo1 lrmd: [692]: info: RA output:=20
(share-a-fs:stop:stderr) umount: /share-a: device is busy.#012=20
(In some cases useful info about processes that use#012         the=20
device is found by lsof(8) or fuser(1))
Jun  9 11:54:16 ubuntu-nodo1 lrmd: [692]: info: RA output:=20
(share-a-fs:stop:stderr)
Jun  9 11:54:16 ubuntu-nodo1 Filesystem[4065]: ERROR: Couldn't unmount=20
/share-a; trying cleanup with KILL
Jun  9 11:54:16 ubuntu-nodo1 Filesystem[4065]: INFO: No processes on=20
/share-a were signalled

As you can see the filesystem resource agent tries to unmount /share-a=20
but even if fuser or lsof does not give output, it still remains locked=
=20
(by nfsd, of course).

Have you got any other suggestion? Thanks a lot for your help.

--=20
RaSca
Mia Mamma Usa Linux: Niente =E8 impossibile da capire, se lo spieghi be=
ne!
rasca-9B074fXSGsOr88ip1nKoZ2D2FQJk+8+b@public.gmane.org
http://www.miamammausalinux.org

  parent reply	other threads:[~2010-06-09  8:01 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 [this message]
2010-06-09  8:04           ` Neil Brown
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=4C0F4A69.20005@miamammausalinux.org \
    --to=rasca-9b074fxsgsor88ip1nkoz2d2fqjk+8+b@public.gmane.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    /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