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 18:51:24 +0000 (UTC) [thread overview]
Message-ID: <20120804185124.7F52511FC62@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-16380-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=16380
--- Comment #14 from Artem S. Tashkinov <t.artem@mailcity.com> 2012-08-04 18:51:24 ---
(In reply to comment #12)
> I wasn't able to duplicate this with an underlying ext4 file system, with the
> loop file system being ext2, using a 3.5 kernel on a system with 16G.
>
> I tried both using a variety of small and medium sized files, as well as one
> very large file, and I didn't see any unexplained stuttering in write
> bandwidth. (There were times when cp -r was clearly writing to the in-memory
> page cache, and the writeback hadn't begone yet. There were also times when
> we couldn't do any more writing, because we were busy reading from the source
> drive. But it all looked pretty normal to me.)
Hm, I cannot reproduce the problem with a loop device on top of tmpfs either,
but I've just checked my 250GB ext4 partition and the bug is still there:
When I try to copy a 3GB file (residing in tmpfs so it's all cached) to it,
there's a 4 (four) seconds delay before a single byte gets written to the
destination partition. After that all consequent files get written without any
delays.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2012-08-04 18:51 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 [this message]
2012-08-04 19:51 ` bugzilla-daemon
2012-08-04 20:00 ` bugzilla-daemon
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=20120804185124.7F52511FC62@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).