From: devzero@web.de
To: linux-kernel@vger.kernel.org
Subject: block_dump - full path ?
Date: Sat, 05 Sep 2009 23:44:35 +0200 [thread overview]
Message-ID: <899288751@web.de> (raw)
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 ?
i assume it is a missing feature, correct ?
what about adding full path support, to be enabled with "sysctl vm.block_dump=2" ?
regards
roland
______________________________________________________
GRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://movieflat.web.de
next reply other threads:[~2009-09-05 21:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-05 21:44 devzero [this message]
2009-09-06 15:51 ` Theodore Tso
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=899288751@web.de \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome