Red Hat Bugzilla – Bug 149133
kjournald writes to disc non-stop
Last modified: 2015-01-04 17:17:02 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0 StumbleUpon/1.9991
Description of problem:
I have an smp system and a laptop and both have kjournald writing to disc non-stop.
This problem doesn't happen right away. But after a few weeks of running the system it seems to get progressively worse.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.start the system
Actual Results: kjournald starts writing to disc non-stop
Expected Results: quiet harddrive
Note that this problem can be somewhat controlled by e.g. starting the laptop
without ac, then plugging once booted. Or sometimes by unplugging then
replugging the power cord.
It seems like something is going on with acpi.
could be the memory leak that was fixed recently. Can you try the kernel at
http://people.redhat.com/davej/kernels/Fedora/FC3/ please ?
no change to disk activity. here is a sample of the dmesg output when block_dump
kjournald(471): WRITE block 42616 on dm-0
kjournald(471): WRITE block 42624 on dm-0
kjournald(471): WRITE block 42632 on dm-0
kjournald(471): WRITE block 42640 on dm-0
kjournald(471): WRITE block 42648 on dm-0
kjournald(471): WRITE block 42656 on dm-0
kjournald(471): WRITE block 42664 on dm-0
it runs through blocks like this 8 at a time. but like I said, messing around
with how it's plugged in at bootup and then unplugging - replugging etc makes it
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem. Please update to this new kernel, and
report whether or not it fixes your problem.
If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.
This bug has been automatically closed as part of a mass update.
It had been in NEEDINFO state since July 2005.
If this bug still exists in current errata kernels, please reopen this bug.
There are a large number of inactive bugs in the database, and this is the only
way to purge them.