All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Ch. Eigler <fche@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Tracing IO requests?
Date: Mon, 07 Mar 2011 11:02:35 -0500	[thread overview]
Message-ID: <y0msjuy2a1w.fsf@fche.csb> (raw)
In-Reply-To: <4D6EDFE0.2040905@bartk.us> (Bart Kus's message of "Wed, 02 Mar 2011 16:25:04 -0800")

Bart Kus <me@bartk.us> writes:

>>>> issue is why all the reads?  It should be 99% writes.
>> cp has to read something before it can write it elsewhere.
> Ray, my bad, I should have specified, the cp reads from a different
> volume/set of drives. [...]

One way to try answering such "why" questions is to plop a systemtap
probe at an event that should not be happening much, and print a
backtrace.  In your case you could run this for a little while during
the copy:

# stap -c 'sleep 2' -e '
probe ioblock.request {
  if (devname == "sdg2")                # adjust to taste
    if ((rw & 1) == 0)                  # ! REQ_WRITE
      if (randint(100) < 2)             # 2% of occurrences, if you like
         { println(devname, rw, size)
           print_backtrace() }
}
'


- FChE

  reply	other threads:[~2011-03-07 16:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-02 20:09 [linux-lvm] Tracing IO requests? Bart Kus
2011-03-02 20:13 ` Jonathan Tripathy
2011-03-02 22:19   ` Bart Kus
2011-03-02 23:00     ` Dave Sullivan
2011-03-02 23:44       ` Ray Morris
2011-03-03  0:25         ` Bart Kus
2011-03-07 16:02           ` Frank Ch. Eigler [this message]
2011-03-07 18:06             ` Wendy Cheng
2011-03-03 10:29 ` Bryn M. Reeves

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=y0msjuy2a1w.fsf@fche.csb \
    --to=fche@redhat.com \
    --cc=linux-lvm@redhat.com \
    /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.