linux-ext4 - Re: EXT4-fs (mmcblk0p1): couldn't mount as ext3 due to feature incompatibilities

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180302125624.ybyzy2xjvjitc5c2@rh_laptop>
Date:   Fri, 2 Mar 2018 13:56:24 +0100
From:   Lukas Czerner <lczerner@...hat.com>
To:     Joakim Tjernlund <Joakim.Tjernlund@...inera.com>
Cc:     "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: EXT4-fs (mmcblk0p1): couldn't mount as ext3 due to feature
 incompatibilities

On Thu, Mar 01, 2018 at 12:48:58PM +0000, Joakim Tjernlund wrote:
> Could the above(for ext2 as well) be removed or changed to a non error msg ?
> It looks like a serious error msg as is now.
> 
>  Jocke

You're trying to mount a file system with features that a kernel you're
currently using can't recognize or is incompatible with. So no, the
error can't be just removed, it's there to prevent any further damage.

Given that this is a memory card it's likely that it was made on a
different OS with a defferent e2fsprogs version or a different setting
and the kernel you're trying to mount it into is likely older.

Please show the output of the following commands

uname -a
sudo tune2fs -l /dev/mmcblk0p1

You can also try to mount the file system read only which may work if
the feature in question is RO compatible.

-Lukas