All of lore.kernel.org
 help / color / mirror / Atom feed
From: Garrick Staples <garrick@usc.edu>
To: nfs@lists.sourceforge.net
Subject: Re: nfsd, rmtab, failover, and stale filehandles
Date: Tue, 11 May 2004 11:26:35 -0700	[thread overview]
Message-ID: <20040511182635.GI30964@polop.usc.edu> (raw)
In-Reply-To: <20040507223414.GQ30964@polop.usc.edu>

[-- Attachment #1: Type: text/plain, Size: 1620 bytes --]

I just wanted to mention that failover has been rock solid with those two
patches.  Thank you very much for your help!

Does the patch below look ok?


On Fri, May 07, 2004 at 03:34:15PM -0700, Garrick Staples alleged:
> On Fri, May 07, 2004 at 02:38:12PM -0700, Garrick Staples alleged:
> > But now I've just noticed something else that is odd.  Something that I'm
> > surprised I haven't come across before...  I have to unexport filesystems
> > twice before I can unmount them.
> 
> 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?
> 
> Force a cache flush if unexporting, and don't reread rmtab if we're using the
> new cache.
> 
> --- exportfs.c_orig     2004-05-07 15:32:22.423905760 -0700
> +++ exportfs.c  2004-05-07 15:33:33.669998637 -0700
> @@ -127,10 +127,13 @@
>                  */
>                 if (!f_reexport)
>                         xtab_export_read();
> -               if (!f_export)
> +               if (!f_export) {
> +                       force_flush=1;
>                         for (i = optind ; i < argc ; i++)
>                                 unexportfs(argv[i], f_verbose);
> -               rmtab_read();
> +               }
> +               if (!new_cache)
> +                       rmtab_read();
>         }
>         if (!new_cache) {
>                 xtab_mount_read();
> 
> 
> -- 
> Garrick Staples, Linux/HPCC Administrator
> University of Southern California



-- 
Garrick Staples, Linux/HPCC Administrator
University of Southern California

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-05-11 18:30 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 [this message]
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

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=20040511182635.GI30964@polop.usc.edu \
    --to=garrick@usc.edu \
    --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.