I suggest you start by simply echo "1" >/proc/sys/vm/block_dump and turning off klogd
http://linux.inet.hr/proc_sys_vm_block_dump.html If it is not enough, search the archive for a similar discussion i had a year ago. There is a code in the kernel where the block_dump is hooked thus, you can find out a lot just by looking in there. On Sunday 18 June 2006 17:05, Michael Sternberg wrote: > We have to write driver that intercept all I/O to disk and notifies > user-mode application with following data: block length and device number. > What is a proper way to implement it: to write a block driver above disk > layer or to implement a file system filter ? If we'll implement a file > system filter could we miss some direct I/O to the disk ? What kind of I/O > could we miss ? > > ================================================================= > To unsubscribe, send mail to [EMAIL PROTECTED] with > the word "unsubscribe" in the message body, e.g., run the command > echo unsubscribe | mail [EMAIL PROTECTED] -- Regards, Tzahi. -- Tzahi Fadida Blog: http://tzahi.blogsite.org | Home Site: http://tzahi.webhop.info WARNING TO SPAMMERS: see at http://members.lycos.co.uk/my2nis/spamwarning.html ================================================================To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
