All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Garrick Staples <garrick@usc.edu>, nfs@lists.sourceforge.net
Subject: Re: nfsd, rmtab, failover, and stale filehandles
Date: Mon, 7 Jun 2004 23:42:28 -0400	[thread overview]
Message-ID: <20040608034228.GA31761@fieldses.org> (raw)
In-Reply-To: <16581.11543.342424.795946@cse.unsw.edu.au>

On Tue, Jun 08, 2004 at 01:05:59PM +1000, Neil Brown wrote:
> > I'm looking at exportfs.c to see if I can add in a call to flush the caching
> > when unmounting, does the following seem reasonable?
> 
> The code already flushes the caches if anything has changed.
> 
> Towards the end of main() in exportfs.c there is:
> 
> 	xtab_export_write();
> 	if (new_cache)
> 		cache_flush(force_flush);

Ah!  I missed that.

> And to answer Bruce's subsequent question:
> > Can someone explaing what the reason was for adding the -f flag to
> > exportfs?
> Because it is useful for testing.  It should not be needed during
> normal running.

Got it, that makes more sense.  But if the only time "-f" is ever needed
is when there's a bug somewhere, then maybe it should just be removed,
or at least not documented?  Otherwise it seems like it's only likely to
cause confusion.

--b.


-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      reply	other threads:[~2004-06-08  3:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-06 18:56 nfsd, rmtab, failover, and stale filehandles Garrick Staples
2004-05-06 19:07 ` J. Bruce Fields
2004-05-06 19:12   ` Garrick Staples
2004-05-06 19:13 ` Garrick Staples
2004-05-06 21:53   ` Garrick Staples
2004-05-06 22:24     ` J. Bruce Fields
2004-05-06 22:42       ` Garrick Staples
2004-05-06 23:00       ` Garrick Staples
2004-05-07 17:18         ` Garrick Staples
2004-05-07 18:25         ` J. Bruce Fields
2004-05-07 21:38           ` Garrick Staples
2004-05-07 21:52             ` elijah wright
2004-05-07 22:17               ` Garrick Staples
2004-05-07 22:27                 ` elijah wright
2004-05-07 22:34             ` Garrick Staples
2004-05-11 18:26               ` Garrick Staples
2004-05-13 21:00               ` J. Bruce Fields
2004-05-13 21:37                 ` Garrick Staples
2004-06-08  3:05               ` Neil Brown
2004-06-08  3:42                 ` J. Bruce Fields [this message]

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=20040608034228.GA31761@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=garrick@usc.edu \
    --cc=neilb@cse.unsw.edu.au \
    --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.