From: Bart Kus <me@bartk.us>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Tracing IO requests?
Date: Wed, 02 Mar 2011 16:25:04 -0800 [thread overview]
Message-ID: <4D6EDFE0.2040905@bartk.us> (raw)
In-Reply-To: <20110302174412.06eecd67@bettercgi.com>
On 3/2/2011 3:44 PM, Ray Morris wrote:
>>> On 3/2/2011 12:13 PM, Jonathan Tripathy wrote:
>>> I know the IO is only being caused by a "cp -a" command, but the
>>> 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.
Thanks for the systemtap tip, Dave!
--Bart
next prev parent reply other threads:[~2011-03-03 0:25 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 [this message]
2011-03-07 16:02 ` Frank Ch. Eigler
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=4D6EDFE0.2040905@bartk.us \
--to=me@bartk.us \
--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 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).