On Mon, 21 Sep 2015 16:08:59 +0100, Chris Clayton wrote:
> Applying the 4.2.1-rc1 patch results in a kernel that emits the messages,
> so I guess my fix-not-yet-in-4.2 theory is right.
I have been getting these forever since I switched to ext4-for-ext3,
at least since early last year - if not lon
On 09/21/15 15:55, Chris Clayton wrote:
> Thanks Ortwin.
>
> On 09/21/15 14:27, Ortwin Glück wrote:
>>> [2.481399] EXT4-fs (sda2): couldn't mount as ext3 due to feature
>>> incompatibilities
>>> [2.482426] EXT4-fs (sda2): couldn't mount as ext2 due to feature
>>> incompatibilities
>>
Thanks Ortwin.
On 09/21/15 14:27, Ortwin Glück wrote:
>> [2.481399] EXT4-fs (sda2): couldn't mount as ext3 due to feature
>> incompatibilities
>> [2.482426] EXT4-fs (sda2): couldn't mount as ext2 due to feature
>> incompatibilities
>
> As the kernel doesn't know which FS your root is,
> [2.481399] EXT4-fs (sda2): couldn't mount as ext3 due to feature
incompatibilities
> [2.482426] EXT4-fs (sda2): couldn't mount as ext2 due to feature
incompatibilities
As the kernel doesn't know which FS your root is, it tries the whole list of filesystems
(init/do_mounts.c mount_blo
Hi,
I've just built and booted 4.3.0-rc2 and I'm seeing the following new messages
on the console during boot up:
[2.481399] EXT4-fs (sda2): couldn't mount as ext3 due to feature
incompatibilities
[2.482426] EXT4-fs (sda2): couldn't mount as ext2 due to feature
incompatibilities
They
5 matches
Mail list logo