billionmonkeys
February 25th, 2007, 12:24 AM
I've got a myth box running edgy and a 2.6.19 kernel, and kjournald seems to access the disk constantly (the hd light flashes roughly 3 times per second when the system is idle)
here is an example: i did this:
echo 1 >/proc/sys/vm/block_dump
wait 12 seconds
echo 0 >/proc/sys/vm/block_dump
[ 6691.516770] kjournald(1813): WRITE block 710949504 on sda1
[ 6691.516781] kjournald(1813): WRITE block 709925704 on sda1
[ 6691.516786] kjournald(1813): WRITE block 709925632 on sda1
[ 6691.516790] kjournald(1813): WRITE block 709925712 on sda1
[ 6691.516988] kjournald(1813): WRITE block 197976 on sda1
[ 6691.516993] kjournald(1813): WRITE block 197984 on sda1
[ 6691.516996] kjournald(1813): WRITE block 197992 on sda1
[ 6691.516999] kjournald(1813): WRITE block 198000 on sda1
[ 6691.517003] kjournald(1813): WRITE block 198008 on sda1
[ 6691.517006] kjournald(1813): WRITE block 198016 on sda1
[ 6691.517009] kjournald(1813): WRITE block 198024 on sda1
[ 6691.517120] kjournald(1813): WRITE block 198032 on sda1
[ 6693.789685] kjournald(1813): WRITE block 710949504 on sda1
[ 6693.789698] kjournald(1813): WRITE block 709925712 on sda1
[ 6693.789704] kjournald(1813): WRITE block 709925632 on sda1
[ 6693.789891] kjournald(1813): WRITE block 198040 on sda1
[ 6693.789895] kjournald(1813): WRITE block 198048 on sda1
[ 6693.789899] kjournald(1813): WRITE block 198056 on sda1
[ 6693.789902] kjournald(1813): WRITE block 198064 on sda1
[ 6693.789977] kjournald(1813): WRITE block 198072 on sda1
[ 6696.037396] bash(7073): dirtied inode 4026531947 (block_dump) on proc
so you can see that kjournald is doing most of the disk activity. Whats strange to me is that it seems to be writing the same blocks over and over, I've seen some of those blocks written multiple times in multiple instances of the above test.
So my questions:
- why does kjournald do this? what is it doing?
- how do I make it stop?
many thanks for any help
here is an example: i did this:
echo 1 >/proc/sys/vm/block_dump
wait 12 seconds
echo 0 >/proc/sys/vm/block_dump
[ 6691.516770] kjournald(1813): WRITE block 710949504 on sda1
[ 6691.516781] kjournald(1813): WRITE block 709925704 on sda1
[ 6691.516786] kjournald(1813): WRITE block 709925632 on sda1
[ 6691.516790] kjournald(1813): WRITE block 709925712 on sda1
[ 6691.516988] kjournald(1813): WRITE block 197976 on sda1
[ 6691.516993] kjournald(1813): WRITE block 197984 on sda1
[ 6691.516996] kjournald(1813): WRITE block 197992 on sda1
[ 6691.516999] kjournald(1813): WRITE block 198000 on sda1
[ 6691.517003] kjournald(1813): WRITE block 198008 on sda1
[ 6691.517006] kjournald(1813): WRITE block 198016 on sda1
[ 6691.517009] kjournald(1813): WRITE block 198024 on sda1
[ 6691.517120] kjournald(1813): WRITE block 198032 on sda1
[ 6693.789685] kjournald(1813): WRITE block 710949504 on sda1
[ 6693.789698] kjournald(1813): WRITE block 709925712 on sda1
[ 6693.789704] kjournald(1813): WRITE block 709925632 on sda1
[ 6693.789891] kjournald(1813): WRITE block 198040 on sda1
[ 6693.789895] kjournald(1813): WRITE block 198048 on sda1
[ 6693.789899] kjournald(1813): WRITE block 198056 on sda1
[ 6693.789902] kjournald(1813): WRITE block 198064 on sda1
[ 6693.789977] kjournald(1813): WRITE block 198072 on sda1
[ 6696.037396] bash(7073): dirtied inode 4026531947 (block_dump) on proc
so you can see that kjournald is doing most of the disk activity. Whats strange to me is that it seems to be writing the same blocks over and over, I've seen some of those blocks written multiple times in multiple instances of the above test.
So my questions:
- why does kjournald do this? what is it doing?
- how do I make it stop?
many thanks for any help