Description of problem: When the machine is cleanly shut down and rebooted, the ext3 driver complains about the filesystem state and restores the journal during init. Cannot easily reproduce this, just happened after a clean test3 install, and a couple of times during test2, maybe after kernel or selinux related updates IIRC. How reproducible: Sometimes Steps to Reproduce: 1. Use the laptop for a while 2. (Maybe upgrade/install the new kernel?) 3. Reboot Actual Results: Filesystem is not left in a clean sate when unmounted Expected Results: No errors on boot after a clean shutdown
Also seen on my thinkpad 600, as if the 2.6 kernel isnt correctly cache flushing and powering down the drive
I'm still seing this after updating to kernel-2.6.5-1.356 Also (noticed with the same batch of updates from 5/8), is it really necessary to power off and spin down the hard disks on reboot? I haven't noticed this spinning down before these updates and certainly not with 2.4 kernels
... and with kernel-2.6.5-1.358 on a fresh FC2 install
this should be fixed now, as we flush just before the powerdown.