linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: David Gnedt <david.gnedt@davizone.at>
To: Chao Yu <chao2.yu@samsung.com>,
	'Jaegeuk Kim' <jaegeuk@kernel.org>,
	'Matthias Prager' <linux@matthiasprager.de>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: f2fs bug: Unable to mount big volumes in kernel 4.5
Date: Mon, 21 Mar 2016 21:58:15 +0100	[thread overview]
Message-ID: <56F06067.2060404@davizone.at> (raw)
In-Reply-To: <00d401d18320$75f94e80$61ebeb80$@samsung.com>

Hello,

> Following commit in dev branch of f2fs-tools has fixed this issue, could you
test this
> patch firstly?
> ("mkfs.f2fs: set segment_count in super block correctly")

Sorry, I cannot recreate the volume on the 8TB Seagate drive right now, but I
did a test with a loopback device of equal size.

Should I be worried about the changes in mkfs.f2fs since 1.6.0? Would it be
suggested to recreate the filesystem? Or is it maybe possible to manually fix it?
If it is really only the alignment, I think it shouldn't matter for SMR drives,
as they are not using constant size zones anyway, so misalignment cannot be
avoided with f2fs.

>> Could you test the attached patch?

I did a roundup test of all kernel/f2fs-tools version I thought that make sense.
I hope the patch will be included in upcoming mainline kernels.

Short summary:
--------------
Filesystems created with a recent dev version of f2fs-tools work without any
problems and don't need the f2fs kernel patch.
Filesystems created with older f2fs-tools need the f2fs kernel patch to mount
correctly.
I guess that is exactly what everyone expected to be the outcome.

Full details:
-------------
f2fs-tools D:  release 1.6.0 (Seagate SMR drive)
f2fs-tools L1: release 1.6.0 (Loopback)
f2fs-tools L2: 2016-01-08 mkfs.f2fs: introduce zone align for main area (Loopback)
f2fs-tools L3: 2016-03-16 mkfs.f2fs: set segment_count in super block correctly
(Loopback)

Test procedure:
$ truncate -s 8001559724032 f2fs-tools-1.6.0.img
$ losetup -f f2fs-tools-1.6.0.img
$ mkfs.f2fs -s64 -t0 -a0 /dev/loop0
$ mount -t f2fs -onoinline_data,noatime,flush_merge,no_heap,ro /dev/loop0 /mnt
$ umount /mnt

Kernel: Linux 4.4.6 x86_64
f2fs-tools D:  Works
f2fs-tools L1: Works
f2fs-tools L2: Works
f2fs-tools L3: Works

Kernel: Linux 4.5.0 x86_64
f2fs-tools D:  Failed -> Same errors as before
f2fs-tools L1: Failed -> Same errors as before
f2fs-tools L2: Failed -> Same errors as before
f2fs-tools L3: Works

Kernel: Linux 4.5.0+patch x86_64
f2fs-tools D:  Works
f2fs-tools L1: Works
f2fs-tools L2: Works
f2fs-tools L3: Works

Best regards,
David Gnedt

------------------------------------------------------------------------------
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=278785351&iu=/4140

  parent reply	other threads:[~2016-03-21 21:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <56EEC766.2030503@davizone.at>
     [not found] ` <20160320224654.GB4752@jaegeuk.hsd1.ca.comcast.net>
2016-03-21  3:18   ` f2fs bug: Unable to mount big volumes in kernel 4.5 Chao Yu
2016-03-21  9:58     ` Matthias Prager
2016-03-21 15:57       ` Jaegeuk Kim
2016-03-21 10:30     ` Marc Lehmann
2016-03-21 16:03       ` Jaegeuk Kim
2016-03-22  3:37         ` Chao Yu
2016-03-22 20:05           ` Jaegeuk Kim
2016-03-21 20:58     ` David Gnedt [this message]
2016-03-21 22:56       ` Matthias Prager
2016-03-22  8:16         ` Chao Yu
     [not found]         ` <20160322203613.GA14498@jaegeuk.gateway>
2016-03-22 20:50           ` Matthias Prager
2016-03-22 21:05             ` Jaegeuk Kim
     [not found]           ` <56F29214.9040001@davizone.at>
2016-03-23 16:41             ` Matthias Prager
2016-03-23 21:00               ` Marc Lehmann
2016-03-24  1:29                 ` Jaegeuk Kim
2016-03-22 21:05         ` Jaegeuk Kim
2016-03-22  8:15       ` Chao Yu

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=56F06067.2060404@davizone.at \
    --to=david.gnedt@davizone.at \
    --cc=chao2.yu@samsung.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux@matthiasprager.de \
    /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).