From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 42872] fstat()/ext3_iget() sometime takes over 2 minutes...
Date: Thu, 22 Mar 2012 14:37:49 GMT [thread overview]
Message-ID: <201203221437.q2MEbnRU019169@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-42872-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=42872
--- Comment #3 from Jan Kara <jack@suse.cz> 2012-03-22 14:37:48 ---
I did some testing of read latencies under heavy write load. Switching to
data=writeback helped a lot (not that data=ordered shouldn't be fixed but it's
not so simple). So can you try whether it helps also your case?
--
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-03-22 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 18:52 [Bug 42872] New: fstat()/ext3_iget() sometime takes over 2 minutes bugzilla-daemon
2012-03-06 20:29 ` [Bug 42872] " bugzilla-daemon
2012-03-15 17:56 ` bugzilla-daemon
2012-03-22 14:37 ` bugzilla-daemon [this message]
2012-04-04 23:31 ` 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=201203221437.q2MEbnRU019169@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).