From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 14972] [regression] msync() call on ext4 causes disk thrashing
Date: Sun, 3 Jan 2010 12:11:57 GMT [thread overview]
Message-ID: <201001031211.o03CBvL3007984@demeter.kernel.org> (raw)
In-Reply-To: <bug-14972-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=14972
--- Comment #8 from Theodore Tso <tytso@mit.edu> 2010-01-03 12:11:56 ---
I'm not sure why you are getting the device busy or resource busy error to the
BLKTRACESETUP ioctl. Are you sure this is a kernel with the blktrace support
configured in? And I assume the '#' error message indicates that you are
running as root. You don't have SELinux or some other LSM configured, do you?
Blktrace running alone does not produce output; it produces trace files for
each CPU that can be parsed using the blkparse program. If you look back,
you'll see that I suggested running the btrace program after you install the
blktrace package. The btrace program is a convenience script which runs
blktrace and blkparse to produce immediate output to standard out. There are
man pages for blktrace, blkparse, and btrace which should have been installed
when you installed the binaries for blktrace.
Still, it shouldn't have spit out those error messages....
--
Configure bugmail: http://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:[~2010-01-03 12:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-01 23:09 [Bug 14972] New: [regression] msync() call on ext4 causes disk thrashing bugzilla-daemon
2010-01-01 23:14 ` [Bug 14972] " bugzilla-daemon
2010-01-02 13:19 ` bugzilla-daemon
2010-01-02 15:10 ` bugzilla-daemon
2010-01-02 16:47 ` bugzilla-daemon
2010-01-02 16:48 ` bugzilla-daemon
2010-01-02 16:54 ` bugzilla-daemon
2010-01-02 17:54 ` bugzilla-daemon
2010-01-03 10:31 ` bugzilla-daemon
2010-01-03 12:11 ` bugzilla-daemon [this message]
2010-01-03 12:38 ` bugzilla-daemon
2010-01-04 3:35 ` bugzilla-daemon
2010-01-04 10:05 ` bugzilla-daemon
[not found] <bug-14972-13602@https.bugzilla.kernel.org/>
2011-03-03 11:25 ` bugzilla-daemon
2012-01-11 0:08 ` bugzilla-daemon
2012-03-17 8:46 ` bugzilla-daemon
2012-03-17 9:07 ` 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=201001031211.o03CBvL3007984@demeter.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).