From: Bill Broadley <bill@broadley.org>
To: linux-btrace@vger.kernel.org
Subject: Re: Seg fault in blkparse.
Date: Wed, 25 May 2011 08:51:28 +0000 [thread overview]
Message-ID: <4DDCC310.1040500@broadley.org> (raw)
In-Reply-To: <4DDC418E.4080407@broadley.org>
Sorry for the confusion.
Some small fixes.
On 05/25/2011 01:48 AM, Bill Broadley wrote:
> Sure. I did have the log from the previous run, but I was careful in
I didn't have the logs so I had to reproduce them.
> So for proper btrfs usage I should monitor /dev/sdc1? Use 12 -d's to add
> each device? Use -I and list the 12 devices one per line in a file?
I meant for proper blktrace usage, not btrfs
prev parent reply other threads:[~2011-05-25 8:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 23:38 Seg fault in blkparse Bill Broadley
2011-05-25 6:19 ` Tao Ma
2011-05-25 8:48 ` Bill Broadley
2011-05-25 8:51 ` Bill Broadley [this message]
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=4DDCC310.1040500@broadley.org \
--to=bill@broadley.org \
--cc=linux-btrace@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).