From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
Date: Tue, 24 May 2016 14:37:23 +0000 [thread overview]
Message-ID: <bug-118401-13602-g6eHUpi4JY@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-118401-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=118401
--- Comment #7 from Theodore Tso <tytso@mit.edu> ---
The ext4 file system will happily mount file systems that are intended for ext2
and ext3. That is, ext4 supports a superset of the features supported by the
ext2 and ext3 file system implementations.
The CONFIG_EXT4_USE_FOR_EXT23 (before ext3 dropped was dropped) and
CONFIG_EXT4_USE_FOR_EXT2 (after the ext3 driver was dropped) merely determines
whether or not ext4 claims to be the ext2 or ext3 drivers. This matters only
if the file system type is explicitly used in the mount command (e.g., "mount
-t ext3 ...") or if you are mounting a non-root file system in /etc/fstab.
Now, the distribution is doing something wierd with initramfs, so it's possible
this is the cause of the issue, but when the kernel is mounting the root file
system it will try using all of the file systems available to it to try to
mount it.
Furthermore the error message of not being able to find the file system with
the specific UUID isn't the error message in the boot logs that would indicate
that the problem was that the initramfs was trying to mount with ext3 and
failed to find it.
Still, if you want to try compiling with CONFIG_EXT4_USE_FOR_EXT2, that
certainly wouldn't hurt and would probably help once you get the system
working.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2016-05-24 14:37 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 11:41 [Bug 118401] New: Lenovo A740 gave up waiting for root device with kernels >= 4.3 bugzilla-daemon
2016-05-18 16:02 ` [Bug 118401] " bugzilla-daemon
2016-05-19 8:40 ` bugzilla-daemon
2016-05-19 8:42 ` bugzilla-daemon
2016-05-19 8:43 ` bugzilla-daemon
2016-05-19 8:56 ` bugzilla-daemon
2016-05-24 13:07 ` bugzilla-daemon
2016-05-24 14:37 ` bugzilla-daemon [this message]
2016-05-24 17:46 ` bugzilla-daemon
2016-05-31 5:51 ` bugzilla-daemon
2016-06-01 15:26 ` bugzilla-daemon
2016-06-01 16:02 ` bugzilla-daemon
2016-06-01 18:53 ` bugzilla-daemon
2016-06-01 21:50 ` bugzilla-daemon
2016-06-02 10:28 ` bugzilla-daemon
2016-06-02 12:52 ` bugzilla-daemon
2016-06-02 18:19 ` bugzilla-daemon
2016-06-03 19:03 ` bugzilla-daemon
2016-06-03 19:04 ` bugzilla-daemon
2016-06-03 19:07 ` bugzilla-daemon
2016-06-03 19:08 ` bugzilla-daemon
2016-06-04 6:28 ` bugzilla-daemon
2016-06-04 9:36 ` bugzilla-daemon
2016-06-04 13:45 ` bugzilla-daemon
2016-06-04 22:05 ` bugzilla-daemon
2016-06-05 1:46 ` bugzilla-daemon
2016-06-05 11:12 ` bugzilla-daemon
2016-06-05 11:14 ` bugzilla-daemon
2016-06-05 12:21 ` bugzilla-daemon
2016-06-05 13:43 ` bugzilla-daemon
2016-06-06 7:27 ` bugzilla-daemon
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=bug-118401-13602-g6eHUpi4JY@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).