SEO

#1 (**permalink**) 02-21-2008, 11:05 AM

file -s showed that each ext3 partition needed journal recovery.
Although the check at boot showed clean and I noticed no problems using
the system, I booted off a Knoppix cd and ran fsck.ext3 on hda6 (home)
and 7 (root). No errors found. Rebooted into Gentoo. For both home
and root, I got, "It's been 49,710 days since last mount, check
forced." (136 years?) No errors. file -s still shows "journal needs
recovery." Is this just some artifact with no relation to any reality?

--

#2 (**permalink**) 02-21-2008, 11:05 AM

Ed <edjlb@yahoo.com> writes:
>file -s showed that each ext3 partition needed journal recovery.
>Although the check at boot showed clean and I noticed no problems using
>the system, I booted off a Knoppix cd and ran fsck.ext3 on hda6 (home)
>and 7 (root). No errors found. Rebooted into Gentoo. For both home
>and root, I got, "It's been 49,710 days since last mount, check
>forced." (136 years?)

Apparently Knoppix set the last-mounted time wrong.

> No errors. file -s still shows "journal needs
>recovery."

A mounted ext3 file system always has this flag set; this is cleared
when the file system is unmounted. So when you do a clean unmount, no
recovery journal happens, but if you don't, you will get a recovery.
This is just like the "unclean" status of an ext2 file system, except
that unclean ext2 file systems are fscked. However, the message is
more informative for ext2 file systems:

[/home/anton:3220]# file -s /dev/hdb15
/dev/hdb15: Linux rev 1.0 ext2 filesystem data (mounted or unclean)

- anton
--
M. Anton Ertl Some things have to be seen to be believed
anton@mips.complang.tuwien.ac.at Most things have to be believed to be seen
http://www.complang.tuwien.ac.at/anton/home.html

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Fun with ext3 journal.