public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jaxboe@fusionio.com>
To: Mark Lord <kernel@teksavvy.com>
Cc: Brian Bloniarz <bmb@athenacr.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [GIT PULL] block/io bits for 2.6.35-rc
Date: Mon, 28 Jun 2010 09:03:13 +0200	[thread overview]
Message-ID: <4C284931.2000908@fusionio.com> (raw)
In-Reply-To: <4C27DA4A.3040708@teksavvy.com>

On 2010-06-28 01:10, Mark Lord wrote:
> On 10/06/10 12:44 PM, Brian Bloniarz wrote:
>> On 06/10/2010 12:25 PM, Jens Axboe wrote:
>>> On 2010-06-10 17:55, Linus Torvalds wrote:
>>>> On Thu, Jun 10, 2010 at 6:44 AM, Jens Axboe<jaxboe@fusionio.com>  wrote:
>>>>>
>>>>> - A set of patches fixing the WB_SYNC_NONE writeback from Christoph. So
>>>>>   we should finally have both functional and working WB_SYNC_NONE from
>>>>>   umount context.
>>>>
>>>> I _really_ think this is too late, considering how broken it has been.
>>>> We already reverted the WB_SYNC_NONE things exactly because it didn't
>>>> work, didn't we? I'm going to be off-line in two days, and this part
>>>> of the pull request really makes me nervous, if only simply because of
>>>> the history of it all (ie it's always been broken, why shouldn't it be
>>>> broken now?).
>>>>
>>>> IOW, that's a lot of scary changes, that have historically not been
>>>> safe or sufficiently tested, and have caused problems for various
>>>> filesystems. Convince me why they should suddenly be ok to merge?
>>>
>>> I agree, it's late and it makes me nervous too. I had them cook for
>>> a day, didn't see any problems. And Christoph would not send it in
>>> unless it passes at least xfs qa, which is what found the problems
>>> last time (the ones we reverted).
>>>
>>> It's fixing a regression where umount takes a LONG time if you have
>>> a lot of dirty inodes, since it basically degenerates to a data
>>> integrity writeback instead of a simple WB_SYNC_NONE. If it wasn't
>>> fixing a nasty regression (the distros are all wanting a real fix
>>> for this, it's a user problem), I would not be submitting this code
>>> at this point in time.
>>>
>>
>> Reinforcing that last point: from what I could figure out, Fedora 13
>> is shipping the buggy WB_SYNC_NONE patch currently. Ubuntu 10.04 is
>> shipping an in-kernel workaround that has serious performance
>> drawbacks.
>>
>> https://bugzilla.kernel.org/show_bug.cgi?id=15906 has links to the
>> downstream bugs.
> ..
> 
> Jens, this bug has been biting my servers badly here for the past
> few months -- umount after a backup (from ext4 to ext4) takes 3-4 minutes
> instead of the expected 3-4 seconds.
> 
> Is there a patch file for this against 2.6.34 that I (and others) could use?

It's the patch series from Christoph in my for-linus branch, I intend
to push it upstream when Linus is back and taking patches.

-- 
Jens Axboe


  reply	other threads:[~2010-06-28  7:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-10 13:44 [GIT PULL] block/io bits for 2.6.35-rc Jens Axboe
2010-06-10 15:55 ` Linus Torvalds
2010-06-10 16:25   ` Jens Axboe
2010-06-10 16:40     ` Christoph Hellwig
2010-06-10 16:59       ` Jens Axboe
2010-06-10 17:03       ` Linus Torvalds
2010-06-10 16:44     ` Brian Bloniarz
2010-06-27 23:10       ` Mark Lord
2010-06-28  7:03         ` Jens Axboe [this message]
2010-06-28  9:41           ` Christoph Hellwig
2010-06-28 13:51           ` Mark Lord
2010-06-28 14:05             ` Brian Bloniarz
2010-06-28 14:33               ` Mark Lord
2010-06-28 17:32               ` Jens Axboe
2010-06-28 20:55                 ` Mark Lord
2010-06-10 16:55     ` Linus Torvalds
2010-06-10 17:00       ` Jens Axboe

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=4C284931.2000908@fusionio.com \
    --to=jaxboe@fusionio.com \
    --cc=bmb@athenacr.com \
    --cc=hch@lst.de \
    --cc=kernel@teksavvy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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