public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Harry Edmon <harry@uw.edu>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Odd problem with Stale NFS file handle - NFS v3 server under 2.6.35.x
Date: Wed, 25 Aug 2010 15:09:17 -0700	[thread overview]
Message-ID: <4C75948D.4040400@uw.edu> (raw)
In-Reply-To: <20100825105320.GA17190@infradead.org>

Christoph Hellwig wrote:
> Are you running xfs on this machine?  If so can you please try
> this patch:
>
> 	http://git.kernel.org/?p=linux/kernel/git/dgc/xfsdev.git;a=commitdiff;h=4536f2ad8b330453d7ebec0746c4374eadd649b1
>
>   
This looks very good so far.   I have been running it for 7 hours with 
no problems.  That is much longer than I was able to run before the patch.

I notice that this patch (along with other xfs patches) has been 
submitted for 2.6.36-rc3.   Do you plan to try to get this into 
2.6.35.5+ (2.6.35.4 is already in testing)?

Thanks for the help, I really appreciate it!

-- 
 Dr. Harry Edmon			E-MAIL: harry@uw.edu
 206-543-0547 FAX: 206-543-0308			harry@atmos.washington.edu
 Director of IT, College of the Environment and
 Director of Computing, Dept of Atmospheric Sciences
 University of Washington, Box 351640, Seattle, WA 98195-1640


  parent reply	other threads:[~2010-08-25 22:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-24 17:56 Odd problem with Stale NFS file handle - NFS v3 server under 2.6.35.x Harry Edmon
2010-08-24 22:58 ` J. Bruce Fields
2010-08-24 23:10   ` Harry Edmon
2010-08-24 23:38     ` J. Bruce Fields
2010-08-25  2:16       ` Harry Edmon
2010-08-25 10:53 ` Christoph Hellwig
2010-08-25 16:49   ` Harry Edmon
2010-08-25 22:09   ` Harry Edmon [this message]
2010-08-26 10:45     ` Christoph Hellwig
2010-08-26 18:55       ` Harry Edmon

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=4C75948D.4040400@uw.edu \
    --to=harry@uw.edu \
    --cc=hch@infradead.org \
    --cc=linux-nfs@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox