All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miao Xie <miaox@cn.fujitsu.com>
To: Manish Katiyar <mkatiyar@gmail.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>, Linux-Ext4 <linux-ext4@vger.kernel.org>
Subject: Re: [BUG][e2fsprogs] e2fsck: e2fsck reports ext3 message when checking ext4 filesystem
Date: Wed, 24 Dec 2008 15:34:01 +0800	[thread overview]
Message-ID: <4951E5E9.7080400@cn.fujitsu.com> (raw)
In-Reply-To: <ea11fea30812232040g1e939f87y6bfaf5e82df99dd1@mail.gmail.com>

on 2008-12-24 12:40 Manish Katiyar wrote:
> On Wed, Dec 24, 2008 at 8:44 AM, Miao Xie <miaox@cn.fujitsu.com> wrote:
>> 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"?
> 
> Because it is hardcoded :-(
> 
>>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

> 
> Thanks -
> Manish
> 
>> 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 majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
> 
> 
> 



  reply	other threads:[~2008-12-24  7:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-24  3:14 [BUG][e2fsprogs] e2fsck: e2fsck reports ext3 message when checking ext4 filesystem Miao Xie
2008-12-24  4:40 ` Manish Katiyar
2008-12-24  7:34   ` Miao Xie [this message]
2009-02-11  2:35   ` Miao Xie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4951E5E9.7080400@cn.fujitsu.com \
    --to=miaox@cn.fujitsu.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=mkatiyar@gmail.com \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.