Hopefully, someone can tell me if this is OK.
I recently had a problem with my system and had to do a complete
restore. Fortunately, I had made a full backup just the day before. My
filesystems are Ext3 (why else would I be posting this here?). :)
Anyway, when I originally changed my filesystems from Ext2 to Ext3, I
did while they were still mounted. As a result, the journal file was
visible.
Now, after the system restore, I can find no journal files at all. I
thought maybe it was now a hidden (.journal) file but no such thing is
present. Looking at dmesg, everything seems to have booted up normally.
All Ext3 messages are fine... no errors.
My question is, how can I know for sure if everything really IS fine? I
did a tune2fs -l on one of my filesystems. I don't know if it's any help
but here is the output.
Any help is appreciated!
Rick
tune2fs 1.32 (09-Nov-2002)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: f2c11886-c1cc-4b75-8cc2-96f72be630e9
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal dir_index filetype needs_recovery
sparse_super
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 1766016
Block count: 3528267
Reserved block count: 176413
Free blocks: 1805916
Free inodes: 1354924
First block: 0
Block size: 4096
Fragment size: 4096
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 16352
Inode blocks per group: 511
Last mount time: Fri Nov 22 10:53:26 2002
Last write time: Fri Nov 22 10:53:26 2002
Mount count: 7
Maximum mount count: 27
Last checked: Thu Nov 21 23:20:28 2002
Check interval: 15552000 (6 months)
Next check after: Wed May 21 00:20:28 2003
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Journal UUID: <none>
Journal inode: 8
Journal device: 0x0000
First orphan inode: 0
Default directory hash: tea
Directory Hash Seed: a288fa3f-abf8-4e0a-91cc-a6ed6f58e8b5