dumpe2fs and external journal: Illegal inode number while reading journal inode
Ralf Hildebrandt
Ralf.Hildebrandt at charite.de
Wed Feb 25 17:20:36 UTC 2009
I created an ext4 fs with an external journal.
I wanted to check how big the journal was, and tried:
# dumpe2fs -h /dev/mapper/volg1-logv1
dumpe2fs 1.41.3 (12-Oct-2008)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: 032613d3-6035-4872-bc0a-11db92feec5e
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal resize_inode dir_index filetype
needs_recovery extent sparse_super large_file uninit_bg
Filesystem flags: signed_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 19519488
Block count: 624605184
Reserved block count: 0
Free blocks: 257817321
Free inodes: 10481629
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 875
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 1024
Inode blocks per group: 32
Filesystem created: Tue May 8 21:04:31 2007
Last mount time: Wed Feb 25 18:01:47 2009
Last write time: Wed Feb 25 18:01:47 2009
Mount count: 19
Maximum mount count: -1
Last checked: Sat Dec 27 23:16:47 2008
Check interval: 0 (<none>)
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Journal UUID: 1a7063f5-8965-40f2-9feb-e37d6ac467e9
Journal device: 0x6806
First orphan inode: 622943
Default directory hash: tea
Directory Hash Seed: 44337061-e542-44bb-afb9-40597ccf1c6d
Journal backup: inode blocks
dumpe2fs: Illegal inode number while reading journal inode
--
Ralf Hildebrandt Ralf.Hildebrandt at charite.de
Charite - Universitätsmedizin Berlin Tel. +49 (0)30-450 570-155
Geschäftsbereich IT | Abt. Netzwerk Fax. +49 (0)30-450 570-962
Hindenburgdamm 30 | 12200 Berlin
More information about the Ext3-users
mailing list