From: Garrick Staples <garrick@usc.edu>
To: nfs@lists.sourceforge.net
Subject: Re: nfsd, rmtab, failover, and stale filehandles
Date: Thu, 6 May 2004 16:00:55 -0700 [thread overview]
Message-ID: <20040506230055.GC26968@polop.usc.edu> (raw)
In-Reply-To: <20040506222455.GP18964@fieldses.org>
[-- Attachment #1: Type: text/plain, Size: 1328 bytes --]
On Thu, May 06, 2004 at 06:24:55PM -0400, J. Bruce Fields alleged:
> On Thu, May 06, 2004 at 02:53:11PM -0700, Garrick Staples wrote:
> > I'm at a total loss. Everything I'm reading tells me that all I need to ensure
> > is that fs device names are the same on both servers so that the generated
> > filehandles are the same, and that I need to move all lines matching
> > ":$mountpoint:" in rmtab to the new server. The former is done since I'm using
> > persistant device numbers with lvm. The latter shouldn't be needed because I'm
> > using the "new" proc interface with 2.6.5.
> >
> > rmtab definitly doesn't do any noticable difference. I can add random text
> > and blank it out with no noticable difference on the clients.
> >
> > Is this a client problem? The clients are all 2.4.24 and 2.4.26.
> >
> > All clients and servers are using vanilla kernels.
> Hmm, also, could you try recompiling mountd with the following patch
> applied?
No effect. All I did was kill mountd, run the patched mountd, and try to 'ls'
on the client.
Watching an strace of mountd, it doesn't seem that mountd is ever contacted.
The client reports stale filehandle pretty much immediately, and mountd doesn't
do anything.
--
Garrick Staples, Linux/HPCC Administrator
University of Southern California
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-05-06 23:02 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 [this message]
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
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=20040506230055.GC26968@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.