All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kris Vassallo <kris@linuxcertified.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: nfs@lists.sourceforge.net
Subject: Re: Stale File handles keep coming back
Date: Tue, 26 Apr 2005 15:22:29 -0700	[thread overview]
Message-ID: <1114554149.4470.5.camel@localhost.localdomain> (raw)
In-Reply-To: <17006.13241.129839.558300@cse.unsw.edu.au>

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

On Tue, 2005-04-26 at 05:27, Neil Brown wrote:

> On Monday April 25, kris@linuxcertified.com wrote:
> > I am experiencing a problem with stale file handles, and I have not been
> > able to find an answer in the archives nor has doing anything in the
> > readme helped. I apologize if an answer has already been posted
> > regarding an issue such as this. After many frustrating hours of
> > troubleshooting I am hoping for some help. The mail is long but I am
> > hoping that it answers all the questions. 
> 
> Very odd...
> 
> The output of:
> 
>   echo 2048 > /proc/sys/sunrpc/rpc_debug
>   grep . /proc/net/rpc/*/content
>   ls -l /proc/fs/nfsd
>   cat /proc/fs/nfs/exports

As you wished:

[root@venus ~]# echo 2048 > /proc/sys/sunrpc/rpc_debug
[root@venus ~]# grep . /proc/net/rpc/*/content
/proc/net/rpc/auth.unix.ip/content:#class IP domain
/proc/net/rpc/auth.unix.ip/content:# expiry=1114555250 refcnt=0
/proc/net/rpc/auth.unix.ip/content:nfsd 10.113.1.35 10.113.1.0/26
/proc/net/rpc/auth.unix.ip/content:# expiry=1114554736 refcnt=0
/proc/net/rpc/auth.unix.ip/content:nfsd 10.113.1.31 10.113.1.0/26
/proc/net/rpc/auth.unix.ip/content:# expiry=1114555091 refcnt=0
/proc/net/rpc/auth.unix.ip/content:nfsd 10.113.1.32 10.113.1.0/26
/proc/net/rpc/auth.unix.ip/content:# expiry=1114554725 refcnt=0
/proc/net/rpc/auth.unix.ip/content:nfsd 10.113.1.33 10.113.1.0/26
/proc/net/rpc/auth.unix.ip/content:# expiry=1114553809 refcnt=0
/proc/net/rpc/auth.unix.ip/content:nfsd 10.113.1.30 10.113.1.0/26
/proc/net/rpc/auth.unix.ip/content:# expiry=1114554372 refcnt=0
/proc/net/rpc/auth.unix.ip/content:nfsd 10.113.1.23 10.113.1.0/26
/proc/net/rpc/auth.unix.ip/content:# expiry=1114554950 refcnt=0
/proc/net/rpc/auth.unix.ip/content:nfsd 10.113.1.20 10.113.1.0/26
/proc/net/rpc/auth.unix.ip/content:# expiry=1114554967 refcnt=0
/proc/net/rpc/auth.unix.ip/content:nfsd 10.113.1.22 10.113.1.0/26
/proc/net/rpc/auth.unix.ip/content:# expiry=1114555344 refcnt=0
/proc/net/rpc/auth.unix.ip/content:nfsd 10.113.1.15 10.113.1.0/26
/proc/net/rpc/auth.unix.ip/content:# expiry=1114554495 refcnt=0
/proc/net/rpc/auth.unix.ip/content:nfsd 10.113.1.16 10.113.1.0/26
/proc/net/rpc/auth.unix.ip/content:# expiry=1114555310 refcnt=0
/proc/net/rpc/auth.unix.ip/content:nfsd 10.113.1.18 10.113.1.0/26
/proc/net/rpc/auth.unix.ip/content:# expiry=1114555306 refcnt=0
/proc/net/rpc/auth.unix.ip/content:nfsd 10.113.1.13 10.113.1.0/26
/proc/net/rpc/auth.unix.ip/content:# expiry=1114555211 refcnt=0
/proc/net/rpc/auth.unix.ip/content:nfsd 10.113.1.7 10.113.1.0/26
/proc/net/rpc/auth.unix.ip/content:# expiry=1114555134 refcnt=0
/proc/net/rpc/auth.unix.ip/content:nfsd 10.113.1.8 10.113.1.0/26
/proc/net/rpc/auth.unix.ip/content:# expiry=1114554927 refcnt=0
/proc/net/rpc/auth.unix.ip/content:nfsd 10.113.1.9 10.113.1.0/26
/proc/net/rpc/nfs4.idtoname/content:#domain type id [name]
/proc/net/rpc/nfs4.nametoid/content:#domain type name [id]
/proc/net/rpc/nfsd.export/content:#path domain(flags)
/proc/net/rpc/nfsd.export/content:# expiry=1114555041 refcnt=1
/proc/net/rpc/nfsd.export/content:/home
10.113.1.0/26(rw,no_root_squash,sync,no_wdelay,no_subtree_check)
/proc/net/rpc/nfsd.fh/content:#domain fsidtype fsid [path]
/proc/net/rpc/nfsd.fh/content:# expiry=1114555041 refcnt=0
/proc/net/rpc/nfsd.fh/content:10.113.1.0/26 0 0x1100080000000002 /home

[root@venus ~]# ls -l /proc/fs/nfsd/
total 0
-r--r--r--  1 root root 0 Apr 22 19:14 exports
-rw-------  1 root root 0 Apr 22 19:14 filehandle
-rw-------  1 root root 0 Apr 22 19:14 nfsv4leasetime
-rw-------  1 root root 0 Apr 22 19:14 threads

[root@venus ~]# cat /proc/fs/nfs/exports
# Version 1.1
# Path Client(Flags) # IPs
/home   10.113.1.0/26(rw,no_root_squash,sync,no_wdelay,no_subtree_check)
[root@venus ~]#

Hope this helps! 
Thanks for taking a look at this, 
Kris


> 
> might help.
> 
> Thanks,
> NeilBrown

[-- Attachment #2: Type: text/html, Size: 4500 bytes --]

  reply	other threads:[~2005-04-26 22:22 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-25 21:07 Stale File handles keep coming back Kris Vassallo
2005-04-26 12:27 ` Neil Brown
2005-04-26 22:22   ` Kris Vassallo [this message]
2005-04-27  2:42     ` Neil Brown
2005-04-29  7:01       ` Frank Steiner
2005-04-29  8:00         ` Frank Steiner
2005-04-29 14:08         ` Trond Myklebust
2005-04-30 13:15           ` Frank Steiner
2005-04-30 16:29             ` Trond Myklebust
2005-05-02  6:24               ` Frank Steiner
2005-05-03 10:45         ` Frank Steiner
2005-05-03 11:11         ` Frank Steiner
2005-05-05  0:15           ` Kris Vassallo
2005-05-06  6:38             ` Frank Steiner
2005-05-09  6:04               ` Frank Steiner
2005-04-29 14:03       ` Frank Steiner
2005-05-03 21:21   ` Kris Vassallo
2005-05-04  5:44     ` Frank Steiner
2005-05-04 22:48       ` Kris Vassallo
2005-05-04 23:06         ` Trond Myklebust
2005-05-12  1:01       ` Kris Vassallo
2005-05-12  1:14         ` Neil Brown

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=1114554149.4470.5.camel@localhost.localdomain \
    --to=kris@linuxcertified.com \
    --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.