All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 14972] [regression] msync() call on ext4 causes disk thrashing
Date: Mon, 4 Jan 2010 03:35:24 GMT	[thread overview]
Message-ID: <201001040335.o043ZOrW020607@demeter.kernel.org> (raw)
In-Reply-To: <bug-14972-13602@http.bugzilla.kernel.org/>

http://bugzilla.kernel.org/show_bug.cgi?id=14972


Eric Sandeen <sandeen@redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sandeen@redhat.com




--- Comment #10 from Eric Sandeen <sandeen@redhat.com>  2010-01-04 03:35:22 ---
(In reply to comment #9)
> grep BLK.*TRACE /usr/src/linux/.config
> 
> CONFIG_BLK_DEV_IO_TRACE=y
> 
> Yes, I'm running under root. SeLinux is disabled in the kernel. I've no idea
> what to do :(

Drop the echos.  Just mounting debugfs & running blktrace will suffice:

[root@inode ~]# mount -t debugfs none /sys/kernel/debug/
[root@inode ~]# blktrace /dev/sda
^C=== sda ===
  CPU  0:                    0 events,        0 KiB data
  CPU  1:                    1 events,        1 KiB data
  Total:                     1 events (dropped 0),        1 KiB data

but if you do this first:

[root@inode ~]# echo blk > /sys/kernel/debug/tracing/current_tracer
[root@inode ~]# echo 1 > /sys/block/sda/sda3/trace/enable

you get the -EBUSY:

[root@inode ~]# blktrace /dev/sda
BLKTRACESETUP(2) /dev/sda failed: 16/Device or resource busy
Thread 1 failed open /sys/kernel/debug/block/(null)/trace1: 2/No such file or
directory
Thread 0 failed open /sys/kernel/debug/block/(null)/trace0: 2/No such file or
directory
FAILED to start thread on CPU 0: 1/Operation not permitted
FAILED to start thread on CPU 1: 1/Operation not permitted

It's not related to selinux.

-Eric

-- 
Configure bugmail: http://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:[~2010-01-04  3:35 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
2010-01-03 12:38 ` bugzilla-daemon
2010-01-04  3:35 ` bugzilla-daemon [this message]
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=201001040335.o043ZOrW020607@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.