All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tao Ma <tm@tao.ma>
To: linux-btrace@vger.kernel.org
Subject: Re: Seg fault in blkparse.
Date: Wed, 25 May 2011 06:19:12 +0000	[thread overview]
Message-ID: <4DDC9F60.9000507@tao.ma> (raw)
In-Reply-To: <4DDC418E.4080407@broadley.org>

On 05/25/2011 07:38 AM, Bill Broadley wrote:
> 
> I recorded a 3 minutes of heavy IO (generated with fio) with:
> blktrace -w 240 -a read -a write -a fs -I devs -o btrfs-12-blk.log
> 
> (I used 240 seconds to make sure I didn't miss any of the 180 seconds of
> I/O).
> 
> As a small aside I wasn't sure what the default filter mask was, it
> seems more correct to use:
> blktrace -w 240 -A read -a write -a fs -I devs -o btrfs-12-blk.log
> 
> So set the mask to exactly (and only) read, then add write, and fs.  But
> that dies with:
>    Invalid set action mask read/0x0
> 
> The above mentioned file "devs" contains /etc/sdc1 ... /dev/sdn1 (12
> devices, one per line).
> 
> It generated 16 log files (it's a dual socket x quad core/8 thread intel
> CPUs).  The logs total 15M (using du --total -h *blktrace*).
> 
> blkparse reliably seg faults at around 102 seconds into the log:
>   8,209  1     5749   102.246254903  4825  U   N [(null)] 2
>   8,113  4    10445   102.255427790     0  C   R 14356151 + 8 [10445]
> Segmentation fault
> 
> Stderror does have some strange output:
> 
> # blkparse btrfs-12-blk.log > /dev/null
> Bad magic 0
> Bad magic 0
> Bad magic 0
> Bad magic 8
> Bad magic 0
> Bad magic 0
> Bad magic 0
> Bad magic c2d3ccfa
> Segmentation fault
> 
> It generated 61,758 lines of output when it dies.
> 
> Additional information about this machine, it's an ubuntu 11.04 x86-64
> machine with:
> # uname -a
> Linux fb 2.6.38-8-server #42-Ubuntu SMP Mon Apr 11 03:49:04 UTC 2011
> x86_64 x86_64 x86_64 GNU/Linux
> # blkparse --version
> blkparse version 1.0.1
> # blktrace --version
> blktrace version 2.0.0
> 
> This doesn't seem like a particularly challenging log to handle.
> 
> I looked for a way to tell blkparse to use a larger buffer but I didn't
> see a way to do that with blkparse --help or the blkparse man page.
> 
> Stupid user error?  Suggestions?  I'm sending it to this list as
> directed by the man page.
would you mind providing a tar.gz for the btrfs-12-blk.log?

Regards,
Tao

  reply	other threads:[~2011-05-25  6:19 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 [this message]
2011-05-25  8:48 ` Bill Broadley
2011-05-25  8:51 ` Bill Broadley

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=4DDC9F60.9000507@tao.ma \
    --to=tm@tao.ma \
    --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 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.