linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 16380] ext2/ext4 filesystem "hangs" for a few seconds when trying to write a lot of data to a freshly RW mounted FS
Date: Sat,  4 Aug 2012 20:00:28 +0000 (UTC)	[thread overview]
Message-ID: <20120804200028.9235611FC62@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-16380-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=16380


Artem S. Tashkinov <t.artem@mailcity.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




--- Comment #16 from Artem S. Tashkinov <t.artem@mailcity.com>  2012-08-04 20:00:28 ---
(In reply to comment #15)
> The delay before the write starts is normal; that's encoded in how the
> writeback code handles dirty pages.  We don't start writes the instant that
> pages are dirtied in the buffer cache.
> 
> In any case, if you have arguments about how the writeback code makes its
> choices, it's kinda of pointless to be complaining on a bug targetted at the
> ext4 developers, since we start the writeback when the VM system asks us to
> start write pages belonging to a particular inode....
> 
> See /usr/src/linux/Documentation/sysctl/vm.txt for more information.

Thanks for letting us know, probably what I perceived as a regression in ext4fs
was in fact a change in the VM writeback code.

It's still weird and terribly counter intuitive as no other OS exhibit this
behavior, but now that I know why it happens I need to file a different bug
report.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2012-08-04 20:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-16380-13602@https.bugzilla.kernel.org/>
2011-03-22 22:02 ` [Bug 16380] Loop devices act strangely in 2.6.35 bugzilla-daemon
2011-03-22 22:05 ` [Bug 16380] ext2 driver "hangs" for a few seconds when trying to write a lot of data to a freshly RW mounted FS bugzilla-daemon
2012-08-04 11:19 ` [Bug 16380] ext2/ext4 filesystem " bugzilla-daemon
2012-08-04 11:19 ` bugzilla-daemon
2012-08-04 11:53 ` bugzilla-daemon
2012-08-04 12:16 ` bugzilla-daemon
2012-08-04 12:54 ` bugzilla-daemon
2012-08-04 18:13 ` bugzilla-daemon
2012-08-04 18:14 ` bugzilla-daemon
2012-08-04 18:51 ` bugzilla-daemon
2012-08-04 19:51 ` bugzilla-daemon
2012-08-04 20:00 ` bugzilla-daemon [this message]
2015-02-07 10:25 ` bugzilla-daemon

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=20120804200028.9235611FC62@bugzilla.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).