From: Theodore Tso <tytso@mit.edu>
To: devzero@web.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: block_dump - full path ?
Date: Sun, 6 Sep 2009 11:51:47 -0400 [thread overview]
Message-ID: <20090906155147.GH3055@mit.edu> (raw)
In-Reply-To: <899288751@web.de>
On Sat, Sep 05, 2009 at 11:44:35PM +0200, devzero@web.de wrote:
> Hi,
>
> i came across the nice debugging feature sysctl vm.block_dump=1 which leaves information on read/write in dmesg for every process.
>
> Sep 5 20:11:15 neoware kernel: kjournald(423): WRITE block 155542512 on sda2
> Sep 5 20:11:15 neoware kernel: kjournald(423): WRITE block 155542520 on sda2
> Sep 5 20:11:15 neoware kernel: kjournald(423): WRITE block 155542528 on sda2
> Sep 5 20:11:19 neoware kernel: pdflush(14): WRITE block 144498288 on sda2
> Sep 5 20:11:19 neoware kernel: pdflush(14): WRITE block 144916496 on sda2
> Sep 5 20:11:19 neoware kernel: pdflush(14): WRITE block 144917376 on sda2
> Sep 5 20:11:19 neoware kernel: pdflush(14): WRITE block 144704600 on sda2
>
> is it possible to log the full path of the process ?
What do you mean by "the full path of the process"? Do you mean the
full path of the process' executable? (In this case kjournald and
pdflush are kernel threads so there is no executable, and thus there
is no "full path". unless you mean pathname to the kernel, i.e., /vmlinux.)
Or did you mean the full path name of the file associated with the
block number? In this case, kjournald is writing to the file system
journal, which has no pathname. pdflush is writing dirty pages from
the page cache, which could be mapped to file names, but it would take
up a huge amount of space in the log -- but to what effect?
What exactly are you trying to do? There might be a more efficient
way of gathering whatever data you are trying to get for your experiment.
- Ted
next prev parent reply other threads:[~2009-09-06 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-05 21:44 block_dump - full path ? devzero
2009-09-06 15:51 ` Theodore Tso [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-06 16:14 devzero
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=20090906155147.GH3055@mit.edu \
--to=tytso@mit.edu \
--cc=devzero@web.de \
--cc=linux-kernel@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.