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: <1520001043.24467.324.camel@infinera.com>
Date:   Fri, 2 Mar 2018 14:30:45 +0000
From:   Joakim Tjernlund <Joakim.Tjernlund@...inera.com>
To:     "lczerner@...hat.com" <lczerner@...hat.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 Fri, 2018-03-02 at 13:56 +0100, Lukas Czerner wrote:
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
> 
> 
> 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.

Not quite, I have a ext4 FS and fstab looks:
LABEL=BOOT		/boot		auto		noatime		1 2

and then I always get this error as kernel tries ext3 first, reports a big fat error,
then kernel tries ext4 and succeeds. I think this should be allowed without having
an error msg printed.

> 
> 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

cu3-jocke ~ # uname -a
Linux cu3-jocke 4.14.12+ #6 SMP Thu Feb 8 14:05:02 CET 2018 ppc e5500 GNU/Linux
cu3-jocke ~ # tune2fs -l /dev/mmcblk0p1
tune2fs 1.43.6 (29-Aug-2017)
Filesystem volume name:   BOOT
Last mounted on:          /boot
Filesystem UUID:          f0a6a649-ce97-4d82-b190-eb1fc3e348a2
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg
sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags:         unsigned_directory_hash 
Default mount options:    user_xattr acl discard
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              32768
Block count:              131072
Reserved block count:     6553
Free blocks:              116724
Free inodes:              32710
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      31
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
Flex block group size:    16
Filesystem created:       Mon Dec 11 17:21:11 2017
Last mount time:          Fri Mar  2 13:36:36 2018
Last write time:          Fri Mar  2 13:36:36 2018
Mount count:              65
Maximum mount count:      -1
Last checked:             Mon Dec 11 17:21:11 2017
Check interval:           0 (<none>)
Lifetime writes:          171 MB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:	          256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      52d5b1f5-a98f-43cd-aa48-f9cd3cfa32ea
Journal backup:           inode blocks