From: Garrick Staples <garrick@usc.edu>
To: nfs@lists.sourceforge.net
Subject: Re: nfsd, rmtab, failover, and stale filehandles
Date: Fri, 7 May 2004 14:38:12 -0700 [thread overview]
Message-ID: <20040507213811.GL30964@polop.usc.edu> (raw)
In-Reply-To: <20040507182543.GA27341@fieldses.org>
[-- Attachment #1: Type: text/plain, Size: 1892 bytes --]
On Fri, May 07, 2004 at 02:25:43PM -0400, J. Bruce Fields alleged:
> On Thu, May 06, 2004 at 04:00:55PM -0700, Garrick Staples wrote:
> > No effect. All I did was kill mountd, run the patched mountd, and try to 'ls'
> > on the client.
>
> I think that's not enough....
>
> > 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.
>
> The upcall was made earlier, and the kernel has cached it (even if it's
> a negative result). So, just to make sure, could you try:
>
> killall rpc.mountd
> exportfs -f #flush the kernel's caches
> rpc.mountd #(the patched version)
Hey! That did, in fact, revive a long-standing stale filehandle! Cheers for
Mr. Fields!
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.
Good and normal...
[root@hpc-fs3 root]# mount /dev/vgtest/lvtest /mnt/test
[root@hpc-fs3 root]# exportfs -o rw,no_subtree_check,no_root_squash,async 10.125.0.0/16:/mnt/test
[root@hpc-fs3 root]# exportfs -u 10.125.0.0/16:/mnt/test
[root@hpc-fs3 root]# umount /mnt/test
Same thing, but I did an 'ls' on the client after it was exported...
[root@hpc-fs3 root]# mount /dev/vgtest/lvtest /mnt/test
[root@hpc-fs3 root]# exportfs -o rw,no_subtree_check,no_root_squash,async 10.125.0.0/16:/mnt/test
[root@hpc-fs3 root]# exportfs -u 10.125.0.0/16:/mnt/test
[root@hpc-fs3 root]# umount /mnt/test
umount: /mnt/test: device is busy
[root@hpc-fs3 root]# exportfs -u 10.125.0.0/16:/mnt/test
[root@hpc-fs3 root]# umount /mnt/test
'exportfs -f' does as well as a second umount.
--
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-07 21:41 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 [this message]
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=20040507213811.GL30964@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.