From: Matthias Prager <linux@matthiasprager.de>
To: linux-f2fs-devel@lists.sourceforge.net
Cc: Matthias Prager <linux@matthiasprager.de>
Subject: [BUG] f2fs: mounting with kernel >= 4.5.0 fails
Date: Sun, 20 Mar 2016 22:53:19 +0100 [thread overview]
Message-ID: <56EF1BCF.5010809@matthiasprager.de> (raw)
Hello,
since kernel 4.5.0 I'm unable to mount f2fs filesystems with costom
section sizes.
I use 1 GiB section sizes (for smr-hdds). A filesystem created with the
command:
> mkfs.f2fs -l test2 -o 0 -a 0 -s 9 /dev/sdj
fails to mount in kernel 4.5.0 with the following dmesg output (3TB hdd):
> [ 263.898973] F2FS-fs (sdj): Wrong MAIN_AREA boundary, start(1502208) end(732566528) blocks(731063808)
> [ 263.898977] F2FS-fs (sdj): Can't find valid F2FS filesystem in 1th superblock
> [ 263.899142] F2FS-fs (sdj): Wrong MAIN_AREA boundary, start(1502208) end(732566528) blocks(731063808)
> [ 263.899144] F2FS-fs (sdj): Can't find valid F2FS filesystem in 2th superblock
> [ 263.899148] F2FS-fs (sdj): Wrong MAIN_AREA boundary, start(1502208) end(732566528) blocks(731063808)
> [ 263.899150] F2FS-fs (sdj): Can't find valid F2FS filesystem in 1th superblock
> [ 263.899152] F2FS-fs (sdj): Wrong MAIN_AREA boundary, start(1502208) end(732566528) blocks(731063808)
> [ 263.899154] F2FS-fs (sdj): Can't find valid F2FS filesystem in 2th superblock
It makes no difference whether the fs is created using kernel 4.5.0 or
earlier kernels (f2fs-tools are version 1.6.0 from gentoo stable, I
tested kernels 4.1.19, 4.3.3 and 4.4.6).
Using the command:
> mkfs.f2fs -l test2 -o 0 -a 0 /dev/sdj
instead (without the '-s 9' parameter), the fs is mountable with kernel
4.5.0 without any issues.
(The other parameters make no difference - i.e. 'mkfs.f2fs /dev/sdj' is
fine for kernel 4.5.0, 'mkfs.f2fs -s 9 /dev/sdj' is not. Different
custom sections sizes don't seem to make a difference.)
Is there a real problem with the fs or are the newly introduced checks
in kernel 4.5 simply buggy?
---
Matthias
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
next reply other threads:[~2016-03-20 22:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-20 21:53 Matthias Prager [this message]
[not found] ` <20160320224509.GA4752@jaegeuk.hsd1.ca.comcast.net>
2016-03-20 23:52 ` [BUG] f2fs: mounting with kernel >= 4.5.0 fails Matthias Prager
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=56EF1BCF.5010809@matthiasprager.de \
--to=linux@matthiasprager.de \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.