From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@kernel.org
Subject: [Bug 194567] New: ext4 no longer mounts
Date: Sun, 12 Feb 2017 20:55:10 +0000 [thread overview]
Message-ID: <bug-194567-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=194567
Bug ID: 194567
Summary: ext4 no longer mounts
Product: File System
Version: 2.5
Kernel Version: 4.4.48
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: bugzilla.kernel.org@plan9.de
Regression: No
I have a single ext4 filesystem on my workstatioon used to host mysql database
files. I don't know how old it is (months, years), but I happen to keep the
mkfs command used to create it (the device is 67108864 sectors):
mke2fs -t ext4 -b 4096 -N 65536 -I 128 -L DB -m 0 -O
dir_index,extent,filetype,flex_bg,^has_journal,large_file,^resize_inode,sparse_super,uninit_bg
It worked fine till 4.4.47. it no longer mounts in 4.4.48:
[ 206.596713] EXT4-fs (dm-24): VFS: Can't find ext4 filesystem
[ 214.028205] EXT4-fs (dm-24): first meta block group too large: 2 (group
descriptor block count 2)
[ 242.185792] EXT4-fs (dm-24): first meta block group too large: 2 (group
descriptor block count 2)
e2fsck -f (from "e2fsck 1.43.4 (31-Jan-2017)") finds no errors. Not sure if
this is a bug in mkfs, e2fsck, or the kernel, but since it is a regression in
the kernel, I reported it here.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2017-02-12 20:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-12 20:55 bugzilla-daemon [this message]
2017-02-13 4:00 ` [Bug 194567] ext4 no longer mounts bugzilla-daemon
2017-02-13 14:59 ` bugzilla-daemon
2017-02-15 6:29 ` bugzilla-daemon
2017-02-15 11:30 ` bugzilla-daemon
2017-02-15 23:46 ` 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-194567-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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