Bug 207036 - ext3 recovery needed after reboot
Summary: ext3 recovery needed after reboot
Alias: None
Product: Fedora
Classification: Fedora
Component: initscripts
Version: 6
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
: 207117 (view as bug list)
Depends On:
Blocks: FC6Blocker
TreeView+ depends on / blocked
Reported: 2006-09-18 21:04 UTC by ctm
Modified: 2014-03-17 03:02 UTC (History)
3 users (show)

Clone Of:
Last Closed: 2006-10-10 16:13:28 UTC

Attachments (Terms of Use)
Portion of yum.log that lists updates between bad and good reboots (2.38 KB, text/plain)
2006-09-21 16:48 UTC, ctm
no flags Details

Description ctm 2006-09-18 21:04:49 UTC
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:
1. reboot
2. look for "INFO: recovery required"
Actual results:
Error message present

Expected results:
No error message

Additional info:
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).

Comment 1 Bill Nottingham 2006-09-19 14:57:13 UTC
*** Bug 207117 has been marked as a duplicate of this bug. ***

Comment 2 Janne Pikkarainen 2006-09-19 16:19:08 UTC
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.

Comment 3 ctm 2006-09-20 21:04:45 UTC
After upgrading to initscripts-8.41-1, I've rebooted my machine three times and no recovery has been 

Comment 4 Bill Nottingham 2006-09-21 15:54:10 UTC
That's... odd. Nothing of relevance changed in that area.

Comment 5 ctm 2006-09-21 16:16:49 UTC
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.

Comment 6 ctm 2006-09-21 16:48:35 UTC
Created attachment 136881 [details]
Portion of yum.log that lists updates between bad and good reboots

Comment 7 ctm 2006-09-21 16:51:13 UTC
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.

Comment 8 Bill Nottingham 2006-10-10 16:13:28 UTC
Closing, then - I can't reproduce this either. Please reopen if it comes back.

Note You need to log in before you can comment on or make changes to this bug.