From: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
To: "Wu Fengguang" <fengguang.wu@intel.com>
Cc: <jens.axboe@oracle.com>, "Chris Mason" <chris.mason@oracle.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
<linux-fsdevel@vger.kernel.org>,
"LKML" <linux-kernel@vger.kernel.org>,
<linux-nfs@vger.kernel.org>
Subject: Re: [PATCH v2] NFS: introduce writeback wait queue
Date: Mon, 5 Oct 2009 06:55:54 -0400 [thread overview]
Message-ID: <F047DA72-75B3-4447-84EB-7115C77ECBA3@netapp.com> (raw)
In-Reply-To: <20091005073959.GA23398@localhost>
On Oct 5, 2009, at 3:40, "Wu Fengguang" <fengguang.wu@intel.com> wrote:
> On Mon, Oct 05, 2009 at 03:35:51PM +0800, Wu Fengguang wrote:
>> Trond, I see this trace on linux-next. There are no more dirty pages
>> when `cp' aborts after filling up the partition:
>>
>> cp: writing `/mnt/test/zero3': No space left on device
>>
>> I noticed that since then nr_writeback is decreased very slowly
>> (~100 pages per second). Looks like an interesting behavior.
>
> In the mean time, there are constant 7-8MB/s writes in the NFS server.
> The network flow is much smaller ~400K/s. How can I debug this issue?
Hi Fengguang
This is deliberate behaviour. When asynchronous writes start recieving
errors, then we switch to synchronous write mode until the error
condition clears.
The reason is for doing so is firstly because some filesystems (XFS)
perform very poorly under ENOSPC, and so it takes forever to write
back pages (we don't want to cancel all writebacks for temporary
conditions like ENOSPC). It also allows us to deliver the errors more
promptly to the application.
Cheers
Trond
>
next prev parent reply other threads:[~2009-10-05 10:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-04 3:01 [PATCH] NFS: introduce writeback wait queue Wu Fengguang
2009-10-04 3:05 ` Wu Fengguang
2009-10-05 11:00 ` Jens Axboe
2009-10-06 0:12 ` Wu Fengguang
2009-10-05 7:10 ` [PATCH v2] " Wu Fengguang
2009-10-05 7:35 ` Wu Fengguang
2009-10-05 7:39 ` Wu Fengguang
2009-10-05 10:55 ` Myklebust, Trond [this message]
2009-10-05 13:08 ` Wu Fengguang
2009-10-05 11:01 ` Myklebust, Trond
2009-10-05 13:51 ` Wu Fengguang
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=F047DA72-75B3-4447-84EB-7115C77ECBA3@netapp.com \
--to=trond.myklebust@netapp.com \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=fengguang.wu@intel.com \
--cc=jens.axboe@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--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