e2fsck: e2fsck reports ext3 message when checking ext4 filesystem

BUG Miao Xie 2 participants 4 messages Dec 24, 2008 – Feb 11, 2009

lore

Share & tools

lore

Miao Xie

author

2008-12-24 03:16 UTC #0 lore raw

Hi,

I use "e2fsck" to repair the damaged ext4 device.

The message was followings.

------

# ./e2fsck /dev/sdb3
e2fsck 1.41.3 (12-Oct-2008)
Superblock has an invalid ext3 journal (inode 8).
Clear<y>?
---

Why e2fsck tells me "ext3"? It looks the message was wrong or e2fsck doesn't recognize ext4 correctly.

Thanks！
Miao Xie

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Manish Katiyar

2008-12-24 04:40 UTC #1 lore raw

Quoted 6 lines · Miao Xie

Hi,
I use "e2fsck" to repair the damaged ext4 device.
The message was followings.

Quoted 8 lines

------

# ./e2fsck /dev/sdb3
e2fsck 1.41.3 (12-Oct-2008)
Superblock has an invalid ext3 journal (inode 8).
Clear<y>?
---

Why e2fsck tells me "ext3"?

Because it is hardcoded :-(

Quoted 1 line

From the file e2fsprogs/po/id.po :-

#. @-expanded: superblock has an invalid ext3 journal (inode %i).\n #: e2fsck/problem.c:187
#, c-format
msgid "@S has an @n ext3 @j (@i %i).\n"
msgstr "@S memiliki sebuah @n ext3 @j (@i %i).\n"

Thanks -
Manish

Quoted 11 lines

It looks the message was wrong
or e2fsck doesn't recognize ext4 correctly.
Thanks！
Miao Xie
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Miao Xie

author

2008-12-24 07:36 UTC #2 lore raw

Quoted 18 lines · on 2008-12-24 12:40 Manish Katiyar wrote:

Quoted 6 lines · Miao Xie
Hi,
I use "e2fsck" to repair the damaged ext4 device.
The message was followings.
Quoted 8 lines
------
# ./e2fsck /dev/sdb3
e2fsck 1.41.3 (12-Oct-2008)
Superblock has an invalid ext3 journal (inode 8).
Clear<y>?
---
Why e2fsck tells me "ext3"?
Because it is hardcoded :-(

Quoted 7 lines

Quoted 1 line
From the file e2fsprogs/po/id.po :-
#. @-expanded: superblock has an invalid ext3 journal (inode %i).\n #: e2fsck/problem.c:187
#, c-format
msgid "@S has an @n ext3 @j (@i %i).\n"
msgstr "@S memiliki sebuah @n ext3 @j (@i %i).\n"

I see.
I think e2fsck should tell the correct information, so this problem must be fixed.

Thanks.
Miao Xie

Quoted 18 lines

Thanks -
Manish
Quoted 11 lines
It looks the message was wrong
or e2fsck doesn't recognize ext4 correctly.
Thanks！
Miao Xie
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Miao Xie

author

2009-02-11 02:37 UTC #3 lore raw

In reply to Manish Katiyar

Quoted 18 lines · on 2008-12-24 12:40 Manish Katiyar wrote:

Quoted 6 lines · Miao Xie
Hi,
I use "e2fsck" to repair the damaged ext4 device.
The message was followings.
Quoted 8 lines
------
# ./e2fsck /dev/sdb3
e2fsck 1.41.3 (12-Oct-2008)
Superblock has an invalid ext3 journal (inode 8).
Clear<y>?
---
Why e2fsck tells me "ext3"?
Because it is hardcoded :-(

Quoted 7 lines

Quoted 1 line
From the file e2fsprogs/po/id.po :-
#. @-expanded: superblock has an invalid ext3 journal (inode %i).\n #: e2fsck/problem.c:187
#, c-format
msgid "@S has an @n ext3 @j (@i %i).\n"
msgstr "@S memiliki sebuah @n ext3 @j (@i %i).\n"

someone submitted a patch to fix this bug. I tested it and the test was pass. But I found the translation is not updated.

Thanks!
Miao

Quoted 19 lines

Thanks -
Manish
Quoted 11 lines
It looks the message was wrong
or e2fsck doesn't recognize ext4 correctly.
Thanks！
Miao Xie
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html