[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20120804200028.9235611FC62@bugzilla.kernel.org>
Date: Sat, 4 Aug 2012 20:00:28 +0000 (UTC)
From: bugzilla-daemon@...zilla.kernel.org
To: linux-ext4@...r.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
https://bugzilla.kernel.org/show_bug.cgi?id=16380
Artem S. Tashkinov <t.artem@...lcity.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #16 from Artem S. Tashkinov <t.artem@...lcity.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists