From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756825AbbIUN1n (ORCPT ); Mon, 21 Sep 2015 09:27:43 -0400 Received: from [62.179.121.39] ([62.179.121.39]:60599 "EHLO fep19.mx.upcmail.net" rhost-flags-FAIL-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1756775AbbIUN12 (ORCPT ); Mon, 21 Sep 2015 09:27:28 -0400 X-SourceIP: 2001:470:25:65c::2 X-Authenticated-Sender: odi.ch@hispeed.ch To: Chris Clayton , "linux-kernel@vger.kernel.org" From: =?UTF-8?Q?Ortwin_Gl=c3=bcck?= Subject: Re: EXT4: new warnings from 4.3.0-rc2 Message-ID: <560005B3.7030904@odi.ch> Date: Mon, 21 Sep 2015 15:27:15 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > [ 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_block_root()). Since the removal of ext3, now the ext4 code is responsbile for mounting ext3. Since your FS is ext4 and not ext3, the probe for ext3 fails. That's what the message tells you. You get these even in previous kernels if you say N to ext3 during config. If it bugs you, you can add a hint to your kernel command line: rootfstype=ext4 Ortwin