All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank van Maarseveen <frankvm@frankvm.com>
To: Linux NFS mailing list <nfs@lists.sourceforge.net>
Subject: exportfs -f question
Date: Mon, 14 May 2007 20:28:09 +0200	[thread overview]
Message-ID: <20070514182809.GA7127@janus> (raw)

I have a server which exports 20-30 local filesystems, each with a
different fsid=<decimal-ip-address> option. eth0 on the server has one
additional ip address for every export. Apart from NLM issues mentioned
earlier on this list, what is the best way to drop caches to be able to
umount one exported mount-point on the server?

Right now I do a

	ip addr del... (remove ip address to block traffic for this export)
	exportfs -f
	umount /exported-mountpoint

but since exportfs -f does a

	time(NULL)                              = 1179165584
	open("/proc/net/rpc/auth.unix.ip/flush", O_RDWR) = 3
	write(3, "1179165584\n", 11)            = 11
	close(3)                                = 0
	open("/proc/net/rpc/nfsd.export/flush", O_RDWR) = 3
	write(3, "1179165584\n", 11)            = 11
	close(3)                                = 0
	open("/proc/net/rpc/nfsd.fh/flush", O_RDWR) = 3
	write(3, "1179165584\n", 11)            = 11
	close(3)                                = 0

I wonder if:

-	can above umount fail due to a race with in-kernel operations?
-	is there a more efficient way to flush cached filehandles
	for a specific export or fsid?
	(I have no clue about performance penalty for the other exports)


-- 
Frank

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

                 reply	other threads:[~2007-05-14 18:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20070514182809.GA7127@janus \
    --to=frankvm@frankvm.com \
    --cc=nfs@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.