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, 03 May 2005 14:21:15 -0700 [thread overview]
Message-ID: <1115155275.2894.20.camel@localhost.localdomain> (raw)
In-Reply-To: <17006.13241.129839.558300@cse.unsw.edu.au>
[-- Attachment #1: Type: text/plain, Size: 2079 bytes --]
So in reference to this bug
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=150759
it seems as if ridding the system of the journal by instead using ext2
is fixing the problem? I can't tell if that bug has anything to do with
providing ESTALE errors but it seems to have the same effect where you
can't see files even though they are there.
Has anyone tried using the journal_data_ordered option? I am not sure
there is a way to do that in reiser but I know it can be done with ext3.
I am wondering if stuff is sitting in the journal and there is a lag
between writing in the journal and then having that data written to
disk. Using journal_data_ordered would theoretically fix that problem as
it would force the data to be written to the disk first.
This is just a shot in the dark and I will let you know if I have any
success with this. Does anyone have any ideas on this?
-Kris
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
>
> might help.
>
> Thanks,
> NeilBrown
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> NFS maillist - NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs
[-- Attachment #2: Type: text/html, Size: 2644 bytes --]
next prev parent reply other threads:[~2005-05-03 21:21 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
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 [this message]
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=1115155275.2894.20.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.