From: "J. Bruce Fields" <bfields@fieldses.org>
To: Igor Chudov <ichudov@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: NFS _write_ Performance became horrible overnight
Date: Fri, 16 Jul 2010 16:08:02 -0400 [thread overview]
Message-ID: <20100716200802.GA13077@fieldses.org> (raw)
In-Reply-To: <AANLkTinaHi1bZYRwI-jXiv_xPhQyvTUGmzBrfP-JRYs3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Mon, Jul 12, 2010 at 10:37:48AM -0500, Igor Chudov wrote:
> Hello,
>
> I would like to apologize in advance if, for any reason, my question
> is inappropriate for this mailing list. Please let meknow if that is
> the case.
>
> This seems to be a very odd problem that I have isolated to NFS.
>
> I have two NFS servers. Server A and server B. They serve unrelated
> shares.
>
> Server A is actually two servers using DRBD to stay in sync.
>
> I also have a number of NFS clients.
>
> Both servers worked great up to about last night.
>
> Somehow, NFS writes became extremely slow over Server A, for all
> clients, but not for Server B.
>
> I have no idea, yet, what changed, but wanted to ask here if anyone
> ever had a similar problem (NFS performance going to shit overnight).
>
> Some data points:
>
> 1) From any client, reading files over NFS is fast
> 2) From any client, writing to NFS on Server A is VERY SLOW
> 3) From any client, writing to Samba shares on Server A is fast.
> 4) From any client, writing to NFS on Server B is fast.
> 5) When logged on to Server A, copying a file from local A filesystem
> to itself is fast.
How are you measuring those exactly? (E.g. are you including the time
to do a sync after writing?)
--b.
>
> IOW, everything is fast, EXCEPT for NFS writes to server A.
>
> Any ideas what might cause this sudden deterioration of Server A?
>
> Thank you!!!!!!!!!!!
>
> i
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-07-16 20:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 15:37 NFS _write_ Performance became horrible overnight Igor Chudov
[not found] ` <AANLkTinaHi1bZYRwI-jXiv_xPhQyvTUGmzBrfP-JRYs3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-16 20:08 ` 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=20100716200802.GA13077@fieldses.org \
--to=bfields@fieldses.org \
--cc=ichudov@gmail.com \
--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 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.