public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 109331] EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities
Date: Mon, 14 Dec 2015 21:19:27 +0000	[thread overview]
Message-ID: <bug-109331-13602-B9gl8Udf9Q@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-109331-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=109331

--- Comment #4 from KernelBug <3fdd1e5d@opayq.com> ---
I'm running Slackware 14.1 x86_64 I formatted during the install as ext4.


file -s /dev/sda1

/dev/sda1: Linux rev 1.0 ext4 filesystem data,
UUID=7d75a56d-fa34-48c5-a278-45ede11df261 (needs journal recovery) (extents)
(large files) (huge files)

I don't claim to know everything as a Slacker, LOL, so either I forgot, or
didn't realize that the kernel is going to try each FS until it finds the one
compiled in.

Either way, this message shouldn't be appearing, telling us what we know
already, which is of course you can't load ext3 when you have it compiled for
ext4, such a pointless message...

Please let's get this fixed or silenced...

thanks

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2015-12-14 21:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-14  4:26 [Bug 109331] New: EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities bugzilla-daemon
2015-12-14  4:26 ` [Bug 109331] " 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 [this message]
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-B9gl8Udf9Q@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