From: "J. Bruce Fields" <bfields@fieldses.org>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: Linux NFS mailing list <linux-nfs@vger.kernel.org>,
trond.myklebust@primarydata.com, NeilBrown <neilb@suse.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: NFS issue while copying huge file
Date: Fri, 23 May 2014 09:35:37 -0400 [thread overview]
Message-ID: <20140523133537.GI25423@fieldses.org> (raw)
In-Reply-To: <CAFLxGvxm43MaOqv1JQ8vxkn4s50uHZ8Js6A-Ec+O_sjvFszehQ@mail.gmail.com>
On Thu, May 22, 2014 at 12:50:34PM +0200, Richard Weinberger wrote:
> On Wed, May 21, 2014 at 11:33 PM, Richard Weinberger
> <richard.weinberger@gmail.com> wrote:
> > Hi!
> >
> > My backup server runs CentOS6 with kernel 2.6.32-431.17.1.el6.x86_64.
> > Many servers copy theirs backups to it. This setups works perfectly
> > fine since ages.
> > Today I've configured a new server which runs Kernel 3.12.20 to store
> > it's backups to the NFS server too.
...
> Just gave 3.15-rc6 a try, it happens here too.
I was reading a little quickly and assumed all these kernel versions
described the NFS server, now I understand you're varying only the NFS
client; so against that CentOS 2.6.32 server, you're seeing the problem
when the NFS client is 3.12.20 or 3.15-rc6, but not if the NFS client is
running the same CentOS 2.6.32 version. Got it, sorry for the
confusion.
So with my upstream hat on that's a little less interesting since
upstream is pretty far from any 2.6.32-based kernel at this point.
--b.
prev parent reply other threads:[~2014-05-23 13:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 21:33 NFS issue while copying huge file Richard Weinberger
2014-05-22 10:50 ` Richard Weinberger
2014-05-23 11:56 ` J. Bruce Fields
2014-05-23 12:36 ` Richard Weinberger
2014-05-23 13:39 ` J. Bruce Fields
2014-05-23 13:46 ` Richard Weinberger
2014-05-26 21:50 ` Dave Chinner
2014-05-23 13:35 ` J. Bruce Fields [this message]
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=20140523133537.GI25423@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=richard.weinberger@gmail.com \
--cc=trond.myklebust@primarydata.com \
/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.