Messages in this thread | | | Date | Thu, 15 Nov 2001 13:10:31 -0800 | From | Andrew Morton <> | Subject | Re: Bug in ext3 |
| |
Ben Collins wrote: > > Seems it does have the field set. I guess the bug is then that if there > is no journal, then it shoudl fail to mount it, so ext2 will take over. > Is there any reason to mount a partition as ext3 if there is no journal > to be found? > > Filesystem volume name: <none> > Last mounted on: <not available> > Filesystem UUID: <none> > Filesystem magic number: 0xEF53 > Filesystem revision #: 1 (dynamic) > Filesystem features: has_journal filetype sparse_super > Filesystem state: not clean > Errors behavior: Continue > Filesystem OS type: Linux > Inode count: 1015808 > Block count: 2028288 > Reserved block count: 101414 > Free blocks: 372624 > Free inodes: 690438 > First block: 0 > Block size: 4096 > Fragment size: 4096 > Blocks per group: 32768 > Fragments per group: 32768 > Inodes per group: 16384 > Inode blocks per group: 512 > Last mount time: Thu Nov 15 10:07:12 2001 > Last write time: Thu Nov 15 15:55:23 2001 > Mount count: 2 > Maximum mount count: 20 > Last checked: Thu Nov 15 08:48:40 2001 > Check interval: 15552000 (6 months) > Next check after: Tue May 14 09:48:40 2002 > Reserved blocks uid: 0 (user root) > Reserved blocks gid: 0 (group root) > First inode: 11 > Inode size: 128
Are you running a current version of e2fsprogs? 1.25?
If you are, then this indicates that the filesystem has has_journal set, but it doesn't have a journal inode. That is certainly something which e2fsck should detect and fix. This may be a fsck bug.
You should be able to fix this with `tune2fs -O ^has-journal' on the unmounted or readonly fs. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |