From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Dave Jones <davej@redhat.com>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 3.1rc7+ FSX failure over NFS
Date: Thu, 29 Sep 2011 14:59:32 -0400 [thread overview]
Message-ID: <1317322772.8708.30.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20110929184127.GA12236@redhat.com>
On Thu, 2011-09-29 at 14:41 -0400, Dave Jones wrote:
> Client is running 3.1rc7+ from a day before rc8 landed.
> Server is 3.0.4. FSX dies after a half hour or so.
> Mount options are..
> (rw,relatime,vers=3,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.42.10,mountvers=3,mountport=45114,mountproto=tcp,local_lock=none,addr=192.168.42.10)
>
> I noticed a few NFS commits that I might be missing from
> the last few days, would they explain this ?
Hi Dave,
No, there shouldn't be anything in recent patches that can explain or
fix this.
I have a few questions:
1) What filesystem are you using on the server, and does that filesystem
support high resolution timestamps?
2) Does the file length on the server match the reported erroneous file
length on the client?
3) Do the mtime and ctime on the erroneous file match on the client and
server?
Cheers
Trond
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
next prev parent reply other threads:[~2011-09-29 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 18:41 3.1rc7+ FSX failure over NFS Dave Jones
2011-09-29 18:59 ` Trond Myklebust [this message]
2011-09-29 19:05 ` Dave Jones
2011-09-29 19:22 ` Trond Myklebust
2011-09-29 20:11 ` Dave Jones
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=1317322772.8708.30.camel@lade.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).