Steve Snyder wrote:
I got the ext3 recovery sequence of messages below in my system log today.
Here's what I did prior to the recovery being needed:
1. Rebooted into single mode by puting "single" on the kernel command
line.
2. Ran "prelink -aR". No errors were shown.
3. Shut down with the command "shutdown -h now; exit".
All perfectly proper. So why when the system came back up again was a
"recovery required" of the filesystem?
Thanks.
---------------------
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
EXT3-fs: ide0(3,1): orphan cleanup on readonly fs
ext3_orphan_cleanup: deleting unreferenced inode 337844
ext3_orphan_cleanup: deleting unreferenced inode 176765
ext3_orphan_cleanup: deleting unreferenced inode 337406
EXT3-fs: ide0(3,1): 3 orphan inodes deleted
EXT3-fs: recovery complete.
------------------------
I just did a mke2fs recently, and it said something about doing a
required fs check after so many reboots. Perhaps you reached the default
limit? I did not pay much attention to the message, but I think it was
something like every 37 reboots....
--
Shrike-list mailing list
Shrike-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/shrike-list
