From: Richard Weinberger <richard@nod.at>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Linux NFS mailing list <linux-nfs@vger.kernel.org>,
trond.myklebust@primarydata.com, NeilBrown <neilb@suse.de>,
LKML <linux-kernel@vger.kernel.org>,
David Gstir <david@sigma-star.at>
Subject: Re: NFS issue while copying huge file
Date: Fri, 23 May 2014 15:46:27 +0200 [thread overview]
Message-ID: <537F5133.8020700@nod.at> (raw)
In-Reply-To: <20140523133907.GJ25423@fieldses.org>
Am 23.05.2014 15:39, schrieb J. Bruce Fields:
> And like the lock contention may be in xfs.... So ideally you'd get
> someone who knows the CentOS/RHEL6 xfs code to look at it first.
I saw this coming. ;)
Thanks,
//richard
next prev parent reply other threads:[~2014-05-23 13:46 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 [this message]
2014-05-26 21:50 ` Dave Chinner
2014-05-23 13:35 ` J. Bruce Fields
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=537F5133.8020700@nod.at \
--to=richard@nod.at \
--cc=bfields@fieldses.org \
--cc=david@sigma-star.at \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox