Skip to contentSkip to conversation

block_dump - full path ?

DISCUSSION [email protected] 2 participants 2 messages Sep 5, 2009 – Sep 6, 2009

lore
Share & tools
lore
#0 lore 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

#1 lore raw
Quoted 12 lines · On Sat, Sep 05, 2009 at 11:44:35PM +0200, [email protected] 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
Quoted 1 line

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