Red Hat Bugzilla – Bug 207036
ext3 recovery needed after reboot
Last modified: 2014-03-16 23:02:30 EDT
Description of problem:
After rebooting (via the command line "reboot" command or the Reboot button on the greeter), I get
kernel: EXT3-fs: INFO: recovery required on readonly filesystem.
sometimes I see orphan inodes deleted.
Version-Release number of selected component (if applicable):
How reproducible: 5 out of 5 reboots
Steps to Reproduce:
2. look for "INFO: recovery required"
Error message present
No error message
I'm marking this as initscripts, but I really don't know where the problem is. This is on completely new
FC6t3 installation (i.e. I didn't upgrade or reuse pre-existing filesystems).
*** Bug 207117 has been marked as a duplicate of this bug. ***
So I'm not the only one having this problem.
One thing I just noticed is that during shutdown the system complains something
about unable to unmount LVM volume group. This does not happen every time, though.
After upgrading to initscripts-8.41-1, I've rebooted my machine three times and no recovery has been
That's... odd. Nothing of relevance changed in that area.
Initscripts could be a red herring.
Typically I do yum update at least once a day, so much more than initscripts was updated, but the kernel
wasn't nor was SysVinit. I'll make the system reboot in a loop and see if I get any errors. I'll report back
either way, but if I don't get any errors, I'll attach a copy of my yum.log.
BTW, I removed orca, because I don't need it and it was interfering with my ability to update. I doubt
that's related, but I try to be complete.
Created attachment 136881 [details]
Portion of yum.log that lists updates between bad and good reboots
I've now done 10 reboots since my last round of yum updates. None of them required ext3 recovery.
Prior to that round of yum updates, 5 of the last 5 had recoveries. Attached to comment #6 is the portion
of yum.log that lists those updates.
I can provide copies of my messages file or other logs if it will help.
Closing, then - I can't reproduce this either. Please reopen if it comes back.