From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 109331] New: EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities
Date: Mon, 14 Dec 2015 04:26:05 +0000 [thread overview]
Message-ID: <bug-109331-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=109331
Bug ID: 109331
Summary: EXT4-fs (sda1): couldn't mount as ext3 due to feature
incompatibilities
Product: File System
Version: 2.5
Kernel Version: 3.4.2
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: 3fdd1e5d@opayq.com
Regression: No
Created attachment 197281
--> https://bugzilla.kernel.org/attachment.cgi?id=197281&action=edit
config-4.3.2
I compiled 4.3.2 and when I was looking over the logs I noticed this message in
dmesg;
EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities
I personally don't get this message, as to why the kernel is trying to mount
ext4 as ext3? Or at least it's the way the message comes across.
Can't say I've ever seen anything like this before in the kernel logs...
Hmm
I've attached my config
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2015-12-14 4:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 4:26 bugzilla-daemon [this message]
2015-12-14 4:26 ` [Bug 109331] EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities bugzilla-daemon
2015-12-14 4:30 ` bugzilla-daemon
2015-12-14 5:02 ` bugzilla-daemon
2015-12-14 16:12 ` bugzilla-daemon
2015-12-14 21:19 ` bugzilla-daemon
2015-12-15 0:51 ` bugzilla-daemon
2015-12-15 6:59 ` bugzilla-daemon
2016-04-13 20:35 ` bugzilla-daemon
2020-05-28 4:55 ` 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-109331-13602@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