From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Patrick Doyle <wpdster@gmail.com>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: Are there limitation to the number of named pipes/FIFO's supported by F2FS?
Date: Wed, 5 Sep 2018 10:30:25 -0700 [thread overview]
Message-ID: <20180905173025.GD24972@jaegeuk-macbookpro.roam.corp.google.com> (raw)
In-Reply-To: <CAF_dkJAzcBui=6ov=gbob3-T8u2n3QUyn3znSbLUkFjeg7nB8g@mail.gmail.com>
On 09/05, Patrick Doyle wrote:
> On Wed, Sep 5, 2018 at 11:57 AM Chao Yu <chao@kernel.org> wrote:
> > If there is any chance to retry f2fs, let f2fs guys know anything we can help. :)
> >
> Thank you. If I have the opportunity to do that, I'll let you know.
>
> As far as opportunities are concerned, I could just buy (have my
> employer buy) another 1TB SSD, stick it in my system, format it with
> F2FS, and see if I run into these sorts of issues again. All that
> would take is time, which is in short supply right now. But it's not
> out of the question.
>
> > >
> > > For your own reference, I am running my production system on Ubuntu
> > > 16.04 LTS with a "4.15.0-33-generic" kernel.
> >
> > Large nat bitmap feature was supported in 4.17, old kernel can not recognize the
> > feature flag set in mkfs, to make sure, are you porting last f2fs to 4.15?
> What is the "Large nat bitmap feature"? (Now you've got me curious).
>
> Would that have been turned on by default with the 1.11.0 version of
> mkfs.f2fs I used to gain access to the "-i" option?
I'm quite surprised that there was a case requiring over 10M files. I'm
little bit hesitate to enable this by default due to old kernel issue and
runtime checkpoint overheads given more data writes.
df -i:
w/o -i w/ -i
256GB 12812797 12346877
512GB 11800957 24926717
1TB 10017277 48688637
>
> >
> > To Jaegeuk,
> >
> > Anyway, I think we'd better to add some warn info during formatting with an
> > upgraded mkfs, so that it can reduce the possiblity of encountering incompatible
> > issue between new mkfs and old kernel.
> I think it would also be worthwhile also to submit patches to the LTS
> kernels that would check for an inhibit mounting of F2FS filesystems
> that have features unsupported by the kernel. If that is already in
> place, then I shouldn't have been able to mount my f2fs partition if
> it had the "Large nat bitmap feature" enabled.
Agreed, but I haven't taken a look at how ubuntu maintains their kernels.
BTW, 4.17-stable is EOL, and next -stable is 4.18.6.
>
> --wpd
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
next prev parent reply other threads:[~2018-09-05 17:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 16:28 Are there limitation to the number of named pipes/FIFO's supported by F2FS? Patrick Doyle
2018-09-05 1:55 ` Chao Yu
2018-09-05 4:12 ` Jaegeuk Kim
2018-09-05 13:35 ` Patrick Doyle
2018-09-05 15:57 ` Chao Yu
2018-09-05 16:11 ` Patrick Doyle
2018-09-05 17:30 ` Jaegeuk Kim [this message]
2018-09-06 1:51 ` Chao Yu
2018-09-06 13:14 ` Patrick Doyle
2018-09-06 13:29 ` Chao Yu
2018-09-06 2:03 ` Chao Yu
2018-09-06 12:44 ` Chao Yu
2018-09-06 13:31 ` Patrick Doyle
2018-09-05 17:16 ` Jaegeuk Kim
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=20180905173025.GD24972@jaegeuk-macbookpro.roam.corp.google.com \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=wpdster@gmail.com \
/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).